-
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] disable aws cloud testing by default #23186
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
and removed
needs_team
Indicates that the issue/PR needs a Team:* label
labels
Dec 16, 2020
Collaborator
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
Test | Results |
---|---|
Failed | 0 |
Passed | 17805 |
Skipped | 1385 |
Total | 19190 |
kuisathaverat
approved these changes
Dec 17, 2020
cachedout
approved these changes
Dec 28, 2020
cachedout
approved these changes
Dec 28, 2020
v1v
commented
Jan 6, 2021
v1v
added
aws
Enable builds in the CI for aws cloud testing
and removed
aws
Enable builds in the CI for aws cloud testing
labels
Jan 6, 2021
v1v
added a commit
to v1v/beats
that referenced
this pull request
Jan 7, 2021
* Disable by default, and added the labels/parameters/comments configuration to be customised on a PR basis if required * Created a weekly job to run AWS cloud testing for master and 7.x branches
v1v
added a commit
to v1v/beats
that referenced
this pull request
Jan 7, 2021
* Disable by default, and added the labels/parameters/comments configuration to be customised on a PR basis if required * Created a weekly job to run AWS cloud testing for master and 7.x branches
v1v
added a commit
to v1v/beats
that referenced
this pull request
Jan 7, 2021
* Disable by default, and added the labels/parameters/comments configuration to be customised on a PR basis if required * Created a weekly job to run AWS cloud testing for master and 7.x branches
v1v
added a commit
that referenced
this pull request
Jan 7, 2021
v1v
added a commit
that referenced
this pull request
Jan 7, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
automation
aws
Enable builds in the CI for aws cloud testing
ci
Team:Automation
Label for the Observability productivity team
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?
Run Cloud Testing on demand using the UI, comments or labels or on a weekly basis for the
master
and7.x
branches.Triggers:
awsCloudTests
/test x-pack/metricbeat for aws cloud
aws
Why is it important?
Cloud Testing got a limitation with the number of db instances concurrently with the current service account used in the CI
The quotas and limitations can be found in the limits section.
Issues
See #23105 (comment)
cc @jsoriano and @ph as you commented in #23105 (comment)