sig_core/toolkit
sig_core/toolkit
7
2
Fork 3
Code Issues 6 Pull Requests 2 Actions Projects Releases Wiki Activity
Various scripts and tools for SIG/Core
485 Commits 8 Branches 0 Tags 2 MiB
Python 72.8%
Shell 22.8%
Go 3.1%
Ruby 0.9%
Dockerfile 0.4%
0ad6773539
Go to file
Louis Abel 0ad6773539
catch running as root and old bumpspec version
2022-12-21 01:30:01 -07:00
.github/workflows Fix names for jobs 2022-07-08 13:28:44 -04:00
analyze Add really simple download stats script to parse fastly logs on disk 2022-05-12 18:33:23 -04:00
chat Add chat scripts and update propagation for amis 2022-05-26 00:24:52 -04:00
func Merge pull request 'Fix exit status check.' (#8) from stack/toolkit:exit-status into devel 2022-11-22 03:11:27 +00:00
iso add kernel param to actually boot ppc64le 2022-12-19 20:24:20 -05:00
mangle catch running as root and old bumpspec version 2022-12-21 01:30:01 -07:00
sync Fix regex for syncing 2022-12-19 20:20:28 -05:00
.disable.gitlab-ci.yml fix up readme, disable gitlab tests for now 2022-06-28 12:41:12 -07:00
.gitignore add gitignore 2022-07-13 23:33:23 -04:00
README.md General Changes 2022-12-20 02:05:53 -07:00

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:

  • 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.

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.