Build problem and duplicate releasesPublish date: 15 Aug 16
Yesterday I went to investigate a problem someone had reported only to discover a butt load of releases
As you can see, I have more releases then commits. A build was triggered by a commit, but this doesn’t explain why.
I tried switching it up so it only builds when you put [build] in the commit message – which resulted in having to commit the yaml file as the feature isn’t available via the web interface, it does make sense to have this under version control. However it continued to loop.
Looking at the build history revealed it was looping, per commit
An email off to support resulted in speedy response.
Add “skip_tags: true” to your appveyor.yml.
-Feodor Fitsner, AppVeyor
Bingo. It was looping because I create a GitHub release for each build and tag the release. Which was then causing a build, which created a release that then got tagged, which created a release…
I’m grateful I’m not paying per build! Hopefully this will serve as a warning for others.
I’ve started to remove the releases but I’ve hit the API limit last night. Hopefully I’ll clean up my PowerShell script to deal with it, failing that I may have to rely on the kindnesses of GitHub human.
“I have always depended on the kindness of strangers.”
– Blanche DuBois
I’ve managed to remove the duff tags as well and SIMS Bulk Import is down to two releases on GitHub. I’ve been slightly heavy handed when it came to deleting. Thankfully all the duff releases where pre-release so the problem wasn’t as bad is it could have been.
Below is the PowerShell script I quickly knocked together, the tags I did over lunch at work, thus the proxy bit – note that isn’t our actual proxy address 😉