sshtepa/toolkit
1
0
Fork 0
forked from sig_core/toolkit
Code Pull Requests Activity
Various scripts and tools for SIG/Core
387 Commits 1 Branch 0 Tags 1.9 MiB
Python 72.5%
Shell 23%
Go 3.2%
Ruby 0.9%
Dockerfile 0.4%
0ea2b7fb48
Go to file
Neil Hanlon 0ea2b7fb48
Fix matching for image propagation
2022-10-11 11:51:24 -04: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 add a sudo test 2022-06-29 21:49:12 -07:00
iso Add i686 to translation map 2022-10-11 11:51:23 -04:00
live begin ISO magic 2022-05-19 00:48:07 -07:00
mangle add version parser 2022-09-26 12:36:49 -07:00
sync Fix matching for image propagation 2022-10-11 11:51:24 -04: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 make a correction on the readme 2022-07-11 17:32:47 -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 -> 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.