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

(PA-139) unify pa acceptance workflows #4539

Conversation

er0ck
Copy link
Contributor

@er0ck er0ck commented Jan 1, 2016

(PA-139) acceptance: allow multiple options to beaker using OPTIONS

(PA-139) acceptance: move beaker host generation to own task

This change moves host file generation to its own task. This separates
its concerns from the testing tasks, and allows the testing tasks to be
dependent upon it.

(PA-139) add tmp hostgenerator dir to rake clean list

(PA-139) move common options out of Rakefile

Many people run with beaker standalone. Common and required options have
been moved to the options files to support this workflow in this change.
We also move common options to their own file and load them into the
other options files that are loaded by beaker.

(PA-139) acceptance: fix running against preserved_hosts

(PA-139) fix releasing of preserved hosts

Fix the releasing of hosts helper task by using the user's vmpooler
token from their .fog file. We also remove some lingering
preserved_config logic, which is no longer used due to improvements in
beaker.

(PA-139) fix listing of preserved hosts

This change fixes developer helper tasks made for managing acceptance
VMs easier. We also remove methods that are superseded by beaker
functionality.

(PA-139) acceptance: Rakefile: deprecate CONFIG in favor of HOSTS

(PA-139) acceptance: remove passenger and packages installs

[skip ci]

@er0ck er0ck changed the title DO NOT MERGE (maint) unify pa acceptance workflows (maint) unify pa acceptance workflows Jan 2, 2016
Eric Thompson added 6 commits January 2, 2016 11:04
This change fixes developer helper tasks made for managing acceptance
VMs easier. We also remove methods that are superseded by beaker
functionality.

[skip ci]
Fix the releasing of hosts helper task by using the user's vmpooler
token from their .fog file. We also remove some lingering
preserved_config logic, which is no longer used due to improvements in
beaker.

[skip ci]
Many people run with beaker standalone. Common and required options have
been moved to the options files to support this workflow in this change.
We also move common options to their own file and load them into the
other options files that are loaded by beaker.

[skip ci]
@er0ck er0ck force-pushed the acceptance/stable/maint-unify_PA_acceptance_workflows branch from bd7d385 to 452a304 Compare January 2, 2016 19:06
@er0ck er0ck changed the title (maint) unify pa acceptance workflows (PA-139) unify pa acceptance workflows Jan 2, 2016
@er0ck er0ck changed the title (PA-139) unify pa acceptance workflows DO NOT MERGE(PA-139) unify pa acceptance workflows Jan 4, 2016
Eric Thompson added 3 commits January 4, 2016 11:32
This change moves host file generation to its own task. This separates
its concerns from the testing tasks, and allows the testing tasks to be
dependent upon it.

[skip ci]
@er0ck er0ck changed the title DO NOT MERGE(PA-139) unify pa acceptance workflows (PA-139) unify pa acceptance workflows Jan 4, 2016
@er0ck
Copy link
Contributor Author

er0ck commented Jan 9, 2016

i only tested the test_against_preserved_hosts task with an empty simple test. further testing reveals that beaker wipes out the HOSTS hash when using any options file that points at a preserved_hosts file. i believe a work around is available that i'm working out for deployer. digging into the morass of coupling that is the beaker options parser is probably not the best route for now...

@johnduarte
Copy link
Contributor

suggestion to use BEAKER_HOSTCONFIG rather than HOSTS thoughts?

@er0ck
Copy link
Contributor Author

er0ck commented Jan 11, 2016

yeah, i'm sold on BEAKER_HOSTCONFIG use. i have a couple other updates for this PR. but maybe we should just get those minimal changes in, similar to your hiera PR and then i'll rebase this one as it has extensive unrelated changes.

@johnduarte
Copy link
Contributor

floating an update to hiera component to use BEAKER_HOSTCONFIG. This can be propagated to other puppet-agent components when approved.
puppetlabs/hiera#338

:preserve_hosts => 'onfail',
:forge_host => 'forge-aio01-petest.puppetlabs.com',
:'master-start-curl-retries' => 30
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

review note: moved most of these to the config files so one can run more easily from beaker standalone without repeated code.

@MikaelSmith
Copy link
Contributor

Is this starting from a baseline that's compatible with the changes in FACT-1281?

@er0ck
Copy link
Contributor Author

er0ck commented Jan 13, 2016

@MikaelSmith not yet. but it can be. we should probably wait until after the release for stuff like this PR

@er0ck er0ck closed this Jan 13, 2016
@er0ck
Copy link
Contributor Author

er0ck commented Jan 13, 2016

wrong branch name. re-opening

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

3 participants