The release build should ensure it starts from a fresh environment to avoid
potential mismatches with old code.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
We need separate config files for different DEY versions, so store each file
set in a folder named after the corresponding Yocto codename.
https://onedigi.atlassian.net/browse/DEL-9539
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Instead of having one toolchain per image, we now provide one per platform.
https://onedigi.atlassian.net/browse/DEL-9297
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
In our previous commit, we changed the CVE scan class from "vigiles" to
"digi_ccss" if we plan on building images with the CVE layer. However, we
make this change in conf/local.conf and then run "bitbake-layers add-layer" to
add said layer. Since the bbclass is exclusive to the CVE layer, bitbake isn't
able to recognize it and fails.
Add the CVE layer to the project before adding the Vigiles configuration
template to conf/local.conf.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Our CVE layer now includes a new bbclass that extends the logic of the
"vigiles" bbclass. Use this new class if we are building images with the CVE
layer.
https://onedigi.atlassian.net/browse/DEL-8939
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The crank engine hasn't been fully tested on these platforms yet, so remove
the image from our default build.
https://onedigi.atlassian.net/browse/DEL-8862
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
DY_MACHINES_LAYER is an optional variable only used once. Use bash's
"alternate value" expansion and get rid of the intermediate MACHINES_LAYER
variable.
While on it, remove the DY_BUILD_VARIANTS reference in the script header
as that was removed long ago.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
DY_MANIFEST parameter allows to do a 'repo init' with a specific
manifest file contained in the manifest repository. For example,
'manufacturing.xml' for building manufacturing projects.
By default no manifest file parameter is provided, so the 'repo init'
command will initialize based on the 'default.xml' manifest file.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
(cherry picked from commit c38b4fc4f2c565ab9db20c082016401341e78ce5)
ConnectCore MP15 has support to QT applications, so add it to the daily build.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
(cherry picked from commit b92028b407)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
For now, we're only interested in generating the SBOM, which we can upload and
have Vigiles scan later on if needed. The report generation process adds some
overhead and can cause unwanted errors if the Vigiles server takes too long.
Enable report generation for our automated builds.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This adds two new options:
* One to generate a Vigiles CVE report along with a build
* One to include the meta-digi-security layer in a build
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Support to build wayland-based graphical images has been added for ccimx93,
so build that image.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In the CC6UL this is the only image that has the connectcore demo
included, so add it to the daily build.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is dead code used in the past for the ccardimx28. It is not used in
any other platform, so just remove it.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
By default is enabled the reproducible builds feature and to provide a real
timestamp for the build system, we include it in our local.conf file.
https://onedigi.atlassian.net/browse/DEL-7574
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The buildserver uses this default value when building framebuffer images. Since
the WebKit is not yet compatible with framebuffer images, the builds fail.
Remove dey-image-webkit from the default target lists.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This image is very similar to dey-image-qt, but it includes the WebKit
packagegroup instead of the Qt one. Said packagegroup contains all of the
elements needed to run a WebKit-based browser environment in DEY.
This image requires the meta-webkit layer, so include it in our default
bblayers template. For now, include all WebKit related recipes in a dynamic
layer, because the ccimx6ul doesn't support WebKit and its projects don't need
meta-webkit at all.
https://jira.digi.com/browse/DEL-7339
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This commit fixes an intermittent issue when we are cloning several
repos with a huge history, throwing an unexpected error.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
If we want to share the downloads folder between projects
we need to move it outside to don't remove it.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
These platforms are not supported on DEY 2.6 yet, and a project created for
either of them will fail during the build.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The file 'manufacturing.xml' file in the manifests repository does not exist.
When building manufacturing artifacts, we must use the 'manufacturing/morty'
branch, that already contains the right repositories to clone.
For a manufacturing job, this commit only adds the 'meta-digi-mfg' if it is not
already there.
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
(cherry picked from commit 379ca469dff949e09c667d1a448012881b8812d2)
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Arturo Buzarra
Gabriel Valcazar
Hector Palacios
Javier Viguera
Gonzalo Ruiz
Tatiana Leon
Mike Engel
Isaac Hermida