-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed build when offline #44
Comments
Does the build itself fail or is it just a log message? |
Build is stuck in a loop with the stack trace above. |
I'll have a look. |
I'm curious: Why are you building offline? |
I travel a lot with work and sometimes don't have connectivity on trains, planes, or other locations. We don't always have a network connection ;-) |
@mjpt777 Please try again with |
Seems to be working locally when I disable the network. Thanks. I'm travelling next week when I'll be able to try it properly. |
Now works offline. Thanks. |
I'm seeing this issue again in our Travis CI build. I'm also seeing issues with links not being created when a dependency is pushed to to Maven Central but has not yet shown up in javadoc.io. Can the plugin warn but continue as if successful when a dependency is not online? https://travis-ci.org/real-logic/agrona/jobs/562129281
|
Can you re-run the build with |
Not easy with a PR running in Travis. Sorry. |
Got the stacktrace.
|
Note this change might be happening. maxcellent/javadoc.io#22 |
This is currently happening on all repos I have building on Travis and using javadocs-links. |
maxcellent/javadoc.io#22 would cause a 403 (or 404) response on the HTTP layer, but the exception indicates a problem on the TCP/IP layer. Maybe cloudflare (which is used by javadoc.io) has blocked Travis' public IP addresses. All(!) travis builds share the same set of public IP adresses. |
Could the issue be http vs https? |
It seems like javadoc.io doesn't exist anymore 🤔 |
javadoc.io is available again 👍 |
Thanks for the quick fix. :-) |
I'm still getting issues with 3.3.1 javadoc-links when building offline. I'm now getting an exception trace looping as like below.
It does not mater if I try
gradlew -x javadoc
orgradlew --offline
, it still fails the same way.Is it possible to change the plugin to not take any action of
-x javadoc
is passed?It would be good if you tested offline and purged the DNS catch.
The text was updated successfully, but these errors were encountered: