Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Publish releases directly from Travis after applying a tag #3060
In the light of the current problems with metadata in 3.3 and in the interest of making the releases even easier, I would like for us to move to a "publish on tag" method which we have been applying successfully in a number of pytest plugins (notably
I propose to change our release process to:
Notably missing from the current approach is using
Further @jaraco and a few others use this approach successfully, which gives me further confidence.
This is not fully automated yet, but I believe is a step in that direction nonetheless.
i was also intending to automate it in the following way
a) have pytestbot publish those regendoc executed branches to the pytest repo (because pushing tags to a pr only really works when we do it on the main repo)
By opening a PR you mean? Yeah that sounds like a plan. I was thinking this should be triggered by any merge to
We could have an app running somewhere that receives a merge event via webhooks, and then clones pytest/creates virtualenv/runs invoke regen/pushes a PR against the merged branch.
@conda-forge has a bot running in Heroku which does similar things (they listen for specific comments like
Actually it works, I've done this a few times already: by pushing the tag, you also push the PR's commits to the main repository.
I see what you mean, but I would like to follow with just using Travis deploy tool for now; I understand it may fail to deploy and still pass, but the worst outcome of that (while annoying) is just having to make a upload manually. Having a new invoke task for that seems like a good addition, but shouldn't block the main proposal here IMHO.
In summary I definitely like your ideas (they actually match what I had in the back of my mind for some time as well), but would like to implement what I mention in the initial post soon because it will simplify our deployment process at a very low cost. Your other suggestions are definitely a nice follow up.