Enabling javadoc production for template. #4963
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
I'd rather this be done in a separate profile if possible, so that our published JavaDocs don't include the template files in them. |
Contributor
Author
|
/azp run java - template |
|
Azure Pipelines successfully started running 1 pipeline(s). |
mitchdenny
force-pushed
the
add-javadoc-gen-to-template
branch
from
34bbf1b to
98d5734
Compare
mitchdenny
force-pushed
the
add-javadoc-gen-to-template
branch
from
07f3750 to
00ddf3b
Compare
Contributor
Author
Adjusted this its similar to what we had before, but its driven by a variable that I set on the |
pull bot
pushed a commit
to test-repo-billy/azure-sdk-for-java
that referenced
this pull request
Aug 15, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Working on getting the unified pipeline going for the template project so we can use it for validating the deployment pipeline end-to-end.