[JIRA] [parameterized-trigger-plugin] (JENKINS-25936) Maven environment variables are not expanded when triggering another project.

Sat, 06 Dec 2014 20:04:29 -0800

ikedam commented on Bug JENKINS-25936

Could not reproduce: Tested with Jenkins 1.583, maven-plugin 2.5, parameterized-trigger-plugin 2.25 on Windows 8.1.

  1. Create a free style project "downstream"
    • Add a "Execute Windows batch command" (Of cource, "Execute shell" would be OK if you run Jenkins on Linux)
      • execute "echo %myparam%"
  2. Create a maven project "upstream"
    • Select "Git" for SCM.
    • Goals and options: package -DskipTests=true
    • Add "Trigger parameterized build on other projects" for Post-build Actions.
      • Projects to build: downstream
      • Add "Predefined parameters" and specify "myparam=${POM_ARTIFACTID}"
  3. Run a build for the upstream.

Result:

  • a downstream build outputs "parameterized-trigger".

Please report your versions of Jenkins and plugins, and exact steps to reproduce the problem.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to