kotovalexarian-likes-github/capistrano
1
0
Fork 0
mirror of https://github.com/capistrano/capistrano synced 2023-03-27 23:21:18 -04:00
Code Releases Activity
capistrano/features/configuration.feature

29 lines
1 KiB
Gherkin
Raw Normal View History

Allow configuration location to be configurable This change allows both the `deploy_config_path` and `stage_config_path` to be moved from the default locations of `config/deploy.rb` and `config/deploy` respectively. These values __must__ be set in the `Capfile` prior to `capistrano/setup` being called, for example: set :deploy_config_path, 'app/config/deploy.rb' set :stage_config_path, 'app/config/deploy' # Load DSL and Setup Up Stages require 'capistrano/setup' Fixes #610
2013-10-11 12:24:37 -04:00
Feature: The path to the configuration can be changed, removing the need to
follow Ruby/Rails conventions
Background:
Given a test app with the default configuration
And servers with the roles app and web
Scenario: Deploying with configuration in default location
When I run "cap test"
Then the task is successful
Scenario: Deploying with configuration in a custom location
But the configuration is in a custom location
When I run "cap test"
Then the task is successful
:panda_face: Updated the loading default config tasks and stages config tasks. To show all tasks decalred in default config and stages files was missed from the tasks list. Added default value for :stage and load all default configs. Also added cucumber tests.
2014-01-18 16:18:55 -05:00
Scenario: Show install task with configuration in default location
When I run "cap -T"
Then the task is successful
And contains "install" in the output
Scenario: Show install task with configuration in a custom location
And config stage file has line "desc 'Special Task'"
And config stage file has line "task :special_stage_task"
But the configuration is in a custom location
When I run "cap -T"
Then the task is successful
And contains "special_stage_task" in the output
Copy permalink