skip 6.8 branch when triggering baseline-capture builds #72706
Merged
Conversation
This file contains 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
spalger
added
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
brianseeders
approved these changes
Jul 21, 2020
There was a problem hiding this comment.
Sounds good.. if it helps, I started backporting all of the missing pipeline code in 6.8 in #72293 (I got held up by 6.8 being broken, but it looks like it's fixed now)
|
That's a good idea, but we also don't need 6.8 baselines so I plan to leave this in even if we have the ability to capture 6.8 baselines at some point. |
💚 Build SucceededBuild metrics
To update your PR or re-run it, just comment with: |
This was referenced Jul 21, 2020
spalger
added a commit
to spalger/kibana
that referenced
this pull request
Jul 21, 2020
Co-authored-by: spalger <[email protected]>
spalger
added a commit
to spalger/kibana
that referenced
this pull request
Jul 21, 2020
Co-authored-by: spalger <[email protected]>
spalger
added a commit
that referenced
this pull request
Jul 22, 2020
#72740) Co-authored-by: spalger <[email protected]>
spalger
added a commit
that referenced
this pull request
Jul 22, 2020
#72741) Co-authored-by: spalger <[email protected]> Co-authored-by: spalger <[email protected]>
gmmorris
added a commit
to gmmorris/kibana
that referenced
this pull request
Jul 22, 2020
* master: (23 commits) Stabilize closing toast (elastic#72097) stabilize failing test (elastic#72086) Stabilize filter bar test (elastic#72032) Unskip vislib tests (elastic#71452) [ML] Fix layout of anomaly chart tooltip for long field values (elastic#72689) fix preAuth/preRouting mocks (elastic#72663) [Security Solution] Hide KQL bar (all pages) and alerts filters (Detections) when Resolver is full screen (elastic#72788) [Uptime] Rename Whitelist to Allowlist in parse_filter_map (elastic#71584) [Security Solution] Fixes exception modal not loading content (elastic#72770) [Security Solution][Exceptions] - Require non empty entries and non empty string values in exception list items (elastic#72748) [Detections] Add validation for Threshold value field (elastic#72611) [SIEM][Detection Engine][Lists] Adds version and immutability data structures (elastic#72730) [Security Solution][Detections] Validate file type of value lists (elastic#72746) [pre-req] New Component Layout proposal (elastic#72385) [ML] do not throw an error when agg is not supported by UI (elastic#72685) [Resolver] Origin process (elastic#72382) [Ingest Manager] Allow to force unenroll from the UI (elastic#72386) skip 6.8 branch when triggering baseline-capture builds (elastic#72706) [CI] In-progress PR comments (elastic#72211) Fix sorting of scripted string fields (elastic#72681) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The baseline trigger job runs on all tracked branches, and that includes 6.8 right now. We don't actually track baselines for 6.8 and none of the tools necessary to capture them are in that branch. Rather than update the job definition to skip 6.8 it seems a lot simpler to just skip the branch in the trigger job. Thoughts?