This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
Jamis Buck (author)
Thu Apr 24 21:37:02 -0700 2008
commit ec9a7fa52c9f417a9a01a7e764b520be1ec32c5c
tree 5d4923fd42a60cb46d398fc44384998628f6c562
parent d11006102c07c94e5d54dd0ee63dca825c93ed61
tree 5d4923fd42a60cb46d398fc44384998628f6c562
parent d11006102c07c94e5d54dd0ee63dca825c93ed61
... |
... |
|
... |
... |
|
... |
... |
|












:)
This changeset appears introduced issues for me.
The argument ‘revision’ is being passed in with a value of “origin/switchboard_base” (the name of the branch I’m deploying), which results in the execution of the command:
git ls-remote git@market:/var/gitrepo/market origin/switchboard_base
This command returns absolutely nothing. If I change the command to:
git ls-remote git@market:/var/gitrepo/market switchboard_base
It does do something. Very likely an issue with this command, which used to work in 2.2.x:
set :branch, “origin/switchboard_base”So, based on this, I guess I should no longer be passing in remote branch names.
I’ll fork and add a change that will warn if the remote revision is unresolvable. Overall, this is an exciting change – We’ve had issues before with deploying without first fetching.
Thanks, Tim