Docs CI Upload Versioned Artifacts

.github/workflows/docs-ci.yml

@@ -43,14 +43,18 @@ jobs:
  uses: burrunan/gradle-cache-action@v1
  with:
  job-id: allJavadoc
- arguments: --scan combined-javadoc:allJavadoc
+ arguments: --scan outputVersion combined-javadoc:allJavadoc
  gradle-version: wrapper
+
+ - name: Get Deephaven Version
+ id: dhc-version
+ run: echo "version=$(cat build/version)" >> $GITHUB_OUTPUT
 
  - name: Upload Javadocs
  if: ${{ github.ref == 'refs/heads/main' }}
  uses: actions/upload-artifact@v3
  with:
- name: javadocs
+ name: javadocs-${{ steps.dhc-version.outputs.version }}
  path: 'combined-javadoc/build/docs/javadoc/'
 
  - name: Deploy Javadoc
@@ -101,8 +105,26 @@ jobs:
  uses: burrunan/gradle-cache-action@v1
  with:
  job-id: pythonDocs
- arguments: --scan sphinx:pythonDocs sphinx:pydeephavenDocs
+ arguments: --scan outputVersion sphinx:pythonDocs sphinx:pydeephavenDocs
  gradle-version: wrapper
+
+ - name: Get Deephaven Version
+ id: dhc-version
+ run: echo "version=$(cat build/version)" >> $GITHUB_OUTPUT
+
+ - name: Upload Python Server Docs
+ if: ${{ github.ref == 'refs/heads/main' }}
+ uses: actions/upload-artifact@v3
+ with:
+ name: pyserver-docs-${{ steps.dhc-version.outputs.version }}
+ path: 'sphinx/build/docs/'
+
+ - name: Upload Python Client Docs
+ if: ${{ github.ref == 'refs/heads/main' }}
+ uses: actions/upload-artifact@v3
+ with:
+ name: pyclient-docs-${{ steps.dhc-version.outputs.version }}
+ path: 'sphinx/build/pyclient-docs/'
 
  - name: Deploy Python Docs
  if: ${{ github.ref == 'refs/heads/main' }}
@@ -165,8 +187,26 @@ jobs:
  uses: burrunan/gradle-cache-action@v1
  with:
  job-id: cppDocs
- arguments: --scan sphinx:cppClientDocs sphinx:cppExamplesDocs
+ arguments: --scan outputVersion sphinx:cppClientDocs sphinx:cppExamplesDocs
  gradle-version: wrapper
+
+ - name: Get Deephaven Version
+ id: dhc-version
+ run: echo "version=$(cat build/version)" >> $GITHUB_OUTPUT
+
+ - name: Upload Client C++ Docs
+ if: ${{ github.ref == 'refs/heads/main' }}
+ uses: actions/upload-artifact@v3
+ with:
+ name: cppclient-docs-${{ steps.dhc-version.outputs.version }}
+ path: 'sphinx/build/cppClientDocs/'
+
+ - name: Upload Client C++ Example Docs
+ if: ${{ github.ref == 'refs/heads/main' }}
+ uses: actions/upload-artifact@v3
+ with:
+ name: cppclient-examples-${{ steps.dhc-version.outputs.version }}
+ path: 'sphinx/build/cppExamplesDocs/'
 
  - name: Deploy Client C++ Docs
  if: ${{ github.ref == 'refs/heads/main' }}
@@ -191,3 +231,4 @@ jobs:
  remote_port: ${{ secrets.DOCS_PORT }}
  remote_user: ${{ secrets.DOCS_USER }}
  remote_key: ${{ secrets.DEEPHAVEN_CORE_SSH_KEY }}
+

RELEASE.md

@@ -54,6 +54,16 @@ The Deephaven python client is released as the `pydeephaven` wheel at [PyPi](htt
 ### Deephaven go client
 The Deephaven go client is released as a [Go package](https://pkg.go.dev/github.com/deephaven/deephaven-core/go).
 
+### Deephaven API docs
+API documentation is generated for Java, Python and C++ implemetations for Deephaven integration.
+The artifacts are released to [GitHub releases](https://github.com/deephaven/deephaven-core/releases)
+and are published as the following:
+* [Java Client/Server API](https://deephaven.io/core/javadoc/)
+* [Python Integration API](https://deephaven.io/core/pydoc/)
+* [Python Client API](https://deephaven.io/core/client-api/python/)
+* [C++ Client API](https://deephaven.io/core/client-api/cpp/)
+* [C++ Examples](https://deephaven.io/core/client-api/cpp-examples/)
+
 ## Release process
 
 The majority of the release procedure is controlled through the [publish-ci.yml workflow](./.github/workflows/publish-ci.yml).
@@ -150,7 +160,8 @@ Once the workflow job is done, ensure all publication sources have the new artif
 ### 5. Download artifacts
 
 Once the full publish-ci.yml worflow is done, the release artifacts can be downloaded from the GitHub Artifacts (located in the "Summary" tab of the action).
-These are currently manual steps taken from the browser.
+Similarly, release artifacts can be downloaded from the docs-ci.yml workflow.
+These are currently manual steps taken from the browser. (The artifacts will be uploaded in Step #9)
 
 There is potential in the future for QA-ing these artifacts above and beyond the integration testing that CI provides, as the release is not set in stone yet.
 
@@ -208,7 +219,8 @@ Create a new [GitHub release](https://github.com/deephaven/deephaven-core/releas
 
 The convention is to have the Release title of the form `vX.Y.Z` and to autogenerate the release notes in comparison to the previous release tag. Question: should we always generate release notes based off of the previous minor release, instead of patch? Our git release workflow suggests we may want to do it always minor to minor.
 
-Upload the Deephaven server application, deephaven-core wheel, pydeephaven wheel, and SBOM artifacts.
+Upload the Deephaven server application, deephaven-core wheel, pydeephaven wheel, and SBOM artifacts. Also, upload the C++, Java, and Python docs artifacts. 
+(These are the artifacts downloaded in Step #5)
 
 Hit the GitHub "Publish release" button.