From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: repo.eclipse.org outage breaking all our linux CI jobs
Date: Thu, 24 Apr 2025 15:13:58 -0700 [thread overview]
Message-ID: <xmqqfrhxtdg9.fsf@gitster.g> (raw)
As https://www.eclipsestatus.io/ reports there is no ETA for
recovery, and due to the failure of downloading JGit material in an
early stage of our CI jobs, our linux CI jobs are all failing, I am
very tempted to apply the following to 'maint' immediately and
propagate it all the way up to 'master', 'next', and 'seen'.
I would very very much appreciate additional thoughts and advices by
anybody more involved in JGit community and more clueful than I am
on the situation.
Anyway, what is somewhat funny is that at the end of this script,
there is an attempt to notice and report the lack of jgit (as well
as p4 and lfs) but still continuing:
...
if type jgit >/dev/null 2>&1
then
echo "$(tput setaf 6)JGit Version$(tput sgr0)"
jgit version
else
echo >&2 "WARNING: JGit wasn't installed, see above for clues why"
fi
end_group "Install dependencies"
but because ci/lib.sh does "set -e", we fail way before we hit this
code. I am tempted to suggest we remove that "set -e" as a long
term maintainability improvement measure, but that is a separate
topic.
ci/install-dependencies.sh | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git c/ci/install-dependencies.sh w/ci/install-dependencies.sh
index be9ba5e30a..4dda5db7e5 100755
--- c/ci/install-dependencies.sh
+++ w/ci/install-dependencies.sh
@@ -74,8 +74,9 @@ ubuntu-*|i386/ubuntu-*|debian-*)
-C "$CUSTOM_PATH" --strip-components=1 "git-lfs-$LINUX_GIT_LFS_VERSION/git-lfs"
rm "git-lfs-linux-amd64-$LINUX_GIT_LFS_VERSION.tar.gz"
- wget --quiet "$JGITWHENCE" --output-document="$CUSTOM_PATH/jgit"
- chmod a+x "$CUSTOM_PATH/jgit"
+ wget --quiet "$JGITWHENCE" --output-document="$CUSTOM_PATH/jgit" &&
+ chmod a+x "$CUSTOM_PATH/jgit" ||
+ echo >&2 "JGit download failed, but we do not care and keep going"
;;
esac
;;
next reply other threads:[~2025-04-24 22:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 22:13 Junio C Hamano [this message]
2025-04-24 23:10 ` [PATCH] ci: skip unavailable external software Junio C Hamano
2025-04-25 4:19 ` Patrick Steinhardt
2025-04-25 9:49 ` Junio C Hamano
2025-04-25 10:02 ` Patrick Steinhardt
2025-04-25 14:39 ` Junio C Hamano
2025-04-25 12:01 ` Johannes Schindelin
2025-04-25 14:41 ` Junio C Hamano
2025-04-25 15:38 ` [PATCH 0/2] ci: update unavailable external software handling Junio C Hamano
2025-04-25 15:38 ` [PATCH 1/2] ci: update the message for unavailble third-party software Junio C Hamano
2025-04-25 15:38 ` [PATCH 2/2] ci: download JGit from maven, not eclipse.org Junio C Hamano
2025-04-25 14:57 ` repo.eclipse.org outage breaking all our linux CI jobs shejialuo
2025-04-25 15:20 ` Junio C Hamano
2025-04-26 14:12 ` shejialuo
2025-04-28 6:49 ` Patrick Steinhardt
2025-04-28 10:30 ` shejialuo
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=xmqqfrhxtdg9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.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 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).