| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
The distbuild system can be configured to act as a CI controller.
Providing appropriate config makes it copy all the scripts and systemd
units out of the mason directory onto the target, such that it will
start building and testing the configured cluster morphology on boot.
|
| |
|
|
|
| |
This will deploy and run build tests on systems listed in the morphology
passed as its first argument.
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| | |
Reviewed-By: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
|
| |/
|
|
| |
This makes the release-upload script more versatile.
|
| | |
|
| |\
| |
| |
| |
| | |
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
Reviewed-By: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
|
| | | |
|
| | |
| |
| |
| | |
No morph file is needed in any of them
|
| | |
| |
| |
| |
| | |
No morph file needed thanks to a patch upstreamed by me to use
autoreconf to check the automake version
|
| | |
| |
| |
| |
| | |
GTK+2 doesnt depend on genivi-foundation and x-common is already a
dependency of x-x86_64-generic
|
| | |
| |
| |
| | |
stratum
|
| | |
| |
| |
| | |
As they are shared by GTK+2 and GTK+3
|
| |/
|
|
|
| |
Move to xfce stratum for now as seems to be the only stratum that
requires it
|
| |\
| |
| |
| |
| | |
This is a merge of the baserock/michaeldrake/ci-release-scripts branch,
but with some cleanups of the code for cleanliness.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
For comprehensibility.
|
| | | |
|
| | |
| |
| |
| |
| | |
Avoiding a condition that has a negation tends to be a bit simpler
for humans to understand.
|
| | |
| |
| |
| |
| | |
Move stuff into new methods to make overall logic clearer and to
avoid stuffing too much into each method.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
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.
|
| |
|
|
|
| |
Reviews:
+2 Richard Maw
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| | |
This merges Javier's patch to update glib and gobject-introspection
that was sent to the mailing list.
Reviewed-by: Richard Maw
Reviewed-by: Pedro Alvarez
|
| |/
|
|
| |
(2.40 and 1.40)
|
| |\
| |
| |
| |
| |
| |
| |
| | |
This merges an update of connman to 1.24 by Pedro Alvarez as
required for GENIVI.
Reviewed-by: Richard Maw
Reviewed-by: Sam Thursfield
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
This merges changes from Emmet Hikory and Michael Drake to
consolidate X strata so they're easier to work with.
|
| | |
| |
| |
| | |
This is the ref for the merged branch from Emmet.
|
| | |
| |
| |
| |
| | |
The GENIVI-specific X definitions now only differ in name, so
may be consolidated.
|
| |/
|
|
|
|
| |
As the X morphlogies no longer carry significant variation, and
maintaining syncronisation becomes a frustrating manual exercise, they
are consolidated, based on the x86_64 X, which seems most current.
|
| |\
| |
| |
| |
| | |
Reviewed-by: Richard Maw
Reviewed-by: Adam Coldrick
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
- Scripts written by Lars Wirzenius.
- Reviewed by Michael Drake.
These scripts are to be copied to the system on which the
backups are made. They are stored here to keep the related
logic in one source location.
|
| | |
| |
| |
| |
| | |
This is useful so that we can deploy a Gitlab system with a separate
/home disk.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The Gitlab Rake script for backing up doesn't backup the database
that Gitlab CI uses, and additonally it does a git bundle for each
git repository. Our GitLab instance has hundreds of git repositories,
making the bundling be a very expensive things.
Instead, we use the Postgres tool to dump all databases to a file,
and arrange to backup the dump files, the git repositories, and all
other relevant files directly.
|
| | | |
|
