Skip to content
This repository has been archived by the owner on Oct 28, 2024. It is now read-only.

Support skip-ci-build label for beatsWhen #733

Merged
merged 1 commit into from
Sep 29, 2020

Conversation

v1v
Copy link
Member

@v1v v1v commented Sep 28, 2020

What does this PR do?

Support the scenario:

As a contributor I want my PR to be skipped in the CI when I configured it with a github label.

Important

Talking more precisely for Beats this change won't affect the Lint stage since it runs always before the mono-repo stage dynamic generation that happens when using beatsWhen and beatsStages

Why is it important?

Provide fine granularity to configure the builds based on the user expectations too

Related issues

Caused by elastic/beats#20104

@v1v v1v self-assigned this Sep 28, 2020
@v1v v1v added the automation label Sep 28, 2020
@apmmachine
Copy link
Contributor

💚 Build Succeeded

Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: [Pull request #733 opened]

  • Start Time: 2020-09-28T14:03:20.266+0000

  • Duration: 8 min 23 sec

Test stats 🧪

Test Results
Failed 0
Passed 813
Skipped 9
Total 822

Steps errors

Expand to view the steps failures

  • Name: Archive JUnit-formatted test results
    • Description: [2020-09-28T14:06:14.181Z] Recording test results
      [2020-09-28T14:06:14.404Z] Failed to read /var/li

    • Duration: 0 min 0 sec

    • Start Time: 2020-09-28T14:06:14.172+0000

    • log

@v1v v1v marked this pull request as ready for review September 28, 2020 14:18
@v1v v1v added the enhancement New feature or request label Sep 28, 2020
@v1v v1v requested a review from a team September 28, 2020 14:19
@botelastic botelastic bot added the groovy label Sep 28, 2020
@v1v v1v merged commit 6ad6ed6 into elastic:master Sep 29, 2020
@v1v v1v deleted the feature/support-skip-label-builds branch September 29, 2020 11:04
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants