baserock/baserock/definitions.git - gitlab.com: baserock/definitions.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Use file: URI for list-artifacts in release-upload	Richard Maw	2014-08-19	1	-1/+1
\| \| \| \| \| \|	This requires the script be run in the top of the definitions repository, but will actually try to upload the changes that were tested, rather than the current HEAD.
*	Pass cluster morphology to release upload script.baserock/michaeldrake/release-upload-cluster	Michael Drake	2014-08-01	1	-9/+12
\| \| \| \|	This makes the release-upload script more versatile.
*	Add --upload-build-artifacts setting	Lars Wirzenius	2014-07-30	1	-1/+13
\|
*	Join short lines into one line, for readability	Lars Wirzenius	2014-07-30	1	-2/+1
\|
*	Avoid running rsync if source file list is empty	Lars Wirzenius	2014-07-30	1	-1/+4
\|
*	Refactor long method into smaller ones	Lars Wirzenius	2014-07-30	1	-19/+37
\| \| \| \|	For comprehensibility.
*	Add markers around list in debug log	Lars Wirzenius	2014-07-30	1	-0/+2
\|
*	Refactor process_args to be clearer	Lars Wirzenius	2014-07-30	1	-9/+14
\| \| \| \| \|	Move stuff into new methods to make overall logic clearer and to avoid stuffing too much into each method.
*	Add --upload-release-artifacts setting	Lars Wirzenius	2014-07-30	1	-13/+9
\|
*	Fix releasing when no changes to the cache are required	Michael Drake	2014-07-30	1	-6/+9
\| \| \| \| \|	Without this change the rsync and xargs commands will wait forever for input that will never arrive.
*	Allow release scripts to be configured to only handle a subset of architectures	Michael Drake	2014-07-30	1	-1/+28
\| \| \| \| \| \| \| \| \| \| \|	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-upload to be configured not to upload release images	Michael Drake	2014-07-30	1	-3/+21
\| \| \| \| \| \| \| \| \|	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.
*	Chmod uploaded files	Lars Wirzenius	2014-07-24	1	-1/+18
\| \| \| \|	Suggested-by: Sam Thursfield
*	Add new scripts for building, uploading release	Lars Wirzenius	2014-07-24	1	-0/+370
	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.