Currently if the CI fails it will add a message in Gerrit containing only a link to the Jenkins job. However, the actual build is actually done in Travis, and the build logs are stored in transfer.sh, which are not very straight forward to find as shown on the following document: http://www.dogtagpki.org/wiki/Jenkins_CI#Troubleshooting
To simplify CI troubleshooting, Jenkins message should also include the link to the Travis job, and possibly the link to the build logs on transfer.sh as well.
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue priority set to: major - Issue set to the milestone: 1.0 TASKS
Metadata Update from @mharmsen: - Issue assigned to dmoluguw
Fixed in master:
Commits: https://github.com/dogtagpki/pki/commit/138543e3fbad76cd0fba0ebd71548e5d8033f498 https://github.com/dogtagpki/pki/commit/fbc04caed6cfe3e47e7db32e19fc0d4f1e4b82f1
Fixed in 10_5 Branch:
Commit: https://github.com/dogtagpki/pki/commit/910ee1d32c7859beb9d85f7bcbd322335a7563a6
Metadata Update from @dmoluguw: - Issue close_status updated to: fixed
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/3054
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.