On Wed, Sep 27, 2017 at 8:31 PM, Mark Waite <[email protected]> wrote: > > > 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. > > 1. Create a reference installation which is configured to meet your > needs > 2. Copy the XML configuration files from the JENKINS_HOME directory > 3. Copy the plugins (hpi and/or jpi files) from the > JENKINS_HOME/plugins directory > 4. Place those copies into your docker image (or onto the file system > where you're testing your "fresh install" steps) > 5. Run that "fresh install", confirm that it preserved all the > settings you need > > I get that this would be one way. I just find it to be ... not elegant enough.
I really think that this part of Jenkins is something is somehow way to hard to get done. To get stuff done I'll definitely go down that route but to minimize maintenance efforts I'd rather have it in a Groovy script (that is despite not having done a whole lot of it; actually: 0). Using a scripting language and API just seems to be more "affordable" in the long run. /Martin -- http://www.xing.com/profile/Martin_Marcher http://www.linkedin.com/in/martinmarcher Mobil: +43 / 660 / 62 45 103 UID: ATU68801424 -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAK1mKETRqM1%3DkW3kyPQXpE6Lay9BBqLfn7Jk1XSWg0bf31%2B%3DEw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
