Skip to content

Auto-port 5.0: Propagate the CI envionment variables through to the docker builds - #17139

Merged
chrisvest merged 1 commit into
5.0from
auto-port-pr-17138-to-5.0
Jul 25, 2026
Merged

Auto-port 5.0: Propagate the CI envionment variables through to the docker builds#17139
chrisvest merged 1 commit into
5.0from
auto-port-pr-17138-to-5.0

Conversation

@netty-project-bot

Copy link
Copy Markdown
Contributor

Auto-port of #17138 to 5.0
Cherry-picked commit: 6e8c31d


Motivation:
TestLens requires this in order to activate its profile. It's possible some of our other tools, e.g. sdkman also make use of this.

Modification:
Add CI to the environments in our docker-compose files.

Result:
We should now get testlens results from our docker-based linux builds.

…17138)

Motivation:
TestLens requires this in order to activate its profile. It's possible
some of our other tools, e.g. sdkman also make use of this.

Modification:
Add `CI` to the environments in our docker-compose files.

Result:
We should now get testlens results from our docker-based linux builds.

(cherry picked from commit 6e8c31d)
@testlens-app

testlens-app Bot commented Jul 25, 2026

Copy link
Copy Markdown

✅ All tests passed ✅

🏷️ Commit: e76de3f
▶️ Tests: 40064 executed
⚪️ Checks: 12/12 completed


Learn more about TestLens at testlens.app.

@chrisvest chrisvest added this to the 5.0.0.Final milestone Jul 25, 2026
@chrisvest
chrisvest merged commit ab041e2 into 5.0 Jul 25, 2026
13 checks passed
@chrisvest
chrisvest deleted the auto-port-pr-17138-to-5.0 branch July 25, 2026 01:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants