Skip to content

Enable auto-cancellation on Travis #15878

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

Closed
bashtage opened this issue Apr 3, 2017 · 4 comments
Closed

Enable auto-cancellation on Travis #15878

bashtage opened this issue Apr 3, 2017 · 4 comments
Labels
CI Continuous Integration

Comments

@bashtage
Copy link
Contributor

bashtage commented Apr 3, 2017

Travis has rolled out a new feature (beta) that will automatically cancel builds when a new build appears in a branch. This can help shorten build time when someone commits a small number of small changes to an open PR. This seems like a good feature of have on PRs (but not master) and can help with "push spam".

@jreback

@jreback
Copy link
Contributor

jreback commented Apr 3, 2017

1bcb671

already enabled! (this commit is for putting in our own auto-cancel).

note that you need to enable it on your own branch. I suppose we could document that.

@jreback jreback closed this as completed Apr 3, 2017
@jreback
Copy link
Contributor

jreback commented Apr 3, 2017

actually its on master as well. because if you have an open PR, then you push again, we need and want it to cancel the previous one (on master).

@jreback jreback added the CI Continuous Integration label Apr 3, 2017
@jreback jreback added this to the No action milestone Apr 3, 2017
@bashtage
Copy link
Contributor Author

bashtage commented Apr 3, 2017

There is no way to tell what other repos settings are on Travis, so I though I would check that it was on. Might help a lot.

@jreback
Copy link
Contributor

jreback commented Apr 3, 2017

yeah if you want to create an issue about updating: http://pandas-docs.github.io/pandas-docs-travis/contributing.html#test-driven-development-code-writing

IOW about CI interactions would be fine. (IOW the meaning of 'green' builds and such).

I find newbie are confused by this actually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration
Projects
None yet
Development

No branches or pull requests

2 participants