Global Tool Configuration - scripted

[Liora Milbaum]

I frequently create Jenkins test environments. 

Can I script to process of updating Global Tool Configuration? If the answer is yes, how?

Thanks,

Liora

[Mark Waite]

Can you further describe what you mean by "updating Global Tool Configuration"?

For example, are you switching from one version of automatically installed Java to another version of automatically installed Java?

Are you switching from one automatically installed maven (or ant) to another?

Are you switched from one version of git (or other command line dependency) to another?

Mark Waite

--
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/2663ad04-50f8-4068-ab5e-0c5228e0e7fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Liora Milbaum]

I want my Jenkins test env created with tools configured by a script.

You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/Yvc1oxrrilM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHK0-6-J6u8TW9CfgdL1tzZwVTpcyXtwZgZSHxY1w77BA%40mail.gmail.com.

[Mark Waite]

Sorry for being so particular, but the phrases you're using could be addressed in many different ways.  I can point you to a way that I've found helpful to automatically configure tools for my Jenkins instances.  I'm not sure it is a preferred practice, or even a good practice, but it has worked quite well for me.  Maybe that is what you're wanting.

I have a Docker instance defined at https://github.com/MarkEWaite/docker/tree/lts-with-plugins/ref which includes automatically installed JDK 6, JDK 7, JDK 8, Maven, and Ant.  I have many Jenkins jobs defined in that same Docker instance.  Those jobs depend on the tools by symbolic name (JDK 6 == jdk6, JDK 7 == jdk7, JDK 8 == jdk8, Maven == mvn, Ant == ant-latest).  When those jobs run, if they need a tool that is not already installed on the agent, the tool will be automatically installed.  Thus far, the technique has worked quite well for my needs, with variations of that Docker instance being regularly used to check LTS release candidates, LTS releases, old releases, and new plugin release candidates.

Branches in that docker repository represent configurations that are interesting to me.  There is an "lts" branch, an "lts-with-plugins" branch, and an lts-oldest-with-plugins.  In a private repository I have "lts-with-plugins-add-credentials" and "lts-with-plugins-add-credentials-and-nodes" and others.  That collection of branches allow me to rapidly switch from exploring and testing one variant or another.

Thanks,

Mark Waite