you could use this plugin: https://wiki.jenkins-ci.org/display/JENKINS/Tool+Environment+Plugin to reuse the JDK definitions (JAVA_HOME) for your scripts - this way you at least don't have to hard code JAVA_HOME… /imod
On 27.03.2012, at 16:25, Andreas wrote: > Hi, > > my current favorite solution is to define a special ant and maven version as > Jenkins tools. Lets say ant-sonar and maven-sonar. Once installed I add to > the ant / mvn script of these tool installations: > > ## Special code to get a fix 1.6 jdk to run sonar 2.14 > JAVA_HOME=/usr/share/jdk1.6.0_20 > export JAVA_HOME > echo \*\*\* Using hardcoded JAVA_HOME in \"`basename $0`\" pointing to > \"$JAVA_HOME\". >&2 > > It is still kind of a hack but it limits the effort that has to go in the > reconfiguration of each job. > > > Kind Regards, Andreas. > > Am Montag, 26. März 2012 11:54:15 UTC+2 schrieb Andreas: > Hi, > > > I face the issue that I have to use different JDKs for different build steps. > Namely I need to invoke the compile step in ant with a 1.5 JDK and run the > sonar ant target with a 1.6 JDK. There is no easy way to split this job, so a > multi job setup is no solution here. Also I do not want to fork into a > different JDK in ant manually - actually only Jenkins knows where the JDK is > installed on the build node. > > I face a similar requirement for maven goals. > > I'm thinking about extending the ANT plugin to allow JDK selection in the > advanced options and the set JAVA_HOME accordingly. > > Is there an easy, already existing solution? Any ideas are welcome. > > > Kind Regards, Andreas. > > Am Montag, 26. März 2012 11:54:15 UTC+2 schrieb Andreas: > Hi, > > > I face the issue that I have to use different JDKs for different build steps. > Namely I need to invoke the compile step in ant with a 1.5 JDK and run the > sonar ant target with a 1.6 JDK. There is no easy way to split this job, so a > multi job setup is no solution here. Also I do not want to fork into a > different JDK in ant manually - actually only Jenkins knows where the JDK is > installed on the build node. > > I face a similar requirement for maven goals. > > I'm thinking about extending the ANT plugin to allow JDK selection in the > advanced options and the set JAVA_HOME accordingly. > > Is there an easy, already existing solution? Any ideas are welcome. > > > Kind Regards, Andreas. > > Am Montag, 26. März 2012 11:54:15 UTC+2 schrieb Andreas: > Hi, > > > I face the issue that I have to use different JDKs for different build steps. > Namely I need to invoke the compile step in ant with a 1.5 JDK and run the > sonar ant target with a 1.6 JDK. There is no easy way to split this job, so a > multi job setup is no solution here. Also I do not want to fork into a > different JDK in ant manually - actually only Jenkins knows where the JDK is > installed on the build node. > > I face a similar requirement for maven goals. > > I'm thinking about extending the ANT plugin to allow JDK selection in the > advanced options and the set JAVA_HOME accordingly. > > Is there an easy, already existing solution? Any ideas are welcome. > > > Kind Regards, Andreas. > > Am Montag, 26. März 2012 11:54:15 UTC+2 schrieb Andreas: > Hi, > > > I face the issue that I have to use different JDKs for different build steps. > Namely I need to invoke the compile step in ant with a 1.5 JDK and run the > sonar ant target with a 1.6 JDK. There is no easy way to split this job, so a > multi job setup is no solution here. Also I do not want to fork into a > different JDK in ant manually - actually only Jenkins knows where the JDK is > installed on the build node. > > I face a similar requirement for maven goals. > > I'm thinking about extending the ANT plugin to allow JDK selection in the > advanced options and the set JAVA_HOME accordingly. > > Is there an easy, already existing solution? Any ideas are welcome. > > > Kind Regards, Andreas. > > Am Montag, 26. März 2012 11:54:15 UTC+2 schrieb Andreas: > Hi, > > > I face the issue that I have to use different JDKs for different build steps. > Namely I need to invoke the compile step in ant with a 1.5 JDK and run the > sonar ant target with a 1.6 JDK. There is no easy way to split this job, so a > multi job setup is no solution here. Also I do not want to fork into a > different JDK in ant manually - actually only Jenkins knows where the JDK is > installed on the build node. > > I face a similar requirement for maven goals. > > I'm thinking about extending the ANT plugin to allow JDK selection in the > advanced options and the set JAVA_HOME accordingly. > > Is there an easy, already existing solution? Any ideas are welcome. > > > Kind Regards, Andreas.
