Skip to content
Continuous Integration

Include failure message in Nexus exception #674

Sign in to view logs

Include failure message in Nexus exception

Include failure message in Nexus exception #674

Triggered via pull request October 2, 2024 23:06
@Quinn-With-Two-NsQuinn-With-Two-Ns
opened #2251
Quinn-With-Two-Ns:nexus-failure-message
Status Success
Total duration 12m 58s
Billable time 22m
Artifacts –

ci.yml

on: pull_request
Unit test with in-memory test service [Edge]
9m 4s
Unit test with in-memory test service [Edge]
Unit test with docker service [JDK8]
11m 38s
Unit test with docker service [JDK8]
Unit test with cloud
16s
Unit test with cloud
Copyright and code format
36s
Copyright and code format
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Unit test with cloud
❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run)
Unit test with in-memory test service [Edge]
❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run)
Unit test with docker service [JDK8]
❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run)
Unit test with cloud
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23
Unit test with in-memory test service [Edge]
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23
Unit test with docker service [JDK8]
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23