0

We have a very old Jenkins version (1.577) on windows server that we upgrade to 2.516.3 version successfully more or less. The most problematic issue is related to a freestyle job: the job is a build for a java app that read a custom string variable (VERSION), make all the build, populate dimensionscm repository using its own proprietary plugin, and at the end of the build named it with APPNAME_VERSION-BUILDNO. Unfortunately the variable we assign a value at the beginning of the build won't be passed to the dimensionscm plugin that cannot valuate correctly the variable and let the app named APPNAME_VERSION-77 instead of APPNAME_1.41-77 (as a sample).

This make also the baseline job that is linked to the build job and invoked by it, failed each time because it point to a wrong name.

I try to use EnvInject but with no success. In the old infrastructure still in place the job is working as expected.

Does anyone knows how I could fix it? as we have more than 200 jobs that run in that way.

New contributor
DanieleF is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.