Jira (PUP-7432) Improve Beaker Workflow

Rishi Javia (JIRA) Fri, 07 Jul 2017 15:47:30 -0700

Title: Message Title

Rishi Javia commented on

PUP-7432

my 2¢

For the first problem pointed out by Josh Cooper about all beaker exec calls attempting to run pre-suite:

If you specify pre-suite during beaker exec call and not with beaker init, beaker subcommands will not remember or execute pre-suite on the following beaker exec calls. For example:

# Initialize beaker config, make sure to remove pre_suite from options.rb

$ bx beaker init --hosts hosts.yaml --options-file config/aio/options.rb --helper lib/helper.rb --load-path lib --debug --type aio --keyfile ~/.ssh/jenkins

# Provision VMs

$ bx beaker provision

# Execute tests (including pre-suite), any pre-suite or options-file provided here are executed for this exec call only

$ bx env SERVER_VERSION=latest SHA=5.0.0 beaker exec --tests tests/puppet_apply_basics.rb --pre-suite path/to/my/presuite/tests

# Execute tests again, this will not run pre-suite!

$ bx beaker exec --tests tests/puppet_apply_basics.rb

# Destroy VMs

$ bx beaker destroy

I know right now the pre-suites are embedded in the options file like this, but I'm just making sure that you are aware of this feature that if an options/pre-suite is provided with exec, subcommands would not remember them for the following exec calls. Code for exec.

So if you separate your options file into two:

has beaker options specific for aio/git
has pre-suite specific for aio/git
You can provide the first file with beaker init and pre-suite options file with beaker exec.

Add Comment

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7432) Improve Beaker Workflow

Reply via email to