summaryrefslogtreecommitdiff
path: root/.github/workflows
AgeCommit message (Collapse)Author
2024-04-16https://github.com/secondlife/viewer/issues/1214 - Update cla.yamlVir Linden
2024-04-11CI: adopt xz compressionBennett Goble
Move towards packaging artifacts with xz, which offers higher compression ratios and faster decode time.
2024-04-11CI: Remove python-version from matrixBennett Goble
Drop python version from matrix configuration as it's always 3.11.
2024-03-27Merge remote-tracking branch 'origin/main' into DRTVWR-588-maint-WAndrey Lihatskiy
# Conflicts: # .github/workflows/build.yaml
2024-03-26Merge GLTF PBR Maint 2 to main.Nat Goodspeed
2024-03-12Fix github actions dependency deprecationsBrad Linden
2024-03-09Merge branch 'main' into DRTVWR-588-maint-WAndrey Lihatskiy
2024-03-05To test for presence of secrets, set environment variables.Nat Goodspeed
From https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#using-secrets-in-a-workflow : "Secrets cannot be directly referenced in if: conditionals. Instead, consider setting secrets as job-level environment variables, then referencing the environment variables to conditionally run steps in the job."
2024-03-05Enclose 'if:' expressions in ${{ ... }}.Nat Goodspeed
The previous construct produced: Unrecognized named-value: 'secrets'. Located at position 1 within expression: secrets.AZURE_KEY_VAULT_URI && ...
2024-03-05Make signing and symbol posting jobs conditional on secrets.Nat Goodspeed
Specifically, when secrets aren't available (e.g. for external PRs), skip the affected steps.
2024-03-04Do not automatically close issues (#929)Signal Linden
Mark issues as stale but do not close them.
2024-03-01Now that viewer-build-util@relnotes has merged to v1, use @v1.Nat Goodspeed
2024-03-01Reference updated action-gh-release@v1Nat Goodspeed
instead of the branch that got pulled. (cherry picked from commit b42e01d7acf5d4c55612c3a7df0e1ff6ee5ed951)
2024-03-01Base generated release notes on new floating tag 'release'Nat Goodspeed
instead of on the current tag 7.1.2-release. (cherry picked from commit 27b298d8bc720ff315c8e74cc5bff9ff9ead0552)
2024-03-01Leverage action-gh-release's new previous_tag input.Nat Goodspeed
This should (!) allow us to generate full release notes relative to the previous viewer release, instead of letting action-gh-release guess incorrectly. Also try again to add to the release page a back-link to the specific build. (cherry picked from commit 88ebb92f05dade00cc8fc519cc062a458ecd48f2)
2024-03-01Try basing release notes on github.sha rather than github.ref_name.Nat Goodspeed
(cherry picked from commit 4edd78f2e54b3cd2e0b0a4b9300dfc669231dd98)
2024-03-01Try basing the GH release on github.ref_name instead of github.ref.Nat Goodspeed
Using github.ref as action-gh-release's target_commitish produces: ⚠️ GitHub release failed with status: 422 [{"resource":"Release","code":"invalid","field":"target_commitish"}] (cherry picked from commit c6a6db8488a8b3e7ea6534fbf5e2fe2b17864421)
2024-03-01Try to generate release notes for this specific branch.Nat Goodspeed
Also try to cross-reference release page and build page. (cherry picked from commit a908b4cfa98716d4a838fc1e5a6789faa15d16cf)
2024-03-01Engage new viewer-build-util/which-branch with relnotes output.Nat Goodspeed
Put whatever release notes we retrieve into the generated release page. (cherry picked from commit ff543b744ee0b0fd4dd90b46419ae50a570572ab)
2024-03-01SL-20546: PyGithub was only needed for local which_branch.py.Nat Goodspeed
Now that which_branch.py has moved to viewer-build-util, so has the PyGithub dependency. (cherry picked from commit dd0ec112fe5ded8ed5f69b72b3df26343ca12d35)
2024-03-01SL-20546: Use branch for autobuild package as well as release page.Nat Goodspeed
which_branch.py has moved to viewer-build-util as a reusable action. (cherry picked from commit 09f66828ba573515c3766cce32f4746b8189efcf)
2024-03-01DRTVWR-601: Use viewer-build-util/which-branch to determine branch.Nat Goodspeed
(cherry picked from commit 2c5066f1fcc0c9f145698ef3aaec72d27bce7181) (cherry picked from commit ff1741cecae0fac6d94507fa4a6e4662219af707)
2024-03-01DRTVWR-601: Make autobuild set vcs_url, vcs_branch, vcs_revisionNat Goodspeed
in viewer's autobuild-package.xml. Ensure that AUTOBUILD_VCS_BRANCH is set before the build. (cherry picked from commit b782ab73e640e434e4ed67fa8dfc951f09757585) (cherry picked from commit 6e8d4f48466a5bbad2fcc27bc2877a30e575d4ce)
2024-03-01SL-20546: Make dependency on build job explicit, not indirect.Nat Goodspeed
The release job has been dependent on sign-and-package-windows and sign-and-package-mac, each of which depends on build. But that indirect dependency doesn't convey access to ${{ needs.build.outputs.xxx }}. Add the build job to direct dependencies so release can access its outputs. (cherry picked from commit 819604d2cee6d4527cc436bebfacddf8642635ff)
2024-03-01SL-20546: Add PyGithub to installed Python packages.Nat Goodspeed
(cherry picked from commit 6654ad14eed674e894d2903e0f2ea37c4e806c0f)
2024-03-01SL-20546: Try harder to infer the branch corresponding to build tag.Nat Goodspeed
(cherry picked from commit 59eeaed1187e7592fd83380045916f2d8b9d58e7)
2024-03-01SL-20546: Append generated release notes body to our explicit body.Nat Goodspeed
For a tag build that generates a release page, try to deduce the git branch to which the tag we're building corresponds and add that to release notes. (cherry picked from commit 9e99bb04a32f2ecc0f0b99686ce5a7adb356596d)
2024-03-01SL-20546: Add viewer channel and full version to GitHub release page.Nat Goodspeed
(cherry picked from commit f71662225eadf1589f5331e763e02e0bb1b72137)
2024-02-28Reference updated action-gh-release@v1Nat Goodspeed
instead of the branch that got pulled.
2024-02-26Base generated release notes on new floating tag 'release'Nat Goodspeed
instead of on the current tag 7.1.2-release.
2024-02-26Leverage action-gh-release's new previous_tag input.Nat Goodspeed
This should (!) allow us to generate full release notes relative to the previous viewer release, instead of letting action-gh-release guess incorrectly. Also try again to add to the release page a back-link to the specific build.
2024-02-26Try basing release notes on github.sha rather than github.ref_name.Nat Goodspeed
2024-02-26Try basing the GH release on github.ref_name instead of github.ref.Nat Goodspeed
Using github.ref as action-gh-release's target_commitish produces: ⚠️ GitHub release failed with status: 422 [{"resource":"Release","code":"invalid","field":"target_commitish"}]
2024-02-26Try to generate release notes for this specific branch.Nat Goodspeed
Also try to cross-reference release page and build page.
2024-02-21Merge branch 'main' into DRTVWR-588-maint-WAndrey Lihatskiy
2024-02-15Engage new viewer-build-util/which-branch with relnotes output.Nat Goodspeed
Put whatever release notes we retrieve into the generated release page.
2024-02-14Update cla.yaml allowlist to clear spurious errors (#804)Brad Linden
2024-01-31build.yaml: Build shared branchesBennett Goble
We're currently building every single commit pushed to Github. This is racking up $20k in build charges a month and is generally superfluous. This changeset alters build triggers so that builds automatically run if they are committed to a **shared branch**: - `release/*` - A release stabilization branch - `project/*` - A project viewer branch - `main/*` - The default/stable branch PR commits are also automatically built. ...need to build another commit? Developers can trigger one using a manual workflow run.
2024-01-18SL-20546: Use viewer-build-util@v1 instead of PR branch.Nat Goodspeed
The fix we wanted was on the pr-branch branch of the viewer-build-util repo. Now that it's been published as v1.1.2, the updated v1 tag references the fix, so revert mention to @v1.
2024-01-18SL-20546: Test new viewer-build-util branch pr-branch.Nat Goodspeed
2024-01-18SL-20546: PyGithub was only needed for local which_branch.py.Nat Goodspeed
Now that which_branch.py has moved to viewer-build-util, so has the PyGithub dependency.
2024-01-18SL-20546: Use branch for autobuild package as well as release page.Nat Goodspeed
which_branch.py has moved to viewer-build-util as a reusable action.
2024-01-18DRTVWR-601: Use viewer-build-util/which-branch to determine branch.Nat Goodspeed
(cherry picked from commit 2c5066f1fcc0c9f145698ef3aaec72d27bce7181)
2024-01-18DRTVWR-601: Make autobuild set vcs_url, vcs_branch, vcs_revisionNat Goodspeed
in viewer's autobuild-package.xml. Ensure that AUTOBUILD_VCS_BRANCH is set before the build. (cherry picked from commit b782ab73e640e434e4ed67fa8dfc951f09757585)
2024-01-18SL-20546: Merge branch 'DRTVWR-588-maint-W' into sl-20546.Nat Goodspeed
2023-12-14Merge branch 'DRTVWR-587-maint-V' into DRTVWR-588-maint-WAndrey Lihatskiy
# Conflicts: # indra/newview/llspatialpartition.cpp
2023-11-21Merge branch 'DRTVWR-587-maint-V' into signal/simple-releaseSignal Linden
2023-11-20Switch to viewer-build-util@v1Bennett Goble
Switch the build workflow from targeting the `main` branch of viewer-build-util (which may receive breaking changes) to the stable `v1` major version tag.
2023-11-20Only download release artifacts for releaseBennett Goble
Only download and publish installers on public releases. This simplifies the release process, as the flatten_files utility from viewer-build-utils is not necessary this way. More importantly, it doesn't clutter public releases with files that shouldn't be published such as debug symbols.
2023-11-15SL-20546: build-variables viewer branch no longer exists.Nat Goodspeed