Docs CI Upload Versioned Artifacts

.github/workflows/docs-ci.yml

@@ -38,6 +38,13 @@ jobs:
         run: |
           .github/scripts/gradle-properties.sh >> gradle.properties
           cat gradle.properties
+
+      - name: Set DHC Version
+        id: dhc-version
+        run: |
+          ./gradlew printVersion -q 
+          ./gradlew printVersion -q > dhc_version.txt
+          echo "version="`cat dhc_version.txt` >> "$GITHUB_OUTPUT"
 
       - name: All Javadoc
         uses: burrunan/gradle-cache-action@v1
@@ -50,7 +57,7 @@ jobs:
         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
@@ -96,13 +103,34 @@ jobs:
         run: |
           .github/scripts/gradle-properties.sh >> gradle.properties
           cat gradle.properties
+
+      - name: Set DHC Version
+        id: dhc-version
+        run: |
+          ./gradlew printVersion -q 
+          ./gradlew printVersion -q > dhc_version.txt
+          echo "version="`cat dhc_version.txt` >> "$GITHUB_OUTPUT"
 
       - name: Generate Python Docs
         uses: burrunan/gradle-cache-action@v1
         with:
           job-id: pythonDocs
           arguments: --scan sphinx:pythonDocs sphinx:pydeephavenDocs
           gradle-version: wrapper
+
+      - 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' }}
@@ -160,13 +188,34 @@ jobs:
         run: |
           .github/scripts/gradle-properties.sh >> gradle.properties
           cat gradle.properties
+
+      - name: Set DHC Version
+        id: dhc-version
+        run: |
+          ./gradlew printVersion -q 
+          ./gradlew printVersion -q > dhc_version.txt
+          echo "version="`cat dhc_version.txt` >> "$GITHUB_OUTPUT"
 
       - name: Generate C++ Docs
         uses: burrunan/gradle-cache-action@v1
         with:
           job-id: cppDocs
           arguments: --scan sphinx:cppClientDocs sphinx:cppExamplesDocs
           gradle-version: wrapper
+
+      - 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 +240,4 @@ jobs:
           remote_port: ${{ secrets.DOCS_PORT }}
           remote_user: ${{ secrets.DOCS_USER }}
           remote_key: ${{ secrets.DEEPHAVEN_CORE_SSH_KEY }}
+

RELEASE.md

@@ -150,7 +150,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 +209,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.