Maven Metadata Plugin MY_JAR_VERSION cannot be set from upstream project

[Torsten Reinhard]

Hi,

2 days ago I upgraded from Jenkins 1.609.3 to 1.651.3. , I´m using Maven Metadata Plugin 1.41

Now I have a problem with my parameterized job cascades:

Deploy-INT

       - deploy-backend-INT

       - deploy_frontend-INT

The downstream projects are triggered properly, but the versions arent reflected correctly:

The log from the upstream project says:

14:14:06 + echo 'deploying now Release 1.0.3.9:' (selected from Deploy-INT)
14:14:06 deploying now Release 1.0.3.9:
14:14:06 + echo 'Backend: 1.0.1-b841-r1991' (extracted from this release)
14:14:06 Backend: 1.0.1-b841-r1991
14:14:06 + echo 'Frontend: 1.0.1-b40-r1983'  (extracted from this release)
14:14:06 Frontend: 1.0.1-b40-r1983

But in the triggered (downstream Jobs) I see:

14:14:13 would have deployed frontend-1.1.0-b84-r2002-htdocs-min.tar.gz

=> This is the "latest" release in the dropdown - but not the version passed !

I´m passing the versions as "predefined parameters" with the Parameterized Build Plugin - named exactly like the parameters in the downstream project:

COMPONENT_VERSION=$frontend_version

It seems like some change made in Jenkins doesn´t allow anymore to pass parameters from one job to another when using Mavan Metadata plugin.

Any help appreciated, 

Torsten

[Daniel Beck]

> On 18.11.2016, at 15:37, Torsten Reinhard <em...@torstenreinhard.de> wrote:
>
> It seems like some change made in Jenkins doesn´t allow anymore to pass parameters from one job to another when using Mavan Metadata plugin.

First entry on https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 will explain why, and how to solve this.