Summary
In order to save time for pull request builds and save travis resources, I suggest to reduce the number of builds on travis and azure.
Detailed Explanation
At this point we have 9 different travis configuration build for each pull request. This appears to me as overkill. We just want to know if there was nothing obviously broken. More thorough testing will occur on the master branch.
Drawbacks, Rationale, and Alternatives
Occasionally a build on master will fail, so this is a drawback, but I think the time / electrical energy saved is worth it.
Unresolved Questions
- Which builds to keep, which to delete?
- Should we use only azure with macOS/windows/linux builds?
Summary
In order to save time for pull request builds and save travis resources, I suggest to reduce the number of builds on travis and azure.
Detailed Explanation
At this point we have 9 different travis configuration build for each pull request. This appears to me as overkill. We just want to know if there was nothing obviously broken. More thorough testing will occur on the master branch.
Drawbacks, Rationale, and Alternatives
Occasionally a build on master will fail, so this is a drawback, but I think the time / electrical energy saved is worth it.
Unresolved Questions