Travis CI - Improvements

[pradyunsg]

Are the pip developers comfortable with using Travis CI beta features?

---

There are 2 Travis CI features in public beta right now - Build Stages and Auto Cancellation. I think these can be used to cause fast failing and potentially reduce the build queue times.

With Build Stages, I'd imagine there would be the following stages (in this order):

• unit tests
• integration tests
• pep8 + documentation + packaging

This would nearly double the number of jobs run since currently unit tests and integration tests are run in the same job.

Edit: I just tried it out and I don't think this is useful for pip's CI usage.

Auto Cancellation is definitely a win regardless of whether Build Stages are useful for pip.

---

(edited to condense multiple posts into 1)

[pradyunsg]

Also, what are your thoughts on running tests verbose (pytest -v)?

[xavfernandez]

• Build stages 👍
• Auto cancel seems like a good idea for pull request builds but I'd rather still have a build for each commit/merge on master
• Concerning pytest -v I'm 👍 also :)

[dstufft]

I've already got auto cancellation turned on (though I have it turned on for both branches and PRs, largely because our tests take forever). I agree that I don't think that build stages are incredibly useful for pip. As far as pytest -v goes, I am neutral on it. I am happy to have it go either way.

[pradyunsg]

Cool. I'll make a PR for adding a -v. XD

[pradyunsg]

Oh, one last thing - @dstufft: currently pull requests titles are modified to add the Reviewable tag through your account. It would look nicer if pypa-bot did it. :)

And since I think there's nothing actionable left, I'll close this issue.

[dstufft]

What reviewable tag?

[pradyunsg]

The edit to add "This change is reviewable" - Does anyone even use that?

[dstufft]

I thought I turned that off, turned it off for real now.

[pradyunsg]

Now, I think I'm just gonna use this issue for random questions about CI I have. Is there a better channel/place to do that?

---

Thoughts on enforcing import order using an additional tox job - using isort?

[pradyunsg]

Thoughts on enforcing import order using an additional tox job - using isort?

I just opened #4481.

[pradyunsg]

I'm opening this back up. I'll use this to as a place to ask CI questions as long as I'm working on #4497.

[pradyunsg]

Thoughts on adding Jython testing on Travis CI and AppVeyor?

I think it'd have to be clone, install then do the testing but it seems be do-able and I think it'll might worthwhile to do so.

[pradyunsg]

Thoughts on skipping a CI test-run if a commit-set does not touch any file within pip/ or tests/?

FWIW, cpython does it.

[pradyunsg]

I guess making new issues is easy enough. :P

[pradyunsg]

Thoughts on skipping a CI test-run if a commit-set does not touch any file within pip/ or tests/?

Opened #5185.

Thoughts on adding Jython testing on Travis CI and AppVeyor?

There's #3044 already.

[pfmoore]

Note that Jython is not a supported target for pip (and I think there's at least one issue that we closed unfixed because we weren't able to support the quirk of Jython that triggered the problem).

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.