From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: Cleber Rosa <crosa@redhat.com>, qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>, "Thomas Huth" <thuth@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Erik Skultety" <eskultet@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Andrea Bolognani" <abologna@redhat.com>,
"Willian Rampazzo" <wrampazz@redhat.com>,
"Stefan Hajnoczi" <stefanha@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [PATCH 0/3] gitlab-pipeline-status script: provide more information on errors
Date: Tue, 23 Feb 2021 11:52:17 -0300 [thread overview]
Message-ID: <c3b6aaa9-9914-fed6-aaa8-ef9e5258c714@redhat.com> (raw)
In-Reply-To: <20210222193240.921250-1-crosa@redhat.com>
Hi Cleber,
In case you need to send a v2, mind to add the following patch together?
commit 3c4ed8a78e096e4d7df0398c29887a9d468ae120 (HEAD -> gitlab_runners)
Author: Wainer dos Santos Moschetta <wainersm@redhat.com>
Date: Tue Feb 23 11:26:08 2021 -0300
scripts/ci/gitlab-pipeline-status: Handle ValueError exceptions nicely
With this change, when getting the local branch, it will handle nicely
any threw ValueError exception instead of print the stack trace.
Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
diff --git a/scripts/ci/gitlab-pipeline-status
b/scripts/ci/gitlab-pipeline-status
index 924db327ff..6177df973a 100755
--- a/scripts/ci/gitlab-pipeline-status
+++ b/scripts/ci/gitlab-pipeline-status
@@ -160,7 +160,11 @@ def main():
args = parser.parse_args()
if not args.commit:
- args.commit = get_local_branch_commit(args.branch)
+ try:
+ args.commit = get_local_branch_commit(args.branch)
+ except ValueError as error:
+ print("ERROR: %s" % error)
+ sys.exit(1)
success = False
try:
On 2/22/21 4:32 PM, Cleber Rosa wrote:
> When things go wrong with the GitLab API requests, it's useful to give
> users more information about the possible causes.
>
> Cleber Rosa (3):
> scripts/ci/gitlab-pipeline-status: split utlity function for HTTP GET
> scripts/ci/gitlab-pipeline-status: give more information on failures
> scripts/ci/gitlab-pipeline-status: give more info when pipeline not
> found
>
> scripts/ci/gitlab-pipeline-status | 25 ++++++++++++++++++-------
> 1 file changed, 18 insertions(+), 7 deletions(-)
>
next prev parent reply other threads:[~2021-02-23 15:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 19:32 [PATCH 0/3] gitlab-pipeline-status script: provide more information on errors Cleber Rosa
2021-02-22 19:32 ` [PATCH 1/3] scripts/ci/gitlab-pipeline-status: split utlity function for HTTP GET Cleber Rosa
2021-02-23 14:38 ` Wainer dos Santos Moschetta
2021-02-23 18:09 ` Alex Bennée
2021-02-22 19:32 ` [PATCH 2/3] scripts/ci/gitlab-pipeline-status: give more information on failures Cleber Rosa
2021-02-23 14:40 ` Wainer dos Santos Moschetta
2021-02-23 18:09 ` Alex Bennée
2021-02-22 19:32 ` [PATCH 3/3] scripts/ci/gitlab-pipeline-status: give more info when pipeline not found Cleber Rosa
2021-02-23 14:43 ` Wainer dos Santos Moschetta
2021-02-23 14:52 ` Wainer dos Santos Moschetta [this message]
2021-02-23 15:19 ` [PATCH 0/3] gitlab-pipeline-status script: provide more information on errors Erik Skultety
2021-02-23 15:53 ` Wainer dos Santos Moschetta
2021-03-03 17:54 ` Thomas Huth
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=c3b6aaa9-9914-fed6-aaa8-ef9e5258c714@redhat.com \
--to=wainersm@redhat.com \
--cc=abologna@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=eskultet@redhat.com \
--cc=fam@euphon.net \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=thuth@redhat.com \
--cc=wrampazz@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 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.