Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Maint/fix resource relationships #298

Closed

Conversation

jhoblitt
Copy link
Member

Resolves #294

Joshua Hoblitt added 3 commits May 11, 2015 12:29
Introduced by: voxpupuli@979cb01

Classes/defines which include the jenkins::cli class assume that they can use
the cli even if $::jenkins::cli == false.  This breaks the top level anchor
pattern.  The cli param should either be deprecated and essentially hardwired
to true or attempting to use cli functionality without this param set should
fail; either option is a backwards incompatible change.

As an attempt to preserve backwards compatibility, there are includes and
resource relationships being scattered throughout this module.
Note that idempotence is not checked for as this appears to be broken with at
least jenkins 1.613.
@jenkinsadmin
Copy link

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

@rtyler rtyler modified the milestone: 1.5.0 - Jennings May 18, 2015
@rtyler
Copy link

rtyler commented Aug 9, 2015

I manually resolved this conflict and merged it into master

@rtyler rtyler closed this Aug 9, 2015
@jhoblitt jhoblitt deleted the maint/fix-resource-relationships branch September 17, 2015 17:22
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.

Job update fails with error (Exec[reload-jenkins] not in catalog)
3 participants