Release Automation

Expand all | Collapse all

Better reporting on Jenkins plugin

Jump to Best Answer
  • 1.  Better reporting on Jenkins plugin

    Posted 06-28-2018 11:07 AM

    Trying to accomplish better feedback loop between Jenkins and CA process. Deployment plan has a post deployment process which does few things. Now if i leave the pause on failure- flags on actions, i get a proper error message to Jenkins jobs console output

    Status of deployment [testapp 3.8.62] on environment [int] : Active. Stage Status: Current Stage: Post-Deployment, Current stage Status: Running-With-Errors, Description: 58% Running Post-Deployment (With errors).
    Stage Error Details: ["Update CDD tokens has a process error - Server xxxx has failed step Regex - trim release id."] You can resolve the error then resume the execution from RA.

    But thats not the way want it to be. in most of the cases we have, there's no use leaving the process in paused state because the remedy is most often in developers hands, fixing the jenkins jobs. So, to get that working, added ROC fail deployment step and failure link to it from the failing action.   That then leads to following message

    Status of deployment [testapp 3.8.64] on environment [int] : Failed. Stage Status: Current Stage: Post-Deployment, Current stage Status: Failed, Description: 100% Failed Build step 'Run RA Deployment' marked build as failure Finished: FAILURE

    .. and lost error details, which means somebody needs to look from RA what was the issue.  And while the process details are no more visible, its difficult to see what really was the problem. 


    Is there some way of getting the details of the error back to Jenkins? Or maybe ROC fail deployment action could have a field for message ..

  • 2.  Re: Better reporting on Jenkins plugin
    Best Answer

    Posted 07-03-2018 10:27 AM

    Hi Jan,

     To my understanding the as per my understanding the status we get from Jenkins is the last/latest error message. So in above case if the process is failed in paused-failed stage it returns failed pause message. Now when you are marking release as failed it is that message you get on console which you get via release-status API.


    As I can see in above use case we are interested in process failure status which is been overwritten by release-status the latest which can only be possible to get via report but nothing on Jenkins as you mentioned.


    The use case you mentioned is valid but as I validate it is not possible to capture the same, I would request you to raise an idea and the best possible way I want to achieve this is that there should be an output field on the action ROC - Fail step capturing the error message from last run action before this action.


    May I request if you can submit this on idea as currently I am unable to find a legitimate way of achieving same and the use case looks like a valid one.




  • 3.  Re: Better reporting on Jenkins plugin

    Posted 07-04-2018 03:14 AM

    Hi Saurabh, how do i submit this as idea?


    Br Jan

  • 4.  Re: Better reporting on Jenkins plugin

    Posted 07-04-2018 03:58 AM

    Hi Jan,

     On CA Release Automation communities you can navigate to Idea section and post it there. The details around how to are presented in document Ideas 




  • 5.  Re: Better reporting on Jenkins plugin

    Posted 07-05-2018 08:49 AM

    Ok, thanks, i will do that.


    Br Jan

  • 6.  Re: Better reporting on Jenkins plugin

    Posted 07-04-2018 04:03 AM

    This is very feasible and great feature request. Requested Jan to post this request on idea section of Release Automation as "Feature request" in product.




  • 7.  Re: Better reporting on Jenkins plugin