From: Willian Rampazzo <wrampazz@redhat.com>
To: Wainer dos Santos Moschetta <wainersm@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu Daude" <philmd@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Willian Rampazzo" <willianr@redhat.com>,
"Cleber Rosa Junior" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 3/3] gitlab-ci: Archive logs of acceptance tests
Date: Thu, 17 Dec 2020 10:36:24 -0300 [thread overview]
Message-ID: <CAKJDGDYAp+FML_fjJYR5zcPsxhtbG+Ajv_zQMNokiZB+dMv-tg@mail.gmail.com> (raw)
In-Reply-To: <20201211183827.915232-4-wainersm@redhat.com>
On Fri, Dec 11, 2020 at 3:38 PM Wainer dos Santos Moschetta
<wainersm@redhat.com> wrote:
>
> Keep the logs of acceptance tests for two days on GitLab. If you want
> to make it available for more time, click on the 'Keep' button on
> the Job page at web UI.
>
> By default GitLab will archive artifacts only if the job succeed.
> Instead let's keep it on both success and failure, so it gives the
> opportunity to the developer/maintainer to check the error logs
> as well as to the logs of CANCEL tests (not shown on the job logs).
>
> Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
> ---
> .gitlab-ci.yml | 4 ++++
> 1 file changed, 4 insertions(+)
>
Reviewed-by: Willian Rampazzo <willianr@redhat.com>
prev parent reply other threads:[~2020-12-17 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 18:38 [PATCH 0/3] gitlab-ci: Refactor show logs code and archive logs Wainer dos Santos Moschetta
2020-12-11 18:38 ` [PATCH 1/3] tests/acceptance: Bump avocado requirements to 83.0 Wainer dos Santos Moschetta
2020-12-14 20:48 ` Willian Rampazzo
2020-12-11 18:38 ` [PATCH 2/3] gitlab-ci: Refactor code that show logs of failed acceptances Wainer dos Santos Moschetta
2020-12-14 20:53 ` Willian Rampazzo
2020-12-11 18:38 ` [PATCH 3/3] gitlab-ci: Archive logs of acceptance tests Wainer dos Santos Moschetta
2020-12-17 12:48 ` Thomas Huth
2020-12-17 13:36 ` Willian Rampazzo [this message]
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=CAKJDGDYAp+FML_fjJYR5zcPsxhtbG+Ajv_zQMNokiZB+dMv-tg@mail.gmail.com \
--to=wrampazz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=willianr@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).