Build: #11 failed Changes by Spring Operator <[email protected]>

Build result summary


11 seconds
ddf8c8dd9137048be3cdc4c4a29c61f74562f748 ddf8c8dd9137048be3cdc4c4a29c61f74562f748
No failed test found. A possible compilation error occurred.


No one has taken responsibility for this failure

Code commits

Author Commit Message Commit date
Spring Operator <> Spring Operator <[email protected]> ddf8c8dd9137048be3cdc4c4a29c61f74562f748 ddf8c8dd9137048be3cdc4c4a29c61f74562f748 URL Cleanup
This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).

# Fixed URLs

## Fixed But Review Recommended
These URLs were fixed, but the https status was not OK. However, the https status was the same as the http request or http redirected to an https URL, so they were migrated. Your review is recommended.

* (404) migrated to: ([https]( result 404).

## Fixed Success
These URLs were fixed successfully.

* (301) migrated to: ([https]( result 200).
* migrated to: ([https]( result 200).
* migrated to: ([https]( result 302).
* migrated to: ([https]( result 302).

Jira issues

Unknown Issue TypeLICENSE-2Could not obtain issue details from Jira

Error summary for Default Job

The job generated some errors, drill down into the full build log for more details.

Could not find test result reports in the /opt/bamboo-home/xml-data/build-dir/INTEXT-SPLUNKSI4-JOB1 directory.

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'spring-integration-splunk'.
> Could not resolve all dependencies for configuration ':classpath'.
   > Could not resolve io.spring.gradle:docbook-reference-plugin:0.3.1.
     Required by:
      > Could not HEAD ''.
         > peer not authenticated
   > Could not resolve io.spring.gradle:spring-io-plugin:0.0.4.RELEASE.
     Required by:
      > Could not GET ''.
         > peer not authenticated

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.