Branch: refs/heads/production
Home: https://github.com/jenkins-infra/jenkins-infra
Commit: c15ed7dd934298ce98dbd0a98dd8eb789cb0d16e
https://github.com/jenkins-infra/jenkins-infra/commit/c15ed7dd934298ce98dbd0a98dd8eb789cb0d16e
Author: R. Tyler Croy <[email protected]>
Date: 2015-12-21 (Mon, 21 Dec 2015)
Changed paths:
M dist/profile/manifests/staticsite.pp
Log Message:
-----------
The only way to get the account{} resource to do what you want is to pour
over code
It turns out you can pass a string into the $gid parameter and even if you set
it, you still have to tell the module to not create a bloody group for you.
This should finally get the constant churn on the group membership cleaned up
Actually fixes INFRA-513
Commit: 074d126059e69d0915ddee5dc21c2fb3ca2a4ac7
https://github.com/jenkins-infra/jenkins-infra/commit/074d126059e69d0915ddee5dc21c2fb3ca2a4ac7
Author: R. Tyler Croy <[email protected]>
Date: 2015-12-21 (Mon, 21 Dec 2015)
Changed paths:
M dist/profile/manifests/staticsite.pp
Log Message:
-----------
Merge pull request #184 from jenkins-infra/staging
Force account{} to act like it should
Compare:
https://github.com/jenkins-infra/jenkins-infra/compare/2406efe3240c...074d126059e6
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
