[chore][internal] Add build & read access to buildkite pipelines for members of integration-experience team#18856
Merged
Conversation
mrodm
approved these changes
May 7, 2026
Collaborator
mrodm
left a comment
mrodm
left a comment
There was a problem hiding this comment.
LGTM.
Just a minor comment about inserting this following the sorted order for BUILD_AND_READ permission.
TIA!!
Comment on lines
+108
to
+109
| integration-experience: | ||
| access_level: BUILD_AND_READ |
Collaborator
There was a problem hiding this comment.
Nit.
To try to keep all the teams using BUILD_AND_READ sorted, could you move this entry after the logstash team entry? Around line 80.
Contributor
Author
There was a problem hiding this comment.
@mrodm Thanks for pointing that out, I agree that it's good to keep things tidy. Will fix !
bhapas
approved these changes
May 7, 2026
Contributor
bhapas
left a comment
bhapas
left a comment
There was a problem hiding this comment.
LGTM.. Just resolve the comment from Mario before push.
…lastic/integrations into chore/buildkite-config-add-team-access
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
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.
Proposed commit message
For members (i.e me) of the integration-experience Github team, pipeline access is limited i.e. read-only, as defined by this general setting. As advised by the platform engineering team, I'm adding build & read permissions to the integration-experience team so we can all read & execute builds.
The main impact here is that if a PR is submitted to a repository we steward, some of our team members would not have access to trigger builds from Buildkite's UI. It would be strictly readonly. This might be helpful in situations where flaky tests occur and we need to re-trigger things (although it would be preferable to fix the problem at the source instead)
Here is the platform engineering documentation reference: https://docs.elastic.dev/ci/getting-started-with-buildkite-at-elastic#2-adjust-your-pipeline-settings, more specifically the
Assigning a Pipeline to Teamscollapsible section (which I cannot provide a URL to unfortunately)It's possible we have other repositories impacted by this but I'm seeing if this will fix it here and will open PRs in other repositories we steward afterwards.
How to test this PR locally
N/A