Filter deploy based on Tag/TagName and pre-release status

[ramblingcookiemonster]

Filter deploy based on Tag/TagName and pre-release status

[RamblingCookieMonster]

Hello!

Interesting question - you could likely gate calling PSDeploy (or a particular deployment or deployment tag) based on APPVEYOR_REPO_TAG and APPVEYOR_REPO_TAG_NAME

Now that you mention it, I'll likely try to abstract those into BuildHelpers (e.g. BHTagName which would grab CI_COMMIT_TAG from GitLab CI, APPVEYOR_REPO_TAG_NAME from AppVeyor) - thanks for the idea : )

Might have just gone over my head, but how are you flagging something as a pre-release? via a particular version number? something in the tag name?

Cheers!

[seanmcne]

Thanks for the super quick response!

When you create a release on github there's a checkbox (pictured below)

[seanmcne]

Interesting, your appveyor variable names helped me find some content - looks like provider settings contains most of the info:

https://www.appveyor.com/docs/deployment/github/#provider-settings

[seanmcne]

Looking into this a bit more now, is the idea that we'd commit to Master, commit something with !Deploy and then appveyor would be responsible for tagging and releasing as part of the deployment to powershell gallery?

Currently, we commit and commit until we're ready for a release, then we tag and draft a release to github, once we get some feedback or can test, we eventually decide to finalize the release, at that point we push out to powershell gallery (the gallery is always our final destination once we're sure we want the larger audience to easily pull down the update).

[RamblingCookieMonster]

The workflow is totally up to you, but the GitHub release part isn't covered by PSDeploy (yet) - as you notice though, AppVeyor can do that if it makes sense for you.

I work with modules that are pretty simple (from a module and release perspective) - here's my typical workflow:

• All commits end up generating a package on AppVeyor's NuGet feed via psdeploy (e.g.)
• Commits with !Deploy end up deploying to the gallery (e.g. via psdeploy)

That's about it! I don't use tags or GitHub releases for any projects, so never got around to writing a psdeploy script for this... although now that you mention it, might be nice to have that : )

Cheers!

[seanmcne]

Thanks! I did notice there are appveyor project settings to build tags only, I suppose I could just filter on the branch and build tags only though something to filter would be cool too. Thanks again for the quick responses!

[RamblingCookieMonster]

Closing this out! If you have any ideas on things to add, feel free to open it back up - cheers!