-
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
feat: add a new step to run the e2e tests for certain parts of Beats #21100
Merged
Merged
Changes from 2 commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
8374b73
feat: add a new step to run the e2e tests for certain parts of Beats
mdelapenya feebd7b
chore: do not include heartbeat
mdelapenya 7954ecd
feat: trigger the e2e tests
mdelapenya dbab960
fix: use relative path
mdelapenya ccfff57
chore: use proper target branch name for PRs
mdelapenya 5538991
chore: use different tag
mdelapenya 531833b
fix: use proper env variable
mdelapenya ada4771
chore: pass github checks context to downstream job
mdelapenya 89fb374
chore: revert shared lib version
mdelapenya f5d8615
chore: add BASE_DIR env variable
mdelapenya 56d8593
chore: remove duplicated env
mdelapenya f031bc2
ffix: add param comma separator
mdelapenya 7c8bc9c
fix: wrong copy&paste
mdelapenya 04b787b
chore: move e2e GH check out of the release context
mdelapenya 8442279
chore: simplify conditional logic
mdelapenya 132de4b
chore: refine execution of test suites
mdelapenya b6e34d2
fix: use proper parameter name
mdelapenya 93ddff7
chore: set metricbeat version
mdelapenya 7be604f
chore: remove slack notifications on PRs
mdelapenya de2445b
chore: update parameter
mdelapenya 1271296
chore: run multiple test suites per beat type
mdelapenya File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we are running the tests too early. Let me explain: as we are building different projects in parallel (i.e. metricbeat and filebeat) it could be possible that if the filebeat build is faster, then it reaches the e2e tests stage when the filebeat one has not created its artifacts. Therefore the e2e tests could potentially fail.
I could see it valid to run the e2e tests right after the release stage, so we ensure all artifacts are there. On the other hand, the tests won't be run until the slowest build hadn't finished.
As we discussed, it could be great to decide what to build in an earlier stage, something like prepareBuildContext or similar, where we calculate what to build to be tested.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if the step pushCIDockerImages() is finish the packages are generated and deployed, I not get your concern.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, the
pushCIDockerImages
method is executed per BEATS_FOLDER, so in the context ofBEATS_FOLDER=filebeat
it will push the images for filebeat, only. And maybe we want to test the metricbeat ones too (i.e. elastic-agent starting both processes)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is part of the dependencies of the elastic agent, What are the conditions that define if we have to test Filebeat, Metricbeat, or both?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If those are direct dependencies then
beats/Jenkinsfile
Lines 1364 to 1381 in d2a8922
Otherwise, where those dependencies are defined?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not think they are defined yet. I did a best effort here: elastic/e2e-testing#309 (comment)