Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
Release Engineering
Public
toolkit
Commits
1a35fafa
Commit
1a35fafa
authored
Jul 21, 2021
by
Louis Abel
📺
Browse files
Merge branch 'devel' into 'main'
update readme See merge request
!14
parents
5ddf42fe
b077152f
Pipeline
#47
passed with stage
in 30 seconds
Changes
2
Pipelines
1
Show whitespace changes
Inline
Side-by-side
sync/README.md
View file @
1a35fafa
...
...
@@ -4,3 +4,42 @@ 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.
sync/sign-repos-only.sh
View file @
1a35fafa
#!/bin/bash
# Signs repo metadata only
# Source common variables
export
RLVER
=
8
# shellcheck disable=SC2046,1091,1090
source
"
$(
dirname
"
$0
"
)
/common"
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment