-
New Feature
-
Resolution: Unresolved
-
Major
Currently, the "Progress JIRA issues by workflow action" can only be added as a "build step". However, it should also be available as a "Post-build step" in-case this progress should NOT happen when build fails.
Our use-case: Workflow action "Submit to QA" should only happen if build was successful and all unit tests have passed successfully. We use the xUnit report publisher with specific thresholds as a Post-build action as well. We should be able to place "Progress JIRA issues by workflow action" after these xUnit publishers.
Here's an example how this doesn't work for us today,
As you can see, the workflow action happened before the xUnit changed build result to FAILURE.
10:36:16 [JIRA] Updating issues using workflow action Submit to QA. 10:36:16 [JIRA] JQL: project = ZZZ and fixVersion = "3.1.x" and status in (resolved) 10:36:18 [JIRA] Issue ZZZ-2761 transitioned to "In Review" due to action "Submit to QA". 10:36:19 [JIRA] Issue ZZZ-2749 transitioned to "In Review" due to action "Submit to QA". 10:36:20 [JIRA] Issue ZZZ-2742 transitioned to "In Review" due to action "Submit to QA". 10:36:20 [JIRA] Issue ZZZ-2741 transitioned to "In Review" due to action "Submit to QA". 10:36:21 [JIRA] Issue ZZZ-2733 transitioned to "In Review" due to action "Submit to QA". 10:36:35 [xUnit] [INFO] - Check 'Failed Tests' threshold. 10:36:35 [xUnit] [INFO] - The total number of tests for this category exceeds the specified 'failure' threshold value. 10:36:35 [xUnit] [INFO] - Setting the build status to FAILURE 10:36:35 [xUnit] [INFO] - Stopping recording. 10:36:35 Build step 'Publish xUnit test result report' changed build result to FAILURE 10:36:35 [JDepend] JDepend plugin is ready 10:36:35 [JDepend] Found 1328 classes in 181 packages 10:36:35 Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur.
