Add AWS tests to Jenkinsfile #17480
Merged
Add AWS tests to Jenkinsfile #17480
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
jsoriano
added
in progress
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
jsoriano
force-pushed
the
aws-jenkins
branch
4 times, most recently
from
9790c08
to
886e437
Compare
jsoriano
force-pushed
the
aws-jenkins
branch
2 times, most recently
from
effca4c
to
38f9405
Compare
|
jenkins, test this |
|
jenkins, test this please |
jsoriano
force-pushed
the
aws-jenkins
branch
8 times, most recently
from
fd5503c
to
221c4c8
Compare
|
jenkins, test this |
jsoriano
force-pushed
the
aws-jenkins
branch
7 times, most recently
from
95557cb
to
86da3ac
Compare
kuisathaverat
approved these changes
Apr 28, 2020
|
|
kaiyan-sheng
approved these changes
Apr 28, 2020
exekias
approved these changes
Apr 29, 2020
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
This was referenced Apr 30, 2020
Merged
Modules that don't define a local environment with docker compose or kubernetes (kind) are not being executed. Fall back to the old default of docker in that case.
jsoriano
added a commit
to jsoriano/beats
that referenced
this pull request
May 4, 2020
Add execution of AWS integration tests for Metricbeat to Jenkinsfile. For that, a simple terraform scenario is created that seems to be enough to pass the AWS module tests, this scenario is started by Jenkins, and destroyed as a cleanup step. With this approach terraform scenarios are defined per module, this is consequent with other efforts we are doing with other integrations, where integration test scenarios are defined at the module level. Similar approach will be possibly followed for input integration tests. Most of the logic is added in the Jenkinsfile and as scripts. Some things could be moved to mage when we modify our targets to start scenarios depending on the type of provisioner. Some parts are going to continue being needed in Jenkinsfile in my opinion, as the archive of Terraform states for manual cleanups. (cherry picked from commit c94d4bf)
10 tasks
jsoriano
removed
the
needs_backport
jsoriano
added a commit
that referenced
this pull request
May 4, 2020
Add execution of AWS integration tests for Metricbeat to Jenkinsfile. For that, a simple terraform scenario is created that seems to be enough to pass the AWS module tests, this scenario is started by Jenkins, and destroyed as a cleanup step. With this approach terraform scenarios are defined per module, this is consequent with other efforts we are doing with other integrations, where integration test scenarios are defined at the module level. Similar approach will be possibly followed for input integration tests. Most of the logic is added in the Jenkinsfile and as scripts. Some things could be moved to mage when we modify our targets to start scenarios depending on the type of provisioner. Some parts are going to continue being needed in Jenkinsfile in my opinion, as the archive of Terraform states for manual cleanups. (cherry picked from commit c94d4bf)
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?
Add execution of AWS integration tests for Metricbeat to Jenkinsfile. For that, a simple terraform scenario is created that seems to be enough to pass the AWS module tests, this scenario is started by Jenkins, and destroyed as a cleanup step. With this approach terraform scenarios are defined per module, this is consequent with other efforts we are doing with other integrations, where integration test scenarios are defined at the module level. Similar approach will be followed for input integration tests.
Most of the logic is added in the Jenkinsfile and as scripts. Some things could be moved to mage when we modify our targets to start scenarios depending on the type of provisioner. Some parts are going to continue being needed in Jenkinsfile in my opinion, as the archive of Terraform states for manual cleanups.
Summary of changes:
s3_request, see note below).Why is it important?
To be able to run AWS-related Metricbeat integration tests in Jenkins.
Pending for the future
s3_requestmetricset doesn't pass only by creating S3 buckets, we may need to make some requests to this bucket? I am skipping it by now.mageTargetcleans up the environment and only has a clean working copy of the code. This can be needed if we want to check for the metrics of an specific resource, or we want to collect logs from an specific endpoint. There are two approaches for that:mageTargetso it is possible to unstash more things apart of the source.mageTarget. We may still need to stash/archive the terraform state for cleanups or sharing the environment between stages.Checklist
I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
Related issues