Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(maint) Acceptance Rake - give CONFIG priority #1252

Merged
merged 1 commit into from
Jan 11, 2016

Conversation

johnduarte
Copy link

This commit changes the logic in the beaker_test rake task for
acceptance giving BEAKER_HOSTS priority over TEST_TARGET.
It also changes the name of the ENV variable from CONFIG to
BEAKER_HOSTS

In the case that a static beaker host config file is needed for
running acceptance testing, the file path to this config should
be assigned to the ENV variable BEAKER_HOSTS. This value
will take precedence over any value set for TEST_TARGET.

TEST_TARGET is still used to supply a string for dynamically
generating beaker host configs.

skip:ci

This commit changes the logic in the beaker_test rake task for
acceptance giving BEAKER_HOSTS priority over TEST_TARGET.
It also changes the name of the ENV variable from CONFIG to
BEAKER_HOSTS

In the case that a static beaker host config file is needed for
running acceptance testing, the file path to this config should
be assigned to the ENV variable BEAKER_HOSTS. This value
will take precedence over any value set for TEST_TARGET.

TEST_TARGET is still used to supply a string for dynamically
generating beaker host configs.

skip:ci
@joshcooper
Copy link
Contributor

👍

joshcooper added a commit that referenced this pull request Jan 11, 2016
(maint) Acceptance Rake - give CONFIG priority
@joshcooper joshcooper merged commit 6738577 into puppetlabs:stable Jan 11, 2016
@johnduarte johnduarte deleted the add-beaker-hosts branch December 12, 2016 23:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants