Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

jenkins::slave should not depend on jenkins #533

Closed
jhoblitt opened this issue Mar 11, 2016 · 5 comments
Closed

jenkins::slave should not depend on jenkins #533

jhoblitt opened this issue Mar 11, 2016 · 5 comments
Labels
bug Something isn't working

Comments

@jhoblitt
Copy link
Member

I accidentally introduced a dependency when converting to puppet/archive for all downloads.

Warning: Scope(Class[Jenkins::Slave]): Could not look up qualified variable '::jenkins::proxy_server'; class ::jenkins has not been evaluated
@jhoblitt jhoblitt added the bug Something isn't working label Mar 11, 2016
@jhoblitt jhoblitt added this to the 1.7.0 - Oddjob milestone Mar 11, 2016
@jhoblitt
Copy link
Member Author

jhoblitt commented Apr 3, 2016

Related to #248

@rtyler
Copy link

rtyler commented Apr 6, 2016

Heh, does this mean that every build node has a Jenkins master provisioned on it? 👅

@mprasil
Copy link

mprasil commented Apr 25, 2016

Seeing this won't be out until 1.7, is there some workaround to specify proxy for slave while avoiding duplicate declaration?

@jyaworski
Copy link
Member

This looks like it comes from here:

https://github.com/jenkinsci/puppet-jenkins/blob/master/manifests/slave.pp#L254

getvar could be used, but that's a hack. This would still fail strict_variables testing.

@jhoblitt
Copy link
Member Author

Resolved by #612

@smortex smortex changed the title ::jenkins::slave should not depend on ::jenkins jenkins::slave should not depend on jenkins Nov 24, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants