-
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] run everything for branches/tags #20057
[CI] run everything for branches/tags #20057
Conversation
This reverts commit f652889.
See https://issues.jenkins-ci.org/browse/JENKINS-56500 ``` 15:05:00 org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: 15:05:00 General error during class generation: Method code too large! 15:05:00 15:05:00 java.lang.RuntimeException: Method code too large! 15:05:00 at groovyjarjarasm.asm.MethodWriter.a(Unknown Source) ```
…1v/beats into feature/ci-branches-run-all-by-default * 'feature/ci-branches-run-all-by-default' of github.com:v1v/beats: [CI] run everything for branches/tags
This reverts commit f652889.
This reverts commit f666119.
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
…-basis-when * upstream/master: [CI] run everything for branches/tags (elastic#20057) Limit the number of bytes read by LineReader in Filebeat (elastic#19552) Prefer testify.Error/NoError over NotNil/Nil (elastic#20044)
What does this PR do?
Configure the CI pipeline to run everything by default for all the branches/tags.
Pull Requests, will behave as used to be, only if the changes are related to a particular beat.
Why is it important?
Ensure the CI builds for the branches are running everything smoothly.
Related issues
Closes #19752
Further notes
I initially used the when condition in each stage to enable the condition for no PRs based, see f652889, but I've got hit with