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

Travis: Skip the deploy stage on PRs. #18788

Merged
merged 1 commit into from
Nov 27, 2019

Conversation

epiqueras
Copy link
Contributor

Follows #15159

Avoid dry-running the deploy stage in PRs to get the build time down.

See #17823 (comment).

@epiqueras epiqueras added [Type] Build Tooling Issues or PRs related to build tooling [Type] Performance Related to performance efforts labels Nov 27, 2019
@epiqueras epiqueras added this to the Future milestone Nov 27, 2019
@epiqueras epiqueras self-assigned this Nov 27, 2019
@epiqueras epiqueras requested a review from aduth November 27, 2019 16:45
Copy link
Member

@aduth aduth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@@ -197,7 +197,7 @@ jobs:
- $( npm bin )/wp-scripts test-e2e --config=./packages/e2e-tests/jest.config.js --cacheDirectory="$HOME/.jest-cache" --runTestsByPath $( awk 'NR % 4 == 3' < ~/.jest-e2e-tests )

- stage: deploy
if: branch = master
if: (NOT type IN (pull_request)) AND (branch = master)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could be simpler as...

Suggested change
if: (NOT type IN (pull_request)) AND (branch = master)
if: type IN (push) AND branch = master

Reference: https://docs.travis-ci.com/user/conditions-v1#integration

I don't really know what api and cron are used for, but I doubt we want this stage to run for anything other than push.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

api is for when you trigger a build through the API.

cron is for when a scheduled build runs.

We might have tools that trigger or schedule builds from master in the future and this would support that.

@epiqueras epiqueras merged commit 367c748 into master Nov 27, 2019
@epiqueras epiqueras deleted the try/skipping-the-deploy-stage-on-prs branch November 27, 2019 20:21
@youknowriad youknowriad modified the milestones: Future, Gutenberg 7.1 Dec 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Build Tooling Issues or PRs related to build tooling [Type] Performance Related to performance efforts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants