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
8206311: Add docs-javase, docs-reference to CI build #99
Conversation
|
@erikj79 The following label will be automatically applied to this pull request: When this pull request is ready to be reviewed, an RFR email will be sent to the corresponding mailing list. If you would like to change these labels, use the |
Webrevs
|
@erikj79 This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, but I'd like som clarification about the docs jib target.
configure_args: [ | ||
"--enable-full-docs", | ||
"--with-build-jdk=" + input.get(buildJdkDep, "home_path") | ||
+ (input.build_os == "macosx" ? "/Contents/Home" : "") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not fully understanding the platform selection mechanism here. Previously, docs were only built on linux-x64. I can see no such filtering in the new code; and this piece here even indicates assumed support for macosx.
Question: Is docs still built only on one platform? How is this achieved then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to make the jib profile "docs" buildable on any platform (though I guess windows is likely not going to work well). This makes future development more flexible for local builds. The platform we choose to use for our official CI/tier configurations is controlled elsewhere and will continue to be linux-x64.
@erikj79 This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 8 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the
|
/integrate |
@erikj79 Since your change was applied there have been 8 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 9ade94b. |
Reposting this review as PR.
In order to regularly build the javase and reference docs images, I have made the following changes:
The new top level targets are:
docs-{jdk.javase,reference}-image:
Aliases for the existing docs-{jdk,javase,reference} added for consistency. The old docs-image is now an alias for docs-jdk-image.
all-docs-images:
Builds all 3 of the above docs images.
docs-{jdk,javase,reference}-bundles:
Builds the bundles for each kind of docs image. The existing docs-bundles is now an alias for docs-jdk-bundles.
all-docs-bundles:
Builds all the docs bundles.
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/99/head:pull/99
$ git checkout pull/99