Don't know how to build task 'testing'

[okram]

Is this is a limitation in capistrano that, i cannot seem to be able to create a Stage call, test or testing?.. I am trying to create 4 stages: dev, test, staging & production.. The last 2 were auto created by the command, "bundle exec cap install" itself. 

[root@localhost testapp1]# bundle exec cap install STAGES=dev, testing

mkdir -p config/deploy

[skip] config/deploy.rb already exists

create config/deploy/dev.rb

mkdir -p lib/capistrano/tasks

[skip] Capfile already exists

Capified

(Backtrace restricted to imported tasks)

cap aborted!

Don't know how to build task 'testing'

(See full trace by running task with --trace)

[root@localhost testapp1]# bundle exec cap install STAGES=dev, test

mkdir -p config/deploy

[skip] config/deploy.rb already exists

[skip] config/deploy/dev.rb already exists

mkdir -p lib/capistrano/tasks

[skip] Capfile already exists

Capified

(Backtrace restricted to imported tasks)

cap aborted!

Don't know how to build task 'test'

(See full trace by running task with --trace)

Versions:

• Ruby 2.1.1
• Capistrano   3.4.0 (Rake Version: 10.4.2)
• 
  

Platform:

• Working on.... CentOS

[Lee Hambley]

You can just copy the staging/production files and rename them... It might be a limitation we inherited from Rake or something, honestly I never tried to name an environment "test..."

--
You received this message because you are subscribed to the Google Groups "Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/56fc1523-c571-42ca-8510-c24a513c9511%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Lee Hambley]

The problem might also be the comma space separating dev,

On 17 Apr 2015 8:10 am, "okram" <nirish...@gmail.com> wrote:

[Hassan Schroeder]

On Thu, Apr 16, 2015 at 10:57 PM, okram <nirish...@gmail.com> wrote:
> Is this is a limitation in capistrano that, i cannot seem to be able to
> create a Stage call, test or testing?.. I am trying to create 4 stages: dev,
> test, staging & production.. The last 2 were auto created by the command,
> "bundle exec cap install" itself.

Mac OS (10.9.5)
Ruby 2.2.2
Capistrano Version: 3.4.0 (Rake Version: 10.4.2)

06:04 ~/testcases/rails-4-2/defaults (master)$ cap install STAGES=test,testing

mkdir -p config/deploy
[skip] config/deploy.rb already exists

create config/deploy/test.rb
create config/deploy/testing.rb

mkdir -p lib/capistrano/tasks
[skip] Capfile already exists
Capified

06:14 ~/testcases/rails-4-2/defaults (master)$ cap install STAGES=foo, bar

mkdir -p config/deploy
[skip] config/deploy.rb already exists

create config/deploy/foo.rb

mkdir -p lib/capistrano/tasks
[skip] Capfile already exists
Capified
(Backtrace restricted to imported tasks)
cap aborted!

Don't know how to build task 'bar'

(See full trace by running task with --trace)

It looks like Lee's right about the comma+space being the problem :-)

HTH,
--
Hassan Schroeder ------------------------ hassan.s...@gmail.com
http://about.me/hassanschroeder
twitter: @hassan
Consulting Availability : Silicon Valley or remote

[okram]

Thanks guys!!! yes the 'space' is the culprit... 

[root@localhost testapp1]# bundle exec cap install STAGES=dev,test

mkdir -p config/deploy

[skip] config/deploy.rb already exists

[skip] config/deploy/dev.rb already exists

create config/deploy/test.rb

mkdir -p lib/capistrano/tasks

[skip] Capfile already exists

Capified