Various scripts and tools for SIG/Core
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
Louis Abel b71ae4ce74
add cinnamon to 9 profile
4 days ago
.github/workflows Fix names for jobs 9 months ago
analyze Add really simple download stats script to parse fastly logs on disk 11 months ago
chat Add chat scripts and update propagation for amis 10 months ago
func add openssh tests 3 months ago
iso add cinnamon to 9 profile 4 days ago
mangle fix .gitignore in generates 2 weeks ago
sync increase workers of createrepo 2 months ago
.disable.gitlab-ci.yml fix up readme, disable gitlab tests for now 9 months ago
.gitignore add gitignore 9 months ago
README.md clarify readme 3 months ago

README.md

sig-core-toolkit

Release Engineering toolkit for repeatable operations or functionality testing.

Currently mirrored at our github, and the RESF Git Service. Changes will typically occur at the RESF Git Service.

What does this have?

  • analyze -> Analysis utilities (such as download stats)
  • chat -> mattermost related utilities
  • func -> (mostly defunct) testing scripts and tools to test base functionality
  • iso -> Contains empanadas, which provides ISO, Compose, and Sync related utilities.
  • mangle -> Manglers and other misc stuff
  • sync -> Sync tools, primarily for Rocky Linux 8 and will eventually be deprecated

How can I help?

Fork this repository and open a PR with your changes. Keep these things in mind when you make changes:

  • Your PR should be against the devel branch (not optional)

  • Have pre-commit installed if possible

  • Have shellcheck installed if possible

  • Shell Scripts: These must pass a shellcheck test!

  • Python scripts: Try your best to follow PEP8 guidelines (even the best linters get things wrong)

    • Note that not everything has to pass. Just try your best.

PR's against the main branch will be closed.

PR's are preferred at the RESF Git Service.

Will some of this be moved into separate repositories?

There may be some things that will be moved to its own repository in the near future. From a SIG/Core standpoint, we believe a good chunk of this should stay here as it makes it easier for us to maintain and manage.