Publish CI builds to GitHub Releases, publish on ReadTheDocs #17
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
Left over from port from SimpleITK.
Since the tarball already has "html", this results in html/html.
From development fork.
|
Thank you @thewtex 🚀 ❤️ !! |
|
Thank you! |
|
Will all these releases be available on the main docs site, as is e.g. v5.3? |
|
@dzenanz all the release documentation are published here: https://docs.itk.org/projects/doxygen
And tarballs are in the ITKDoxygen repository GitHub Releases. |
|
https://github.com/InsightSoftwareConsortium/ITKDoxygen/tags: Were the double vv's |
|
@jhlegarreta Yes, 👍 those were unintentional -- removed 🔢 |
|
💯 Thanks Matt. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Publish the CI builds to the
latestGitHub Release. The artifacts are formatted to follow other ITK release doxygen artifacts.Also publish to ReadTheDocs. This provides:
There will be a lag of 1 build between publishing to GitHub Releases and publishing to RTD, i.e. RTD will be updated the next day.
I went through all the old releases and curated them (consistent organization, naming, reduced PNG sizes so they would fit in the releases, removed the old footers) and published them to RTD. There is a
WIP: RTD stubcommit that I would normally rebase/squash, but it should be retained so the subsequent commits can be kept for RTD versions.Supercedes #2
Closes #9 #4