| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
There used to be a check that prevented deployments with names different
to the system. I don't know why this was, but I don't think we need it.
|
|
|
|
|
| |
Without this change the rsync and xargs commands will wait forever for
input that will never arrive.
|
|
|
|
|
|
|
|
|
|
|
| |
We currently build all architectures at once during the release process,
however for our CD pipeline we operate with one CD pipeline per
architecture.
This is not just useful for the CD pipeline work though, as it allows
one organisation to handle releases for x86, where the infrastructure
may be located in the cloud, and one organisation to handle ARM systems,
which may be located in an office.
|
|
|
|
|
|
|
|
|
| |
For continuous artifact cache population, we don't care so much about
the large disk images that we make available at release time.
This patch allows omitting any of the configuration required to upload
the release images to mean that we didn't want to upload them, and
continue without doing so.
|
| |
|
|
|
|
|
|
|
|
| |
The script used to chdir into the release directory before running morph
deploy. Unfortunately, this didn't work because deployments are run from
the top of the definitons repository.
So now the release directory is included in the path to be deployed.
|
| |
|
|
|
|
| |
Suggested-by: Sam Thursfield
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These scripts are a rewrite of scripts/do-release.py and
scripts/distbuild-cluster. The biggest difference is that they split
the tasks of building the things that are to be released, and uploading
them to git.baserock.org / download.baserock.org, where do-release.py
combines both (and distbuild-cluster only builds chunk/stratum/system
artifacts, not the release images). The new scripts are also configurable
using command line options or a configuration file rather than requiring
editing of the source.
These changes will allow, for example, a CI job that builds a release,
but doesn't upload it to download.baserock.org.
The new scripts are coupled with a change to the release process, which
will be documented as a change to the release process page on
wiki.baserock.org.
The 14.29 release of Baserock was done with slightly different versions
of these scripts to make it feasible to upload things over multiple
network connections.
|
|
|
|
|
| |
Fix string quoting.
Put all stuff that needs changed in angle brackets.
|
|
|
|
| |
Replaces references to `master` with release tag name.
|
|\
| |
| |
| |
| | |
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
Reviewed-By: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
|
| |
| |
| |
| |
| |
| |
| | |
- Adds ability to pass cluster, ref and distbuild controller
hosts on the command line.
- Adds --help, and usage.
- Prints the specified parameters out.
|
|/
|
|
|
| |
Remove a comment that is no longer true, fix a formatting error, and
add a docstring to a class that lacked one.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The 'morph deploy' command now lets us deploy system images one at a
time, so let's do that. This means that if all but one image is
deployed successfully, on the next run the user just needs to deploy
one further image.
Also, since each deployment has a unique name in release.morph now,
we can override the location and VERSION_LABEL fields instead of
requiring the user to update them manually before each release. The
release.morph cluster should now specify the *basename* of the image
in the location field only. By basename, I mean the system name plus
the appropriate extension (normally .tar or .img). The do-release
script will then prepend the image path and the version label to get
a filename.
The release.morph cluster has been updated accordingly.
|
|
|
|
|
| |
This was suggested by Richard Maw and I forgot to fix up the branch
'sam/auto-release' before merging it.
|
|
|
|
|
| |
This was a review comment from Richard Maw which I forgot to include
before merging branch 'sam/auto-release'
|
|
|
|
|
| |
If the release script is expected to be 'push-button' then we can't
assume the user will be paying attention to error messages later on.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes it more likely that new artifacts and images might be
publically available before they are officially announced, but I can't
see that causing problems.
Changes were required so that the script will only make public the files
that are part of the release, and not do 'mv *' from a configured
location into a publically shared location while unsupervised. The
intermediate .tar file is now removed from the artifact server when the
script completes.
The script no longer outputs debug messages by default, because the
really long SSH commandlines used to move files into place make this
pretty hard to follow. Some extra status() calls have been added
instead.
There are a few other cosmetic changes in this commit.
|
| |
|
| |
|
|
They probably do not belong in definitions.git at all, but at least they
are now in one place.
In future they should move either into a separate baserock-utilities
chunk, or into morph.git itself.
|