From: "Q. Gylstorff" <Quirin.Gylstorff@siemens.com>
To: jan.kiszka@siemens.com, xenomai@xenomai.org
Subject: [xenomai-images][PATCH 0/4] Prepare xenomai-images for public LAVA Server
Date: Thu, 8 Jul 2021 17:02:57 +0200 [thread overview]
Message-ID: <20210708150301.24083-1-Quirin.Gylstorff@siemens.com> (raw)
From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
Add option to upload the image under test to AWS.
Add option to use AWS as image download source and use
[1] as default LAVA server.
After this patchset is merged the private lava lab
can be migrated.
[1]: https://lava.xenomai.org
Quirin Gylstorff (4):
ci: Add option to upload artifacts to aws bucket
ci: adapt to public lava-server
scripts/run_lava_tests.sh: cleanup shellcheck warnings
README: Add information about LAVA Lab
README.md | 14 ++++++
ci/gitlab-ci-base.yml | 6 ++-
scripts/deploy_to_aws.sh | 46 ++++++++++++++++++++
scripts/run-lava-tests.sh | 90 +++++++++++++++++++++++----------------
4 files changed, 117 insertions(+), 39 deletions(-)
create mode 100755 scripts/deploy_to_aws.sh
- '-
2.20.1
next reply other threads:[~2021-07-08 15:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 15:02 Q. Gylstorff [this message]
2021-07-08 15:02 ` [xenomai-images][PATCH 1/4] ci: Add option to upload artifacts to aws bucket Q. Gylstorff
2021-07-08 15:02 ` [xenomai-images][PATCH 2/4] ci: adapt to public lava-server Q. Gylstorff
2021-07-08 15:03 ` [xenomai-images][PATCH 3/4] scripts/run_lava_tests.sh: cleanup shellcheck warnings Q. Gylstorff
2021-07-08 15:43 ` Bezdeka, Florian
2021-07-08 15:45 ` Jan Kiszka
2021-07-08 15:50 ` Bezdeka, Florian
2021-07-08 15:56 ` Jan Kiszka
2021-07-09 11:40 ` Gylstorff Quirin
2021-07-09 11:48 ` Jan Kiszka
2021-07-08 15:03 ` [xenomai-images][PATCH 4/4] README: Add information about LAVA Lab Q. Gylstorff
2021-07-08 15:43 ` [xenomai-images][PATCH 0/4] Prepare xenomai-images for public LAVA Server Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210708150301.24083-1-Quirin.Gylstorff@siemens.com \
--to=quirin.gylstorff@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.