#9380 enhancement closed wontfix (wontfix)

Configure AppVeyor builds to be skipped for news fragment-only changes

Reported by: Jean-Paul Calderone Owned by:
Priority: normal Milestone:
Component: release management Keywords: continuous-integration appveyor
Cc: Branch:


AppVeyor builds take a long time. It's great to have Windows CI. It's not great to have to wait an hour or more for a complete set of build results.

News fragments can't possibly make any difference to the AppVeyor builds. News fragments get assembled at release time into a news file. Their contents have no other meaning to any part of Twisted. Yet checking in a news fragment change will trigger an AppVeyor build.

AppVeyor configuration supports skipping builds based on the files being changed (<https://www.appveyor.com/docs/how-to/filtering-commits/#commit-files-github-and-bitbucket-only>)

skip_commits.files allows skipping AppVeyor build if all of the files modified in push’s head commit match any of the file matching rules (AND logic applied to multiple values):

Adding such a config section to Twisted's AppVeyor config would reduce CI build time by some non-trivial amount (both directly by avoiding AppVeyor builds sometimes and indirectly be reducing the load on AppVeyor, thus speeding up necessary AppVeyor builds).

Change History (3)

comment:1 Changed 10 months ago by Jean-Paul Calderone

Keywords: review added

comment:3 Changed 10 months ago by Jean-Paul Calderone

Resolution: wontfix
Status: newclosed

Apparently this isn't actually how the AppVeyor feature works. Discussion on the PR.

Note: See TracTickets for help on using tickets.