Metadata Valid
No translation
It's required to support escaping spaces in JENKINSJAVACMD, JENKINSJAVAOPTIONS, JENKINSHOME and JENKINSWAR variables.
For example, it's impossible to set hudson.model.DirectoryBrowserSupport.CSP without this, since CSP policy has to contain spaces, and escaping spaces wasn't possible in JENKINS_JAVA_OPTS.
In an attempt to get #761 merged, I've rebased it and added support for a ssh pubkey configuration in the bootstrap user.
```
jenkins_exec{ 'job-dsl security':
script => @(END)
import jenkins.model.*
def j = Jenkins.getInstance()
def jobDsl = j.getDescriptor("javaposse.jobdsl.plugin.GlobalJobDslSecurityConfiguration")
jobDsl.setUseScriptSecurity(false)
END
}
```
see JENKINS-51430
Retries is only used by the CLI providers. Puppet itself also provides retry functionality. This avoids the need to ensure a gem is installed in the right environment, which may not even work if it's a disconnected environment.
This does ignore a parameter for the maximum time to sleep. I'm looking for feedback on how to best deal with this.
If the password has changed run the update/create credential command.
Adds custom config.xml template for managing authorizationStrategy, securityRealm and views among other things.
Solves #939
<!--
Thank you for contributing to this project!
-->
Allow Java System Properties that may contain spaces as options parameters, like -Dhudson.model.DirectoryBrowserSupport.CSP="sandbox allow-same-origin"
Fixes #927
I want to improve module and add support for FreeBSD platform. I plan to implement it in small commits
chunk/steps and this is the first of them. All changes are tested on FreeBSD 11/12 (aka HEAD)
modulesync 2.12.0
The start-slave script was not using the env vars properly
This generates the start up options from the env vars in jenkins-slave
Fixes #779
This change removes the start up script for macOS and moves the arguments to the plist template.
…t runs
<!--
Thank you for contributing to this project!
-->
Passes credentials to jenkins-cli as environement variables by default so passwords aren't visible in the output of ps during puppet agent runs.
Not sure if this has an associated issue
This is useful on production Jenkins masters where non-scheduled restarts are
dangerous. Unit file changes and user changes that happen before tha package is
installed are not affected.
As of Jenkins 2.176.2 detached plugins were taking precedence over specified plugins due to a fix that was introduced for docker: https://issues.jenkins-ci.org/browse/JENKINS-57528.
The fix in Jenkins ensured stricter processing of plugins. the module was installing plugins as .hpi files where Jenkins expects them to be .jpi files.
This problem was highlighted in https://github.com/voxpupuli/puppet-jenkins/issues/926.
<!--
Thank you for contributing to this project!
-->
<!--
Replace this comment with a description of your pull request.
-->
<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->
By setting the user_realm to ldap and passing in the necessary config fields in ldapconfig through hiera for example then puppet will manage the ldap config.
Parameters to be set in the $ldapconfig hash:
server => "",
rootDN => "",
userSearch => "",
managerDN => "",
managerPasswordSecret => "",
inhibitInferRootDN => "",
disableMailAddressResolver => "",
displayNameAttributeName => "",
mailAddressAttributeName => ""
These will be loaded into a json file and then used by the puppet_helper groovy script to pass these arguments to the LDAPSecurityRealm constructor function.