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

Restrict continuous-integration/travis-ci/push to only the master branch #50

Closed
igalic opened this issue Dec 23, 2015 · 4 comments
Closed

Comments

@igalic
Copy link
Contributor

igalic commented Dec 23, 2015

as per voxpupuli/puppet-archive#102 (comment)

@rnelson0
Copy link
Member

Bump. Does anyone have objections to adding this to the default .travis.yml?

@ffrank
Copy link
Contributor

ffrank commented Sep 14, 2016

👍 make it so

@igalic
Copy link
Contributor Author

igalic commented Oct 14, 2016

done?

@rski
Copy link
Member

rski commented Dec 2, 2016

Right now there is 2x the builds for modulesync, one for the msync branch and one for the PR opened. This is a waste that costs us a lot of time waiting for CI, we should do this.

@rski rski self-assigned this Dec 2, 2016
rnelson0 added a commit that referenced this issue Dec 2, 2016
Fixes #50

This restricts TravisCI to build all PRs and pushes/merges to the branch master (including tags), no other branches will have CI builds. The primary goal is to stop double builds on PRs (one push, one pr).
@rski rski removed their assignment Dec 2, 2016
rnelson0 added a commit that referenced this issue Dec 2, 2016
Fixes #50

This restricts TravisCI to build all PRs and pushes/merges to the branch master (including tags), no other branches will have CI builds. The primary goal is to stop double builds on PRs (one push, one pr).
rnelson0 added a commit that referenced this issue Dec 2, 2016
Fixes #50

This restricts TravisCI to build all PRs and pushes/merges to the branch master (including tags), no other branches will have CI builds. The primary goal is to stop double builds on PRs (one push, one pr).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants