support for disabling plugins about puppet-jenkins HOT 6 CLOSED

@eops-wedgwood does #138 meet your needs?

from puppet-jenkins.

Sorry for the delay in response. I've noticed that some plugins use the hpi extension rather than jpi. I'm not sure if there are others. Looks like #138 only addresses the jpi extension. Sorry for missing that originally.

from puppet-jenkins.

According to "grund" on stackoverflow, plugins are shipped as .hpi when installing and downloading them directly from jenkins-ci.org*, and .jpi when installing them via the jenkins web interface:

http://stackoverflow.com/a/12925032

• However, when upgrading a core plugin (such as ldap or cvs) by downloading the new .hpi file from jenkins-ci.org, jenkins will convert the file from .hpi to .jpi next time it is restarted.

from puppet-jenkins.

#209 resolves this issue. It can be closed.

from puppet-jenkins.

@jhoblitt I'm sitting here researching the plugin behaviors and when i read #209 i got confused because I do not see how that credentials fix resolves this plugins issue? I didnt notice anything in that explaining it. Could you clarify?

from puppet-jenkins.

@gregswift My apologies, it was the PR merged after that, #212 That PR was released as part of v1.4.0. I'm going to close this issue but please feel free to reopen it if there is a bug with this functionality.

from puppet-jenkins.