[BAP-125] Artifactory Maven 3 Task is not setting Bamboo job requirements correctly Created: 03/Jan/12  Updated: 04/Jan/12  Resolved: 04/Jan/12

Status: Resolved
Project: Bamboo Artifactory Plug-in
Component/s: None
Affects Version/s: 1.5.0
Fix Version/s: 1.5.1

Type: Bug Priority: Normal
Reporter: Stefan Bauer Assignee: Noam Y. Tenne (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

Bamboo 3.3.3



 Description   

Following behavior is causing problems in executing Artifactory Maven Task.
If you setup a new plan, add job and "Artifactory Maven 3 Task". The executable and JDK that will be choosed, is missed at Requirements tab.
It causes that build job will run at build agents, where is no "Artifactory Maven 3 Task" executable defined. In this sporadic cases the execution is failed with "Maven home is not defined!" error.

For built-in Maven Taks plugins it is working in the way, that all changes in tasks settings cause adjustments at job Requirements tab.
Artifactory Maven Task plugin missed it. Requirement items can be added manually to workaround the issue, but this is error prone for big environment and project landscapes.

Note: There might be an undiscovered relation to BAP-66 as well.



 Comments   
Comment by Noam Y. Tenne (Inactive) [ 04/Jan/12 ]

Thanks for reporting this; we'll take a look into it.

Comment by Stefan Bauer [ 04/Jan/12 ]

Woohoo, that's fast. Thank you!

Generated at Sat Aug 24 08:10:45 UTC 2019 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.