migration of build artifacts to internal services account

Author: brianwthomas

.github/workflows/main.yml

@@ -15,37 +15,37 @@ jobs:
       matrix:
         config:
           - {
-              name: 'Windows - MSVC',
-              artifact: 'windows-msvc.tar.xz',
+              name: "Windows - MSVC",
+              artifact: "windows-msvc.tar.xz",
               os: windows-latest-l,
-              cc: 'cl',
-              cxx: 'cl',
-              build-type: 'Release',
-              build-code: 'Windows',
-              generator: 'Ninja Multi-Config',
-              coverage: 'false',
+              cc: "cl",
+              cxx: "cl",
+              build-type: "Release",
+              build-code: "Windows",
+              generator: "Ninja Multi-Config",
+              coverage: "false",
             }
           - {
-              name: 'Ubuntu - GCC',
-              artifact: 'linux-gcc.tar.xz',
+              name: "Ubuntu - GCC",
+              artifact: "linux-gcc.tar.xz",
               os: ubuntu-latest-m,
-              cc: 'gcc-11',
-              cxx: 'g++-11',
-              build-type: 'Release',
-              build-code: 'Ubuntu',
-              generator: 'Unix Makefiles',
-              coverage: 'false',
+              cc: "gcc-11",
+              cxx: "g++-11",
+              build-type: "Release",
+              build-code: "Ubuntu",
+              generator: "Unix Makefiles",
+              coverage: "false",
             }
           - {
-              name: 'CentOS 7 - GCC',
-              artifact: 'linux-gcc.tar.xz',
+              name: "CentOS 7 - GCC",
+              artifact: "linux-gcc.tar.xz",
               os: ubuntu-latest-m,
-              cc: 'gcc-11',
-              cxx: 'g++-11',
-              build-type: 'Release',
-              build-code: 'CentOS7',
-              generator: 'Unix Makefiles',
-              coverage: 'false',
+              cc: "gcc-11",
+              cxx: "g++-11",
+              build-type: "Release",
+              build-code: "CentOS7",
+              generator: "Unix Makefiles",
+              coverage: "false",
             }
 
     steps:
@@ -204,4 +204,4 @@ jobs:
       - name: Upload to S3
         if: ${{ matrix.config.name == 'CentOS 7 - GCC' || runner.os == 'Windows' }}
         run: |
-          aws s3 cp build/${{ env.zip_name }} s3://cesium-travis-builds/cesium-omniverse/${{ env.branch }}/${{ env.us_date }}/${{ env.sha_short }}/${{ matrix.config.build-code }}/
+          aws s3 cp build/${{ env.zip_name }} s3://cesium-builds/cesium-omniverse/${{ env.branch }}/${{ env.us_date }}/${{ env.sha_short }}/${{ matrix.config.build-code }}/

docs/release-guide/README.md

@@ -4,7 +4,7 @@ This is the process we follow when releasing a new version of Cesium for Omniver
 
 1. [Release a new version of Cesium for Omniverse Samples](#releasing-a-new-version-of-cesium-for-omniverse-samples).
 3. Make sure the latest commit in `main` is passing CI.
-4. Download the latest build from S3. In the AWS management console (old AWS account), go to the bucket [`cesium-travis-builds/cesium-omniverse/main`](https://s3.console.aws.amazon.com/s3/buckets/cesium-travis-builds?region=us-east-1&prefix=cesium-omniverse/main/&showversions=false), find the appropriate date and commit hash to download the CentOS and Windows zip files (e.g. `CesiumForOmniverse-Linux-xxxxxxx.zip` and `CesiumForOmniverse-Windows-xxxxxxx.zip`)
+4. Download the latest build from S3. In the AWS management console (InternalServices AWS account), go to the bucket [`cesium-builds/cesium-omniverse/main`](https://s3.console.aws.amazon.com/s3/buckets/cesium-builds?region=us-east-1&prefix=cesium-omniverse/main/&showversions=false), find the appropriate date and commit hash to download the CentOS and Windows zip files (e.g. `CesiumForOmniverse-Linux-xxxxxxx.zip` and `CesiumForOmniverse-Windows-xxxxxxx.zip`)
 5. Verify that the Linux package loads in USD Composer (see instructions below).
 6. Verify that the Windows package loads in USD Composer (see instructions below).
 7. Update the project `VERSION` in [CMakeLists.txt](../../CMakeLists.txt).
@@ -18,7 +18,7 @@ This is the process we follow when releasing a new version of Cesium for Omniver
 15. Tag the release, e.g. `git tag -a v0.0.0 -m "0.0.0 release"`.
 16. Push the tag, e.g. `git push origin v0.0.0`.
 17. Wait for CI to pass.
-18. Download the latest build from S3. In the AWS management console (old AWS account), go to the bucket [`cesium-travis-builds/cesium-omniverse`](https://s3.console.aws.amazon.com/s3/buckets/cesium-travis-builds?prefix=cesium-omniverse/&region=us-east-1), find the folder with the new tag and download the CentOS and Windows zip files (e.g. `CesiumForOmniverse-Linux-v0.0.0.zip` and `CesiumForOmniverse-Windows-v0.0.0.zip` )
+18. Download the latest build from S3. In the AWS management console (InternalServices AWS account), go to the bucket [`cesium-builds/cesium-omniverse`](https://s3.console.aws.amazon.com/s3/buckets/cesium-builds?prefix=cesium-omniverse/&region=us-east-1), find the folder with the new tag and download the CentOS and Windows zip files (e.g. `CesiumForOmniverse-Linux-v0.0.0.zip` and `CesiumForOmniverse-Windows-v0.0.0.zip` )
 19. Create a new release on GitHub: https://github.com/CesiumGS/cesium-omniverse/releases/new.
     * Chose the new tag.
     * Copy the changelog into the description. Follow the format used in previous releases.