View build logs
Integrated CI/CD
On this page
Related content
- Automation For Jira - Troubleshooting the most common errors reported in the rule audit logs
- Automation For Jira (A4J) Data Center - The ultimate troubleshooting guide
- Automation for Jira rule fails "java.lang.StringIndexOutOfBoundsException: begin 12, end 3, length 3" error
- The Jira application throws a 500 error in the UI when any Automation For Jira page is accessed
- Automation for Jira - Troubleshooting guide for situations where automation rules are not triggered
- "An unknown error occurred" when enabling or saving Jira Automation rules after upgrade
- Automation rule fails with the error "you do not have the permission to associate a worklog to this issue"
- Automation rule| Rule audit logs indicate an error upon execution even though the operation was performed successfully
- An automation rule shows the error "Could not find configured field '[object Object]'. It may have been deleted" in its configuration
- Automation for Jira cannot publish an Automation rule with an error: "additional fields contains invalid field(s) in ‘update’ or ‘fields’ section: <Field_Name>"
Integrated CI/CD enables Bitbucket Data Center and Server to display contextual information about a build, such as a link to the build’s logs on your CI server. You’ll see this link on the Builds page and the pull request builds tab, making it easy to investigate problems when you spot them.
To enable build log links, you need to Link your CI server.
Last modified on Feb 25, 2021
Related content
- Automation For Jira - Troubleshooting the most common errors reported in the rule audit logs
- Automation For Jira (A4J) Data Center - The ultimate troubleshooting guide
- Automation for Jira rule fails "java.lang.StringIndexOutOfBoundsException: begin 12, end 3, length 3" error
- The Jira application throws a 500 error in the UI when any Automation For Jira page is accessed
- Automation for Jira - Troubleshooting guide for situations where automation rules are not triggered
- "An unknown error occurred" when enabling or saving Jira Automation rules after upgrade
- Automation rule fails with the error "you do not have the permission to associate a worklog to this issue"
- Automation rule| Rule audit logs indicate an error upon execution even though the operation was performed successfully
- An automation rule shows the error "Could not find configured field '[object Object]'. It may have been deleted" in its configuration
- Automation for Jira cannot publish an Automation rule with an error: "additional fields contains invalid field(s) in ‘update’ or ‘fields’ section: <Field_Name>"
Powered by Confluence and Scroll Viewport.