I would like to ask you if there is a documentation explaining how to configure through files, plugins, nodes, git repositories, etc ...so you do not have to use the graphics console every time
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/dfc5e3ea-5a33-445e-82d7-0d8c0c011fab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thx so muchis a starting point, even if it is a limit that there is no direct thing to automatically configure jenkins without too much trouble
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/44ca6b13-e27b-4642-9fa4-052bda87bd26%40googlegroups.com.
I would very much like to do the same.If it helps, I have pretty clear picture of what I'd like to achieve. At least in my mind :)* Run thru the setup steps that install the "default plugins", just like the ones when doing it manually* Either one of:** Make a setup so that Jenkins authenticates "everyone can do anything" to a given LDAP server.** No authentication so that when I go to the Jenkins URL I am an administrator and can start configuring.I'm having a hard time finding examples or docs, so if you have pointers maybe that would be enough. I just can't get a starting point. I'll try and take a look at the examples in https://wiki.jenkins.io/display/JENKINS/Jenkins+Script+Console now that I have a pointer to it...
Best,Martin
On Wednesday, September 20, 2017 at 11:23:14 PM UTC+2, Diego Lagos wrote:I would like to ask you if there is a documentation explaining how to configure through files, plugins, nodes, git repositories, etc ...so you do not have to use the graphics console every time
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f76822b7-3cea-4052-9b52-0216c06268ac%40googlegroups.com.
I think that the technique you're trying to apply can be done entirely without scripts. It is illustrated in the repository I shared earlier in this thread.
- Create a reference installation which is configured to meet your needs
- Copy the XML configuration files from the JENKINS_HOME directory
- Copy the plugins (hpi and/or jpi files) from the JENKINS_HOME/plugins directory
- Place those copies into your docker image (or onto the file system where you're testing your "fresh install" steps)
- Run that "fresh install", confirm that it preserved all the settings you need