toolkit/sync
2021-08-02 16:06:21 -07:00
..
common add additional context for variable in comments 2021-07-09 21:17:40 -07:00
common_8 kickstart directory for pablo 2021-08-02 16:03:51 -07:00
gen-torrents.sh fixup shellcheck 2021-07-09 22:03:32 -04:00
minor-release-sync-to-staging.sh kickstart directory for pablo 2021-08-02 16:06:21 -07:00
prep-staging-8.sh we don't actually have to sed it looks like. 2021-07-27 14:05:36 -07:00
README.md update readme 2021-07-21 11:55:21 -07:00
sign-repos-only.sh update readme 2021-07-21 11:55:21 -07:00
sync-to-prod.sh commented hardlink - add later 2021-07-21 12:44:31 -07:00
sync-to-staging-sig.sh expand use 2021-07-07 19:54:12 -07:00
sync-to-staging.sh expand use 2021-07-07 19:54:12 -07:00
test.sh fixes 2021-07-07 19:58:50 -07:00

sync

These scripts assist in syncing to staging and to prod for releases, whether they are full point releases, simple update releases, or a brand new repository being added. Each script here has a specific purpose.

What to do?

When the scripts are being ran, they are usually ran with a specific purpose or a reason. They are also ran in a certain order.

The below are common vars files. common_X will override what's in common.

.
├── common
├── common_8

These are for the releases in general. What they do is noted below.

├── gen-torrents.sh                  -> Generates torrents for images
├── minor-release-sync-to-staging.sh -> Syncs a minor release to staging
├── prep-staging-8.sh                -> Preps staging updates and signs repos
├── sign-repos-only.sh               -> Signs the repomd (only)
├── sync-to-prod.sh                  -> Syncs staging to production
├── sync-to-staging.sh               -> Syncs a provided compose to staging
├── sync-to-staging-sig.sh           -> Syncs a sig provided compose to staging

Generally, you will only run minor-release-sync-to-staging.sh when a full minor release is being produced. So for example, if 8.5 has been built out, you would run that after a compose. gen-torrents.sh would be ran shortly after.

When doing updates, the order of operations (preferably) would be:

  • sync-to-staging.sh
  • sync-to-staging-sig.sh Only if sigs are updated
  • prep-staging-X.sh -> This is required to ensure the groups, compos, and module data stay sane. This helps us provide older packages in the repos.
  • sync-to-prod.sh -> After the initial testing, it is sent to prod.