Add hacking/shippable/incidental.py script. #68182
Conversation
ansibot
added
affects_2.10
| Reducing incidental test coverage, and eventually removing incidental tests involves the following process: | ||
|
|
||
| 1. Run the entire test suite with code coverage enabled. | ||
| This is done automatically each day on Shippable. |
There was a problem hiding this comment.
Is there an easy way for someone to determine the run number for this nightly run?
There was a problem hiding this comment.
You can look at the run history for a given branch and look for the most recent run triggered by the shipabull user. Here's the link for devel:
https://app.shippable.com/github/ansible/ansible/runs?branchName=devel
Until development resumes on devel you'll want to look at temp-2.10-devel instead:
https://app.shippable.com/github/ansible/ansible/runs?branchName=temp-2.10-devel
However, it's likely that the run has failed results, so you'll need to re-run the failed jobs. However, those will show up as triggered by the user who restarted them, which means multiple people trying to go through this process on the same day may each end up re-running the failed jobs.
Unfortunately there's not an easy way to deal with this currently. It should be possible to create a script using the Shippable API to find the latest nightly run, taking into account re-runs, so you'll know which one to use.
mattclay
removed
the
needs_triage
* Add hacking/shippable/incidental.py script. * Add README.md.
SUMMARY
Add hacking/shippable/incidental.py script and README.md to hacking/shippable/ directory.
ISSUE TYPE
Feature Pull Request
COMPONENT NAME
hacking/shippable/incidental.py