Skip to content

Maint/master/acceptance harness releases pooled hosts#2339

Merged
jpartlow merged 3 commits intopuppetlabs:masterfrom
jpartlow:maint/master/acceptance-harness-releases-pooled-hosts
Mar 6, 2014
Merged

Maint/master/acceptance harness releases pooled hosts#2339
jpartlow merged 3 commits intopuppetlabs:masterfrom
jpartlow:maint/master/acceptance-harness-releases-pooled-hosts

Conversation

@jpartlow
Copy link
Contributor

@jpartlow jpartlow commented Feb 7, 2014

Updates to Beaker 1.6.2, which allows us to preserve hosts on fail. This is now the default. Also updates the cleanup code to check preserved hosts back into the pooling api, and clears out unused rsync code for preserved hosts.

@puppetcla
Copy link

CLA signed by all contributors.

@jpartlow
Copy link
Contributor Author

Fixed! Thanks for catching that @kylog

@kylog
Copy link

kylog commented Feb 19, 2014

Actually @jpartlow after I commented here, I realized that the missing rakes weren't new to this pull so I pushed that change to master. However, since this pull, Andy rearranged docs, so this needs to be rebased against master.

I should have mentioned this when I found it but it slipped my mind. Other than that I'm (thumbsup) on this change.

@jpartlow
Copy link
Contributor Author

Ah, right; I will rebase.

@jpartlow
Copy link
Contributor Author

I'll hold off on merging until after we get acceptance sorted out for the ruby-shadow issue.

jpartlow added 3 commits March 5, 2014 16:10
Our configurations now uses Scott's vcloud pooling api, so rather than
attempt to destroy them directly through vsphere (the code for which was
no longer working with current rbvmomi anyway) we are submitting them to
the pooling api for deletion.
Package re-installation and rsyncing of local code changes while
re-running acceptance tests on preserved vms is something we aren't
doing. A better solution for the cycle of acceptance testing against
local changes is to use a git install against a local git daemon (see
the docs/acceptance_tests.md) to test against changes you have checked
in locally.
Beaker can now be set to preserve hosts if the acceptance run fails.  We
are now defaulting to that for ci and manual testing, and pinning to
Beaker ~>1.7.0, so any release on the 1.7 line.
jpartlow added a commit that referenced this pull request Mar 6, 2014
…s-releases-pooled-hosts

Maint/master/acceptance harness releases pooled hosts
@jpartlow jpartlow merged commit b9173a6 into puppetlabs:master Mar 6, 2014
@jpartlow jpartlow deleted the maint/master/acceptance-harness-releases-pooled-hosts branch March 6, 2014 00:34
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.

3 participants