I’ve kinda worked around this by having a parent build that triggers a new matrix build based on the touched files in the TRAVIS_COMMIT_RANGE. It’s fairly hacky since the API doesn’t support triggering a specific commit, but it works for now: Trigger a specific commit via the Travis API
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Trigger a specific commit via the Travis API | 2 | 2233 | August 16, 2019 | |
| Conditional build without triggering TravisCI VMs | 3 | 1340 | November 20, 2019 | |
| Travis CI to modify same branch (may have to use git stash pop) | 1 | 540 | October 21, 2020 | |
|
TRAVIS_COMMIT is not the commit initially checked out
|
7 | 3674 | December 13, 2020 | |
| Pull request builds checkout wrong commits | 0 | 668 | May 22, 2019 |