Skip to content
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: notify stages in the CI with GitHub checks #1148

Merged
merged 1 commit into from
Feb 16, 2022

Conversation

v1v
Copy link
Member

@v1v v1v commented Feb 15, 2022

What is the problem this PR solves?

Notify build status as GitHub checks for each major stage in the CI

How does this PR solve the problem?

Trying to improve the development experience while contributing to this repository.

@v1v v1v requested a review from a team as a code owner February 15, 2022 15:43
@mergify
Copy link
Contributor

mergify bot commented Feb 15, 2022

This pull request does not have a backport label. Could you fix it @v1v? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v/d./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

@mergify mergify bot added the backport-skip Skip notification from the automated backport with mergify label Feb 15, 2022
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-02-15T15:43:44.200+0000

  • Duration: 16 min 59 sec

Test stats 🧪

Test Results
Failed 0
Passed 260
Skipped 0
Total 260

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@v1v v1v added backport-v8.0.0 Automated backport with mergify backport-v8.1.0 Automated backport with mergify labels Feb 15, 2022
@mergify mergify bot removed the backport-skip Skip notification from the automated backport with mergify label Feb 15, 2022
@v1v v1v merged commit c2f9e50 into elastic:main Feb 16, 2022
mergify bot pushed a commit that referenced this pull request Feb 16, 2022
mergify bot added a commit that referenced this pull request Feb 16, 2022
(cherry picked from commit c2f9e50)

Co-authored-by: Victor Martinez <[email protected]>
@v1v v1v added the backport-7.17 Automated backport to the 7.17 branch with mergify label May 10, 2022
mergify bot pushed a commit that referenced this pull request May 10, 2022
mergify bot pushed a commit that referenced this pull request May 10, 2022
mergify bot added a commit that referenced this pull request May 10, 2022
(cherry picked from commit c2f9e50)

Co-authored-by: Victor Martinez <[email protected]>
v1v added a commit that referenced this pull request May 10, 2022
(cherry picked from commit c2f9e50)

Co-authored-by: Victor Martinez <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-7.17 Automated backport to the 7.17 branch with mergify backport-v8.0.0 Automated backport with mergify backport-v8.1.0 Automated backport with mergify
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants