-
Notifications
You must be signed in to change notification settings - Fork 37.8k
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
A clean build leads to "Failed to download playbook" #30481
Labels
Milestone
Comments
rstoyanchev
added a commit
that referenced
this issue
May 12, 2023
rstoyanchev
added a commit
that referenced
this issue
May 23, 2023
Instead of having antora run always, which happens regardless of whether anything has changed, we'll have it invoked as part of the CI build, and we'll have to run it locally ourselves when necessary. See gh-30481
We've decided to revert the change to download the playbook to the build directory, as well as to remove the task dependency from "check" to "antora", also because it runs every time (regardless of changes) and it is not very fast. Instead we'll have the "antora" task run as part of the CI build, or otherwise we'll run it manually locally. |
rstoyanchev
added a commit
that referenced
this issue
May 23, 2023
rstoyanchev
added
the
status: superseded
An issue that has been superseded by another
label
May 23, 2023
mdeinum
pushed a commit
to mdeinum/spring-framework
that referenced
this issue
Jun 29, 2023
mdeinum
pushed a commit
to mdeinum/spring-framework
that referenced
this issue
Jun 29, 2023
Instead of having antora run always, which happens regardless of whether anything has changed, we'll have it invoked as part of the CI build, and we'll have to run it locally ourselves when necessary. See spring-projectsgh-30481
mdeinum
pushed a commit
to mdeinum/spring-framework
that referenced
this issue
Jun 29, 2023
This reverts commit d8f6567. See spring-projectsgh-30481
mdeinum
pushed a commit
to mdeinum/spring-framework
that referenced
this issue
Jun 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
This looks related to the recent change #30465 to download to the build directory. The
antora
task seems to download the playbook quite early as part of registration. I can see in the logs the playbook is successfully retrieved, but the build directory probably doesn't exist yet.Removing the dependency on "check" it no longer fails. However, the task also no longer gets run as part of the build to flag potential documentation issues.
I'm not sure if there is room for improvement on the Antora side. I find that both the "check" to "antora" dependency as well as the choice to cache the playbook under the build directory are reasonable choices.
The text was updated successfully, but these errors were encountered: