Issue #15521 has been updated by Justin Stoller.
off the top of my head (and my head's a little groggy still) this could be a
'role' method in our helper dsl, something like this.
<pre>
def forge
forges = hosts.select {|h| h['roles'].include? 'forge' }
unless forges.empty?
return forges.first
else
return 'forge-acceptance'
end
end
</pre>
Individuals could override the default 'forge-acceptance' by specifying a host
with 'forge' in the roles array within the config file. Within the tests the
forge's shortname would always be returned by this `forge` method.
(I have not double checked this code for accuracy only offering it as a guide)
----------------------------------------
Refactor #15521: Move puppet module acceptance tests to the new
forge-acceptance host
https://projects.puppetlabs.com/issues/15521#change-67083
Author: Ken Barber
Status: Accepted
Priority: Normal
Assignee:
Category: module tool
Target version: 2.7.x
Affected Puppet version: 2.7.18
Keywords:
Branch:
We seem to have a real forge-acceptance host now, and it would be great if we
can start to point to it, so we can free up forge-dev for our own purposes.
Currently the forge acceptance tests require multiple points of change,
optimally if we can reduce this to 1 point of change that would be great -
ideally if we can make it configurable enough to point to our own host of
choice when required this would be even better.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
