Hello,
At present, when we triggered the Jenkins template task in XL-Release, if the task is success or failed, in XL-Release window we have to click on the "console output" button and then it will navigate to the Jenkins to see the error logs, so error message is not displaying in the XL-Release output window if the task is failed.
So now our requirement is that:
Whenever you executed a Jenkins template task from XL-Release, if the task failed, we want to see the error in XL-Release itself only, which helps us to automate an email with accurate error details and then we no need to navigate to the Jenkins console output to see the error message.
kindly let me know if any further info required from my end.
Thanks
Raveendra
by: ALM t. | 9 months ago | Integrations
Comments
The Release product does not have such an built-in functionality for this purpose. We recommend incorporating a custom task that, in the event of failure, scans the Jenkins log output to extract the precise error, saving it exclusively to a new output property linked to a variable for subsequent use in a notification task. Storing entire Jenkins logs in our system isn’t viable due to database size limitations and the distinct lifecycle of releases compared to Jenkins builds.
Hello Team,
Thank you for the response, but
In the above comments said "in the event of failure, scans the Jenkins log output to extract the precise error" but as i checked, in the event of task failure also its just displaying the console output button, after clicking on the console output button then we can navigate to Jenkins to see the complete error, whatever the error is displaying in the XL-Release window is very minimal information and if we navigate to Jenkins then only we can come to the conclusion what is the exact issue if task failed. Actual error we can see in the jenkins only which not displaying in the release window. So as they said storing full log in XL-Release is not possible due to size limitations, so just want to understand whether its a possible scenario or not.
Thanks
Raveendra
Customers can either build this custom task via a plugin themselves or seek assistance from the Digital.ai Sales Engineering team to facilitate the extraction of Jenkins log output.