Bring back the automatic check for production builds so that images are put in
their main location and test jobs are submitted to LAVA, but mangle the LAVA
webhook callback URL so that we don't create too much noise in Phabricator at
this point.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Due to a GPLv3/readline-releated issue gnupg2 is currently uninstallable and
thus ostree cannot be installed as well, breaking the image build.

In order to start playing with the LAVA setup while the ostree issue is being
resolved temporarily disable the failing images.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

For the v2019dev0 release we'll move to assuming u-boot is in SPI flash
for i.mx6 which allows the sabrelite board to use standard images rather
then needing a specific ones.

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

Fixes: APERTIS-5659

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Fixes: APERTIS-5662

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

If the `image-ostree-$board` entry is marked successful then `ostree`
has to be `true` or the step wouldn't have been run.

Using `true` directly makes the code a bit more explicit and clear.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The only caller of runTestsJobs() is submitTests() and having them split
out doesn't bring any benefit.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The check whether LAVA josb should be submitted now happens outside
of submitTests().

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Keep track of skipped artifacts, failed builds and if the build has been
killed half way so we can find out if a build is suitable for
releasing/longer term preservation (for instance, for being saved as a
weekly entry).

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Ritesh Raj Sarraf <rrs@debian.org>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Since commit a3749cd5 removed the need to work around some NSS/SSH
shortcomings, we can now get rid of the last vestiges of the
workarounds, simplifying the code.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Just like the full SDK, the base SDK image ships the `armhf` devroot
out-of-the-box, so it needs to depend on it.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

After generating the commit, we can use the tip of the branch
to generate the static delta that exactly matches the commit.
Use image_name as the name of the static delta to help distinguish
between each other when in a repository.
The name also contains the pipeline version in the name, hence it
is possible to sort by filename to get the most recent static delta.

Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>

Emanuele Aina authored 6 years ago and Frédéric Dalleau committed 6 years ago

The Base SDK does not need the bits which are specific to the
Canterbury-based app framework and the Mildenhall HMI.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Knowing where the current images live is necessary to be able
to fetch extra ospacks on demand.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Image recipes may need to know images for what release we’re building.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

From now on, sysroots will be for debugging and related purposes,
devroot will be used for foreign archirecture compilation etc.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Ritesh Raj Sarraf authored 6 years ago and Andrej Shadura committed 6 years ago

This is a derivative of image type 'sdk' with 'ivitools' disabled
Apertis: T5428

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Use just a single board definition for both SDK images, and
symlinks for the overlay.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

A new parameter, 'requires', allows declaring a dependency on
a different image build.

Instead of a single artifact list, define two lists.
First build artifacts not requiring any other artifacts,
then build artifacts depending on other artifacts.

This code doesn’t support transitive dependencies.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Instead of manually assembling the artifact list by calling
buildImages with cryptic indexed arguments, take a more declarative
approach of putting everything into a single map and creating
the artifact list out of it programmatically.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Now, with the libnss-unknown package included in our docker build
images, this hack can be safely dropped

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

This pass the release version during test execution because it is needed
by lava-submit.

Signed-off-by: Luis Araujo <luis.araujo@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

The release string in the profile name for lava jobs is unneeded.

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Signed-off-by: Ritesh Raj Sarraf <rrs@debian.org>

Since e1f04718, recipes add .tar.gz themselves, accepting a generic basename
instead. Sysroot generation initially didn’t take that into account, with
337970b9 fixing that issue. However, the sysroot conf file was still broken
as the .tar.gz suffix wasn’t explicitly included.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Commit e1f04718 broke sysroot tarball name generation, resulting
in .tar.gz.tar.gz files.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The default demopack installs media files in `/home/shared`: by
including them only in the ospack they are unavailble on the ostree
images as the whole `/home` gets filtered out during `ostree commit`.

Moving the extraction of the demopack when the full filesystem gets
deployed to the images makes the media files available on ostree images
as well.

See https://phabricator.apertis.org/T5313



Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Emanuele Aina authored 6 years ago and Frédéric Dalleau committed 6 years ago

Export the list of packages installed in the final artifact just before
removing the dpkg database.

This will allow to quickly check the artifacts contents without
unpacking and processing them.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Emanuele Aina authored 6 years ago and Frédéric Dalleau committed 6 years ago

Make ospack and sysroot recipes take a generic basename for the output
artifacts, to which the `.tar.gz` file extension is appended by the
recipe itself. The recipes for the images already works this way as it
works better when generating multiple artifacts.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Ensure that ostree repositories are published just like the other
artifacts. Push the whole repository if one doesn't exist already.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>