|
||||||||
|
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.
Hello Thomas,
The description is not very clear, now that I read it again, sorry for that. But the issue should be easy to reproduce using the following steps:
1. Create a new folder.
2. Create a new project in the folder. In the next steps we will add a manual trigger that triggers this project.
3. Create a new Maven project in the folder.
4. In the Maven project created in step 3 add a 'Build other projects (manual step)' post-build action to trigger the project created in step 2. You should see that validation of the project name fails and it suggests that the project is in the parent folder.
It is essential that the project created in step 3 is a Maven project.
The versions I used are Jenkins 1.532.2 and build-pipeline-plugin 1.4.2.
Wilco