search

cake-contrib / Cake.Paket

Adds paket support to cake.
https://cakebuild.net/extensions/cake-paket
MIT License
6 stars 15 forks source link

Add gitreleasemanager to build #11

Closed larzw closed 7 years ago

gep13 commented 7 years ago

@larzw Let me know if you have any questions about getting this added into your build pipeline.

larzw commented 7 years ago

Thanks! I just watched your talk on it 😄 @gep13

gep13 commented 7 years ago

@larzw doh! 😄 Hope you got something out of it. It was the first time that I had given that talk.

larzw commented 7 years ago

@gep13

This is a really cool tool!

I have a question on setting up a fully automated github workflow. Would I only have to checkout a release branch checkout -b release-1.0.0 and push it to github? Then in theory the build triggered from pushing this to github would do the following steps...

  1. Run any pre-release stuff such as generating docs and updating the SolutionInfo.cs
  2. Commit ^ with a commit like "Preparing for release 1.0.0".
  3. Checkout master and merge in the branch release-1.0.0. Then push the changes to github.
  4. Create a tag and push the tag to github.
  5. Run gitreleasemanager
  6. Create and Push Nuget packages.

I've seen people use tags to trigger releases. Would that be better in this case? If so what would the workflow look like?

Thanks!

larzw commented 7 years ago

@gep13,

I was messing around with triggering builds using tags. I think I like this method better. These are my steps. Any comments? I'm pretty sure something like Cake.Recipes would help me out. I'll probably mess around with that next, but wanted to better understand the process.

Thanks!

gep13 commented 7 years ago

@larzw Great to hear that you like it :+1:

What you have there is essentially what I do yes. Within Cake.Recipe, this is what we do:

https://cake-contrib.github.io/Cake.Recipe/docs/usage/creating-release

We don't create the tag manually, but rather, use the GitHub UI to do that work.