-
Notifications
You must be signed in to change notification settings - Fork 30
Added setting CI Action and CI job id custom values on github action builds #409
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
Conversation
| addCustomValueAndSearchLink(develocity, "CI run", value)); | ||
| envVariable("GITHUB_HEAD_REF", providers).filter(value -> !value.isEmpty()).ifPresent(value -> | ||
| buildScan.value("PR branch", value)); | ||
| envVariable("GITHUB_ACTION", providers).ifPresent(value -> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick, but I'd group all of the env vars together that produce a value + link. In other words, I'd have the GITHUB_HEAD_REF logic last in this code block.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@clayburn done
… improved code grouping
dbe67b5 to
443dd19
Compare
Added setting CI Action and CI job id custom values on github action builds. This is an example GHA builds (the
buildscan), with the scan having two custom values (and search links) added: CI job id and CI step id. This will be helpful when you've got multiple builds running consecutively and are passing in arguments that affect those builds, but are not captured in a build scan (best example are Maven profiles for CCUD Maven).When this is accepted I will do the same for CCUD Maven (and sbt).
Closes #389.