Various scripts and tools for SIG/Core
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Louis Abel 5989f4392f
provide a choice on stage or peridot for live
2 weeks ago
.github/workflows Fix names for jobs 5 months ago
analyze Add really simple download stats script to parse fastly logs on disk 7 months ago
chat Add chat scripts and update propagation for amis 7 months ago
func Merge pull request 'Fix exit status check.' (#8) from stack/toolkit:exit-status into devel 2 weeks ago
iso provide a choice on stage or peridot for live 2 weeks ago
live begin ISO magic 7 months ago
mangle try to fix local pungi prepop 1 month ago
sync actually bump to RC4 for final compose 2 weeks ago
.disable.gitlab-ci.yml fix up readme, disable gitlab tests for now 5 months ago
.gitignore add gitignore 5 months ago
README.md make a correction on the readme 5 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 -> ISO, Compose, and Sync related utilities, primarily for Rocky Linux 9+
  • live -> Live image 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:

  • Have pre-commit installed
  • Have shellcheck installed
  • Shell Scripts: These must pass a shellcheck test!
  • Python scripts: Try your best to follow PEP8 guidelines (even the best linters get things wrong)

Your PR should be against the devel branch at all times. PR's against the main branch will be closed.

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.