Remove files to cleanup disk space so if the machine gets
re-used we aren't wasting disk space. This can happen when different
build types (zephyr, bluetooth, and daily) all happen on the same
machine.
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
Remove the temporary fixes for installing lpc_checksum
and imgtool packages in buildkite. Not required with
the new docker image.
Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
Force CI to manually install imgtool, which is needed
for sanitycheck to build and run the TF-M integration
samples with MCUboot (where MCUboot is built from the
TF-M external project).
Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
On errors we were aborting immediately skipping any needed cleanup after
the error has occured. This will run the cleanup function and upload
reports of failure when something bad happens.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Transient network errors may cause west update to fail. Retry it in
case that happens. Updates for projects which are already up to date
won't hit the network.
Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
Whenever we have an error in the script, exit immediately and avoid
confusing unrelated messages about disk space and such.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
The sanitycheck tests are all failing for the lpcxpresso11u68 board
because the lpc_checksum, a new python script requirement introduced
by this board, is not present in the build environment. This
commit attempt to fix this issue by installing lpc_checksum before
running sanitycheck.
Signed-off-by: Maxime Bittan <maxime.bittan@seagate.com>
We use a seperate pipeline step and try and reuse the run.sh script with
some minor modifications. There's a seperate pipeline for this purpose
that does the schedule build.
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
The junit-annotate step will fail if there are no sanitycheck-*.xml
files to be found which can happen if sanitycheck is run and does
nothing (for example an update to .editorconfig).
Try and create an empty sanitycheck.xml in such a case.
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
Add setup to utilize buildkite for CI purposes:
1. .buildkite/hooks/pre-command:
* Handles getting git checkout setup against upstream repo
* Setup some west module cache (dirs, clean out files & locks)
* init dir for ccache
2. .buildkite/hooks/post-command:
* Report disk usage (meant for possible debugging)
3. .buildkite/pipeline.yml [uses to determine what to do]:
* setup zephyr env vars
* set which docker container to use
(export some local disk caches for git, west modules, and ccache)
* uses plug to general build annotation on failure (junit-annotate)
4. .buildkite/run.sh [ buildkite wrapper to invoke scripts/ci/run.sh ]
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
Kumar Gala