I have been looking at the docs and also trying out various experimental changes with the .travis.yml file in order to toggle my builds based on if there have been code-related changes in a project or it’s just documentation related changes.
So far the issue isn’t as urgent as it might get in time when more developers push and create PRs, all those users who haven’t made changes have to unfairly wait for previous builds to finish especially if those previous builds are triggered by non-code related changes.
We have put up a solution to check for this in the
before_install directive and it then skips the build with the help of an
But it still takes 30-40 seconds before the PR is released from build. Subsequent commits and PRs are waiting in the queue. We think this can be improved further if we didn’t trigger the TravisCI VM’s, and were able to do the same checks at the github hook level. We want to optimise it further than in a few seconds we can see if our PR needs a CI/CD build or not.
Any thoughts or ideas about this? Has someone solved this already - sounds like a common issue others might have as well.