-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[CI] Mandatory windows support for all the versions #23615
Merged
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
botelastic
bot
added
needs_team
Indicates that the issue/PR needs a Team:* label
Team:Automation
Label for the Observability productivity team
Team:Ingest Management
labels
Jan 21, 2021
Pinging @elastic/ingest-management (Team:Ingest Management) |
botelastic
bot
removed
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
Jan 21, 2021
Collaborator
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
/test |
mdelapenya
approved these changes
Jan 25, 2021
Linting caused by another PR that did not change the x-pack, and test failure unrelated to this changes. |
cachedout
approved these changes
Jan 25, 2021
Co-authored-by: cachedout <mike.place@elastic.co>
/test |
1 similar comment
/test |
v1v
added a commit
to v1v/beats
that referenced
this pull request
Jan 26, 2021
v1v
added a commit
to v1v/beats
that referenced
this pull request
Jan 26, 2021
v1v
added a commit
to v1v/beats
that referenced
this pull request
Jan 26, 2021
…pack-when-oss-changes * upstream/master: [DOCS] Add setup content to Kubernetes and Cloud Foundry docs (elastic#23580) [CI] Mandatory windows support for all the versions (elastic#23615) Add check when retrieving the worker process id using performance counters (elastic#23647) Remove 4912 evtx from testing (elastic#23669) Add missing SSL settings (elastic#23632) Update X-Pack Packetbeat config (elastic#23666) Use hostname check from verify.go to handle patterns in TLS certs (elastic#23661) Fix: Dissect Cisco ASA 302013 message usernames (elastic#21196) Add FAQ entry for MADV settings in older versions (elastic#23429) Sync fixes from Integration Package Testing (elastic#23424) [Filebeat] Add Cisco ASA message '302023' parsing (elastic#23092) [Elastic Log Driver] Change hosts config flag (elastic#23628) Audit and Authentication Policy Change Events (elastic#20684)
v1v
added a commit
that referenced
this pull request
Jan 27, 2021
v1v
added a commit
to v1v/beats
that referenced
this pull request
Jan 27, 2021
v1v
added a commit
that referenced
this pull request
Jan 27, 2021
v1v
added a commit
that referenced
this pull request
Jan 27, 2021
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
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.
What does this PR do?
Mandatory stages in the CI for older windows versions on a PR basis, similar to what it runs on
master/7.x/7.[0-9]+
Why is it important?
Discover incompatibility issues earlier rather than when merged.
Further details
Jenkinsfile.yml
supports stages with multiple platforms, if we use that approach then the test output format will change and might affect the Test Dashboards regarding the top-10 failures or the flakiness analysis.If we do so, we might need to run some migration.