Issues when deploying a moving tags on a git repo
Reported by Brian Takita | May 2nd, 2008 @ 07:48 PM
On our project, we have a setup where we deploy from the current tag of the lower level environment.
For example, every time our ci build passed, we move a stable_current tag to the passing version.
When we deploy to demo, we deploy from the stable_current tag and move the demo_current tag when successful.
When we deploy from staging, we deploy from the demo_current tag.
And so on.
Unfortunately, capistrano creates a local version of the revision, which causes the next pull to create an ambiguous reference.
I'll try to create a patch soon.
Comments and changes to this ticket
-
Jamis Buck June 2nd, 2008 @ 09:00 PM
- → State changed from “new” to “open”
Is this still an issue? Is a patch still pending? Please update this ticket. Thanks!
-
Brian Takita June 3rd, 2008 @ 01:56 AM
We are using a different strategy now (using timestamped tags), which ends up working better anyways.
This is no longer an issue for us.
-
Jamis Buck June 3rd, 2008 @ 08:18 AM
- → State changed from “open” to “closed”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
