Continuous integration build for Spring Social Facebook module

Build result summary


18 seconds
d1234a7af223edd8dfa2574b393b2547cfba0cb8 d1234a7af223edd8dfa2574b393b2547cfba0cb8
Failing since
#327 (Changes by Spring Operator <>)
Fixed in
#329 (Changes by Craig Walls)
No failed tests found, a possible compilation error occurred.


This build has been failing since #327
No one has taken responsibility

Code commits

Author Commit Message Commit date
Spring Operator <> Spring Operator <> d1234a7af223edd8dfa2574b393b2547cfba0cb8 d1234a7af223edd8dfa2574b393b2547cfba0cb8 URL Cleanup
- Ensure Gradle Wrapper is downloaded via https
Spring Operator <> Spring Operator <> 2681ce1c3015ead5c45211cf94c630251085da3f 2681ce1c3015ead5c45211cf94c630251085da3f 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 Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

* [ ] with 2 occurrences migrated to: ([https]( result 200).
* [ ] with 255 occurrences migrated to: ([https]( result 200).

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.

Note: /opt/bamboo-home/xml-data/build-dir/SOCIAL-FACEBOOKDEF-JOB1/spring-social-facebook/src/main/java/org/springframework/social/facebook/api/impl/ uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

223 tests completed, 18 failed

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':spring-social-facebook:springReleaseTest'.
> There were failing tests. See the report at: file:///opt/bamboo-home/xml-data/build-dir/SOCIAL-FACEBOOKDEF-JOB1/spring-social-facebook/build/reports/spring-release-tests/index.html

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