[wp-trac] [WordPress Trac] #38500: Automatically cancel pending Travis builds with each commit
WordPress Trac
noreply at wordpress.org
Tue Oct 25 23:28:16 UTC 2016
#38500: Automatically cancel pending Travis builds with each commit
------------------------------+------------------------------
Reporter: johnbillion | Owner:
Type: task (blessed) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Build/Test Tools | Version:
Severity: normal | Resolution:
Keywords: | Focuses:
------------------------------+------------------------------
Comment (by jeremyfelt):
One reason it's nice to have a full build for each commit is so that we
know when a failing test was introduced. If we cancelled pending jobs,
we'd be okay most of the time. Every once and a while we may find
ourselves tracking things down.
Other thoughts:
* Can we set our tests to stop on failure instead of continuing to process
the remainder?
* Is there a way we can cancel remaining jobs inside a build if more than
1 job fails?
* Can we reduce the number of PHP versions we test against? How often has
something failed on 5.3/4/5 and passed on 5.2/6 and 7?
Of course, things run mostly concurrent right now, so some of those may
not help at all. Especially when the biggest slow down is waiting for
everything to pass.
Interesting reading: https://www.drupal.org/drupalorg/blog/drupalci-
continuous-integration-testing-for-drupalorg
We are kind of stretching the bounds of free Travis server power.
This is probably a meta topic. :)
--
Ticket URL: <https://core.trac.wordpress.org/ticket/38500#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list