-
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
action: checks for x-pack/osquerybeat #32753
Merged
v1v
merged 3 commits into
elastic:main
from
v1v:feature/check-actions-osquerybeat-modules
Aug 24, 2022
Merged
action: checks for x-pack/osquerybeat #32753
v1v
merged 3 commits into
elastic:main
from
v1v:feature/check-actions-osquerybeat-modules
Aug 24, 2022
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
v1v
added
automation
Team:Automation
Label for the Observability productivity team
backport-7.17
Automated backport to the 7.17 branch with mergify
backport-v8.4.0
Automated backport with mergify
labels
Aug 22, 2022
botelastic
bot
added
needs_team
Indicates that the issue/PR needs a Team:* label
and removed
needs_team
Indicates that the issue/PR needs a Team:* label
labels
Aug 22, 2022
Collaborator
v1v
commented
Aug 23, 2022
v1v
commented
Aug 23, 2022
cmacknz
approved these changes
Aug 23, 2022
mergify bot
pushed a commit
that referenced
this pull request
Aug 24, 2022
(cherry picked from commit 690783f) # Conflicts: # x-pack/osquerybeat/Jenkinsfile.yml
mergify bot
pushed a commit
that referenced
this pull request
Aug 24, 2022
(cherry picked from commit 690783f)
v1v
added a commit
that referenced
this pull request
Aug 24, 2022
v1v
pushed a commit
that referenced
this pull request
Aug 25, 2022
chrisberkhout
pushed a commit
that referenced
this pull request
Jun 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
automation
backport-7.17
Automated backport to the 7.17 branch with mergify
backport-v8.4.0
Automated backport with mergify
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?
Use GitHub actions to run the
check stage
forx-pack/osquerybeat
What's the
check stage
?mage check
mage update
Why is it important?
Faster builds by running linting/checks outside of the main CI Pipeline.
Errors
Further details
The existing checks in Jenkins are replaced with GitHub checks, hence the union of these 2 new Github workflows substitutes each former check. Therefore, the same commands will run for the same scenarios.
Results
Nearly 10 minutes since they build was triggered in Jenkins and still waiting for workers to be assigned, while the new GitHub checks finished relatively much faster
Related issues
Similar to #32711