Loading Profile...
Is it possible to force-release a revision?
I would like to force-release a revision. For instance, I just changed the host details of my Production server and I want to deploy everything over ftp to the new server. Beanstalk already has updated the old server with the latest revision so now I'm forced to make a new revision in the repository to re-release everything to the new server.
Thanks in advance for your answer :)
Thanks in advance for your answer :)
I’m confident
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Michiel,
From Setup > Releases > Production server, You can switch temporary to a manual upload, and deploy the revision using the Beanstalk interface. After the release is deployed, you can switch back to automatic mode.
Alternatively, a dummy commit will also re-release.
Hope this helps,
Petyo -
Inappropriate?Hi Petyo,
Thank you very much for your quick response. The point is that the deployment method was already set to manual so I couldn't manually re-deploy because the latest revision was already in place in the old server.
I fixed it now with a dummy commit but force-releasing the last release (also if already released) would be a great thing :)
Michiel
I’m happy
-
Inappropriate?Hi Michael,
We are currently evaluating deploying specific revision as a possible feature. I am not sure when or if this will happen.
Another thing that comes to my mind is to invalidate the deployment history of a server, should the host be changed. This would solve cases like yours.
What do you think?
Thanks for your cooperation,
Petyo1 Comment
Add a comment
This answers the question
-
Thanks for the response. (Re)deploying a specific revision would be good. To rollback or to force-release something if a thing went wrong during uploading.
I think keeping a deployment server per host is important or if the host changes that the deployment history will be deleted and you can re-deploy every release.
For now for advanced deploying scenarious I would still use Capistrano but for simple uploading of html mockups for my other team members to review them the ftp deployment is my primary tool :)
Michiel
EMPLOYEE
