#10 'none' SCM strategy - blows up deploy:check - Capistrano

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:id	tickets sorted by id (creation time)
Combine keywords for powerful searching.
Use advanced searching »

#10 √ resolved

'none' SCM strategy - blows up deploy:check

Reported by Neil Wilson | May 4th, 2008 @ 11:31 AM

Needs a default_command

How about

default_command ""

Neil Wilson May 5th, 2008 @ 09:47 PM
(from [0badc5bbb5e0a64e55a2e1aa4202532e72812daa]) Make sure deploy:check works with :none scm (which has no default command) [#10 tagged:committed state:resolved]
http://github.com/jamis/capistra...
Jamis Buck May 5th, 2008 @ 09:47 PM
- → State changed from “new” to “resolved”

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)

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »