summaryrefslogtreecommitdiff
path: root/scripts/release-build
Commit message (Collapse)AuthorAgeFilesLines
* Deploy Masons to use source on upstream trovesRichard Maw2014-08-281-2/+9
| | | | | | | | | | | | | | | | | The per-mason trove only needs to worry about being an artifact cache, so we can prevent it populating itself from the upstream trove by making it use the SSH protocol for fetching sources, and not registering its ssh key with the upstream trove. The MASON_UPSTREAM_TROVE_ADDRESS option has been removed, as this is now the TROVE_HOST. The distbuild network is now configured to use the upstream trove for sources, and the local trove for artifacts, with the ARTIFACT_CACHE_SERVER option. mason.configure now uses ARTIFACT_CACHE_SERVER to tell deploy commands which server to fetch artifacts from.
* Simplify logic and conditionLars Wirzenius2014-07-301-3/+2
| | | | | Avoiding a condition that has a negation tends to be a bit simpler for humans to understand.
* Remove unnecessary leading _ from methodLars Wirzenius2014-07-301-3/+3
|
* Allow release deployments with system name ≠ deployment namebaserock/michaeldrake/ci-release-scriptsMichael Drake2014-07-301-24/+21
| | | | | 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.
* Allow release scripts to be configured to only handle a subset of architecturesMichael Drake2014-07-301-0/+5
| | | | | | | | | | | 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.
* Allow release-build to build subsystems of defined systemsMichael Drake2014-07-301-1/+8
|
* Write release images into release subdirectoryMichael Drake2014-07-301-2/+1
| | | | | | | | 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.
* Add new scripts for building, uploading releaseLars Wirzenius2014-07-241-0/+161
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.
View Lorry Controller Status