New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
images: use /usr/bin/env bash instead of /bin/bash #25558
Conversation
Approved the image builder workflow (needed to rebuild runtime/builder base images required for changes to Docs https://docs.cilium.io/en/v1.13/contributing/development/images/#update-cilim-builder-runtime-images |
This commit switch most usage of "/bin/bash" to "/usr/bin/env bash". This allows to conform to the PATH env variable when invoking bash which is especially important on distros/installs in which bash is NOT installed in /bin/bash. This is a followup commit after PR cilium#24948 / commit 2c367de that specifically targets shebang in images folder. Signed-off-by: Arthur Outhenin-Chalandre <arthur@cri.epita.fr>
Signed-off-by: Arthur Outhenin-Chalandre <arthur@cri.epita.fr>
Hmm I am not sure what I did wrong but last time it didn't generate sha256 for some reasons and the build/push job was not happy about that... Now it should be fine hopefully, could you reapprove the build job please @gandro 🙈 🙏 |
/test |
Hmm should I rebase for the travis test that timed out and the other tests not launching? |
We did have a recent Jenkins outage, the failing I'll also restart Travis manually. Previous run (timeout) https://github.com/cilium/cilium/pull/25558/checks?check_run_id=13659112030 |
/test Job 'Cilium-PR-K8s-1.26-kernel-net-next' failed: Click to show.Test Name
Failure Output
Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next/124/ If it is a flake and a GitHub issue doesn't already exist to track it, comment Then please upload the Jenkins artifacts to that issue. |
The net-next failure is #25605 and not caused by this PR. |
Travis is hitting #25272 which is also currently a known issue. Edit: Unfortunately I cannot restart it. But since the |
Relevant CI passed (or has known flakes) and the image build (which executes the script here) was successful in the critical phase: https://github.com/cilium/cilium/actions/runs/5025428977/jobs/9012381931 The "Push change to PR" stage failed because the source branch here is on a fork. @MrFreezeex manually pushed the changes to the PR in commit 2ce3e1b - which looks identical to what CI was pushing. This is also partially confimred by the follow-up run, which is green: https://github.com/cilium/cilium/actions/runs/5045936115/jobs/9050828649 I'm marking this ready to merge. |
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXX
line if the commit addresses a particularGitHub issue.
Fixes: <commit-id>
tag, thenplease add the commit author[s] as reviewer[s] to this issue.
Fixes: #issue-number