Subversion check doesn't run chat script.
Reported by Neil Wilson | May 2nd, 2008 @ 08:19 AM
When using a svn+ssh repository URL with passwords, the 'handle data' chat script from the strategy doesn't handle the output.
The result is a lot of prompts from what looks like a local execution of the 'svn' command in the evaluation of 'real_revision'.
With the upgrades to Capistrano is there a way to get this version check to execute on just one of the remote machines. Remember that the management station may not even have the version control system installed.
Comments and changes to this ticket
-
Jamis Buck May 2nd, 2008 @ 11:37 AM
If by "management station" you mean "the server from which you are deploying", keep in mind that this is one of the core assumptions of cap's deployment recipes: the server you are deploying from DOES have access to your repository. If that assumption doesn't hold for you, you'll have to either adapt cap's recipes, or write your own. :( However, if someone were to submit a patch that provided a clean, portable means for bypassing that assumption, I'd certainly consider it.
Regarding the password prompt, yeah. The reason the output from local executions isn't filtered through the handle_data method is because of Windows. I don't know of a portable way to interact with external processes. Patches will certainly be appreciated.
-
Neil Wilson May 2nd, 2008 @ 10:55 PM
Currently the implicit assumption is that the server from which you
are deploying is the data acquisition station. Could we not make that
either an explicit role, or a flag (along the lines of 'role :db,
:primary => true' - another example of a requirement to execute on a
single server) so that the job can be farmed out to one of the client
stations?
What do you think?
-
Jamis Buck May 3rd, 2008 @ 09:26 PM
That sounds like a good compromise. Either way (an explicit role, or a new condition) would be fine with me, if you'd like to whip up a patch.
-
Jamis Buck August 17th, 2008 @ 07:16 PM
- → Tag changed from “” to “unfinished”
- → State changed from “new” to “closed”
In order to keep things tidy, I'm going to close this ticket. If anyone comes up with a patch for it, please feel free to repoen.
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 »
