Due we have limited macOS resources we will keep then bot the branch merges, and other test. Thus we going to disable the macOS test by default on PRs. However will be possible to execute those test manually, with a comment, or adding a label to the PR.
Manually
Scenario: A developer creates a new PR
When a developer Launch the beats pipeline from Jenkins UI with the parameter macosTest
Then a build is triggered
And the macOS tests are executed
NOTE: Only users with permissions in the CI will be able to login and trigger the build manually using the UI.
GH Label
Scenario: A developer creates a new PR
When a Beat requires macOS test
Then the test is skipped if the build is not labeled as macOS test needed (label macOS)
NOTE: Only users with write permissions in the repo can add labels to the PR. In addition, builds won't be triggered automatically in the even of a label change.
GH Comment
Scenario: A developer creates a new PR
When a developer put the GitHub comment `/test mac` comment
Then a build is triggered
And the macOS tests are executed
cc @elastic/observablt-robots
Due we have limited macOS resources we will keep then bot the branch merges, and other test. Thus we going to disable the macOS test by default on PRs. However will be possible to execute those test manually, with a comment, or adding a label to the PR.
Manually
NOTE: Only users with permissions in the CI will be able to login and trigger the build manually using the UI.
GH Label
NOTE: Only users with
writepermissions in the repo can add labels to the PR. In addition, builds won't be triggered automatically in the even of a label change.GH Comment
cc @elastic/observablt-robots