[ https://issues.jboss.org/browse/JBTM-1563?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1563: ------------------------------------- Sure, the way this situation has arisen is that a build fails on CI, rather than the assignee having to understand the cause of the failure we allow them to link to the log of a failed build and make an attempt at a subject and component and if possible assignee. The reporter also marks the build as "keep forever". It is then the assignees responsibility to review the log (while still marked as "keep forever") then to update the subject and description to describe the actual problem. The assignee then resolves the issue, and finally removes the old build from CI. What has happened here is the job was renamed, so the link didn't work. I have revised the link to point to the correct job name. I will revise the link, and then we have the failed build that Amos is assigned to look into (that has been marked as "keep forever") but he hasn't looked into the cause of it yet. -- 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