Can no longer deploy a specific revision about capistrano-deploytags HOT 9 CLOSED

A workaround is to create a branch and use -s <branchname>

from capistrano-deploytags.

Sorry for not having put this into the readme. This workaround is exactly what we do. I think there is some consideration needed around how to do this better in the plugin. But there are constraints that make it hard to do differently than it is now.

from capistrano-deploytags.

What would happen if the check was bypassed?

from capistrano-deploytags.

One of the problems with that is that if you weren't actually up to date with what is in the repo (assuming you deploy directly from git like most people), you would tag the wrong commit with the deployment tag. You could also be deploying code you don't know changed. Lastly, other plugins like capistrano-detect-migrations rely on the tree being correct.

from capistrano-deploytags.

If that's the only issue, one could skip deploy tagging as well. Probably one would only want that on some kind of staging setup...

from capistrano-deploytags.

So, since the plugin is all about deploy tagging, I'm wondering how you're using it if not for deployment tags? We don't use it for staging, we use it for tracking which code has been deployed to which production server environment, and the capistrano-detect-migrations plugin uses the tags to idenify new Rails migrations.

from capistrano-deploytags.

I have a staging server environment which mirrors production closely (and at times not so closely). capistrano-deploytags tags deploys to that as well, since it's just a multistage environment. Is there a way to configure cap-deploytags to only tag deploys for a subset of multistage envs?

from capistrano-deploytags.

That would be a good feature, but no, not implemented. Pull requests welcome. :)

from capistrano-deploytags.

Closing as there is a known workaround and currently no obvious solution.

from capistrano-deploytags.