Hello We have used Jenkins 1.x for a number of build jobs because of some old system requirements. Now that some of those systems were retired we could finally upgrade Jenkins to a 2.x version, including plugins of course. Most jobs look fine and seem to work like before. However we have one case that doesn't and I don't know how to fix it.
We have two jobs that are meant to run after another, combined in a job pipeline. The first job is parametrized, so the user first has to enter some information before the job is run. That part still works. If the first job is successful then the user can start the second job in the pipeline view if he wants to. The second job also uses these parametrized variables from the first job. That used to work fine with Jenkins 1.x but not with 2.x. The variables are not resolved and therefore the build fails, like checking out with svn: >Location 'https://.../tags/${FW_SVN_PATH}/${FW_VERSION}/bin' does not exist >Cleaning local Directory . >Checking out https://.../tags/$%7BFW_SVN_PATH%7D/$%7BFW_VERSION%7D/bin at >revision '2020-12-11T11:06:44.042 +0100' What do I need to do to resolve the parametrized variables in the second job with the values from the first job? Remember I'm not talking about the new pipeline scripts from 2.x, this is a job pipeline that already existed in 1.x, and I don't want to rewrite it. After all Jenkins 2.x is advertised as a drop-in replacement. Thanks bye Fabi -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20201211104337.06986437584E%40macserver.private.
