83c1f45dba
Download osx artifacts to working directory
2024-08-06 00:26:43 -07:00
07573f7e10
allow paths with spaces
2024-08-05 23:16:48 -07:00
293187e04b
Build mac symbols for multiple binaries/dynamic libraries and upload them all to bugsplat
2024-08-05 18:17:03 -07:00
2e41f5a35e
Try to get sign-and-package-windows job a runner to run on
2024-06-10 16:11:29 -07:00
e1623bb276
Merge pull request #1489 from secondlife/brad/fix-mac-channel
...
Fix channel detection for mac builds
2024-05-16 09:55:50 -07:00
8011d3f457
Fix channel detection for mac builds
2024-05-15 16:08:04 -07:00
7feec9998e
Move all release_run logic into setvar job.
2024-05-15 15:12:52 -07:00
0960ae7892
Experiment with getting manually triggered workflow builds to optionally do a release
2024-05-15 14:49:07 -07:00
1f0b80f709
Streamline the new workflow `RELEASE_RUN` logic a little.
...
Since downstream jobs reference the output of the new `setvar` job, instead of
directly referencing global `env.RELEASE_RUN`, no need to set `RELEASE_RUN` in
the global environment.
2024-05-15 17:15:25 -04:00
f822193974
Make env.RELEASE_RUN the empty string if false
...
not the string "false", which is true.
2024-05-15 16:08:54 -04:00
18c1458409
Can't reference global env in job.if either.
2024-05-15 16:01:26 -04:00
9d30040dfe
Try to work around workflow YAML env setting limitation.
2024-05-15 15:57:50 -04:00
a4d2574df2
Run ReleaseOS builds, but only when a release page is requested.
2024-05-13 13:46:42 -04:00
4f70946048
Fix syntax error in build.yaml to enable Windows ReleaseOS
2024-05-11 10:14:49 -04:00
afd726979a
Turn on GH Windows ReleaseOS build
2024-05-11 09:58:22 -04:00
6eeef10cda
Update build.yaml
2024-05-02 10:08:46 -04:00
eb0f963b46
Update build.yaml
2024-05-02 09:48:26 -04:00
7f23f160d7
trim trailing whitespace
2024-05-01 17:51:44 +01:00
65495ba765
set viewer channel from branch
2024-05-01 16:42:09 +01:00
a3602d660c
Merge pull request #1323 from secondlife/main
...
Update from main
2024-04-24 16:02:42 -04:00
6ca4dfdb56
Update build.yaml
2024-04-19 16:16:26 -04:00
a65de93541
https://github.com/secondlife/viewer/issues/1286 - branch var from github.repository
2024-04-19 19:51:19 +01:00
f39987f382
https://github.com/secondlife/viewer/issues/1286 - branch var from github.repository
2024-04-19 19:47:46 +01:00
c2730b4fff
https://github.com/secondlife/viewer/issues/1286 - determine viewer_channel from branch name in builds
2024-04-19 16:44:59 +01:00
b340042a3f
https://github.com/secondlife/viewer/issues/1214 - Update cla.yaml
2024-04-16 12:19:09 -04:00
0f94ea86d4
CI: adopt xz compression
...
Move towards packaging artifacts with xz, which offers higher compression ratios and faster decode time.
2024-04-11 15:18:42 -07:00
7fa24d636e
CI: Remove python-version from matrix
...
Drop python version from matrix configuration as it's always 3.11.
2024-04-11 00:16:17 -07:00
78174fc865
Merge remote-tracking branch 'origin/main' into DRTVWR-588-maint-W
...
# Conflicts:
# .github/workflows/build.yaml
2024-03-27 00:14:56 +02:00
c810a409e2
Merge GLTF PBR Maint 2 to main.
2024-03-26 16:55:32 -04:00
231062d532
Fix github actions dependency deprecations
2024-03-12 17:49:19 -07:00
091ee67ec5
Merge branch 'main' into DRTVWR-588-maint-W
2024-03-09 19:46:09 +02:00
74ee07d942
To test for presence of secrets, set environment variables.
...
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-05 14:23:32 -05:00
73a12f5529
Enclose 'if:' expressions in ${{ ... }}.
...
The previous construct produced:
Unrecognized named-value: 'secrets'. Located at position 1 within expression:
secrets.AZURE_KEY_VAULT_URI && ...
2024-03-05 13:50:38 -05:00
6328cb7817
Make signing and symbol posting jobs conditional on secrets.
...
Specifically, when secrets aren't available (e.g. for external PRs), skip the
affected steps.
2024-03-05 13:36:18 -05:00
e07bf1c0a2
Do not automatically close issues ( #929 )
...
Mark issues as stale but do not close them.
2024-03-04 17:32:35 -08:00
9b8800f216
Now that viewer-build-util@relnotes has merged to v1, use @v1.
2024-03-01 16:43:15 -05:00
00d7fef75e
Reference updated action-gh-release@v1
...
instead of the branch that got pulled.
(cherry picked from commit b42e01d7ac
2024-03-01 16:19:02 -05:00
3ee3e011ff
Base generated release notes on new floating tag 'release'
...
instead of on the current tag 7.1.2-release.
(cherry picked from commit 27b298d8bc
2024-03-01 16:19:01 -05:00
7ad13c8511
Leverage action-gh-release's new previous_tag input.
...
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 88ebb92f05
2024-03-01 16:19:01 -05:00
7c52db381c
Try basing release notes on github.sha rather than github.ref_name.
...
(cherry picked from commit 4edd78f2e5
2024-03-01 16:19:01 -05:00
d7e6a7dbd0
Try basing the GH release on github.ref_name instead of github.ref.
...
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 c6a6db8488
2024-03-01 16:19:01 -05:00
603d3a865a
Try to generate release notes for this specific branch.
...
Also try to cross-reference release page and build page.
(cherry picked from commit a908b4cfa9
2024-03-01 16:19:01 -05:00
9f326f5b96
Engage new viewer-build-util/which-branch with relnotes output.
...
Put whatever release notes we retrieve into the generated release page.
(cherry picked from commit ff543b744e
2024-03-01 16:19:01 -05:00
a8cd70123b
SL-20546: PyGithub was only needed for local which_branch.py.
...
Now that which_branch.py has moved to viewer-build-util, so has the PyGithub
dependency.
(cherry picked from commit dd0ec112fe
2024-03-01 16:13:29 -05:00
8f68199ccd
SL-20546: Use branch for autobuild package as well as release page.
...
which_branch.py has moved to viewer-build-util as a reusable action.
(cherry picked from commit 09f66828ba
2024-03-01 16:13:29 -05:00
9b3d4325d9
DRTVWR-601: Use viewer-build-util/which-branch to determine branch.
...
(cherry picked from commit 2c5066f1fcff1741ceca
2024-03-01 16:13:29 -05:00
8590ce0533
DRTVWR-601: Make autobuild set vcs_url, vcs_branch, vcs_revision
...
in viewer's autobuild-package.xml.
Ensure that AUTOBUILD_VCS_BRANCH is set before the build.
(cherry picked from commit b782ab73e66e8d4f4846
2024-03-01 16:13:29 -05:00
cfbef4e4f9
SL-20546: Make dependency on build job explicit, not indirect.
...
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 819604d2ce
2024-03-01 16:13:29 -05:00
e4865db0ca
SL-20546: Add PyGithub to installed Python packages.
...
(cherry picked from commit 6654ad14ee
2024-03-01 16:13:29 -05:00
a13e70aeff
SL-20546: Try harder to infer the branch corresponding to build tag.
...
(cherry picked from commit 59eeaed118
2024-03-01 16:13:29 -05:00
Roxie Linden