[CI] Tag es-pr-check serverless build scans with original PR #136257
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
breskeby
added
>non-issue
:Delivery/Build
Collaborator
|
Pinging @elastic/es-delivery (Team:Delivery) |
jozala
requested changes
Oct 9, 2025
Contributor
jozala
left a comment
jozala
left a comment
There was a problem hiding this comment.
One issue with the fixed address found to be fixed.
I'm also wondering if that's something serverless specific what maybe could be moved to the serverless repo. WDYT?
| value 'Git Commit ID', esCommit | ||
| tag "pr/${esPr}" | ||
| tag 'pull-request' | ||
| link 'Source', "https://github.com/jfreden/elasticsearch/tree/${esCommit}" |
Contributor
There was a problem hiding this comment.
The "source" link should dynamically point to the commit in the PR source repo.
However, I'm not sure we can get the PR source as BUILDKITE_PULL_REQUEST_REPO is empty in the es-pr-check builds I've checked.
Contributor
Author
There was a problem hiding this comment.
good catch. I changed it to just point to the commit in the context of the PR
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Oct 9, 2025
…#136257) These are serverless builds that run in the context of an elasticsearch PR. Therfore we want to keep the context in the generated build scans.
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Oct 9, 2025
…#136257) These are serverless builds that run in the context of an elasticsearch PR. Therfore we want to keep the context in the generated build scans.
This was referenced Oct 9, 2025
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Oct 9, 2025
…#136257) These are serverless builds that run in the context of an elasticsearch PR. Therfore we want to keep the context in the generated build scans.
Collaborator
💔 Backport failed
You can use sqren/backport to manually backport by running |
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 9, 2025
#136277) These are serverless builds that run in the context of an elasticsearch PR. Therfore we want to keep the context in the generated build scans.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 9, 2025
#136276) These are serverless builds that run in the context of an elasticsearch PR. Therfore we want to keep the context in the generated build scans.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 9, 2025
#136278) These are serverless builds that run in the context of an elasticsearch PR. Therfore we want to keep the context in the generated build scans.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.