9ab2f662f8
Merge pull request #1819 from secondlife/brad/tag-release
2024-07-01 10:37:21 -07:00
32b912af9a
Make sure TAG_ID actually gets added to GITHUB_ENV
2024-06-20 17:15:16 -07:00
aa6161ca94
Shorten SHA value used in tag id and attempt to fix js/yaml syntax error
2024-06-20 17:10:00 -07:00
e165be0007
Attempt to use provided GITHUB_TOKEN and generate tag id from inputs
2024-06-18 14:31:41 -07:00
6393e88ca4
Merge remote-tracking branch 'origin/develop' into brad/webrtc-voice-develop
2024-06-18 11:55:30 -07:00
05efb1494d
Fix yaml indentation of javascript snippet in tag-release workflow
2024-06-17 19:17:18 -07:00
f5659945b5
Fix secret name since GITHUB_ prefix is reserved
2024-06-17 18:54:45 -07:00
3da16d1899
Attempt to fix tag-release workflow by moving conditional secrets usage into env
2024-06-17 18:38:00 -07:00
352dff6830
Attempt to fix workflow syntax in new tag-release workflow ( #1792 )
2024-06-17 18:32:24 -07:00
dd64c39d64
Pass through input channel to select the tag channel name
2024-06-17 17:55:29 -07:00
b9a8b3b240
Update naming and add options to tag-release workflow_dispatch.
2024-06-17 17:43:02 -07:00
84a221e7dd
Renamed tag-nightly.yaml to generalize it to other tags when using workflow_dispatch
2024-06-17 17:41:53 -07:00
0e1e1685d4
Skip the actual tag update step gracefully until we have proper tokens set up
2024-06-13 18:14:21 -07:00
b9f287815a
Add new viewer_channel detection for develop branch
2024-06-13 17:55:05 -07:00
41cb778fb0
Initial work setting up scheduled releases for develop branch.
2024-06-13 17:41:17 -07:00
5e60392c27
Merge branch 'develop' of github.com:secondlife/viewer into roxie/webrtc-voice
2024-06-13 14:59:28 -07:00
ed34782283
Merge branch 'main' of github.com:secondlife/viewer into roxie/webrtc-voice
2024-06-11 18:43:34 -07:00
ef9f4b38e9
Merge branch 'main' into DRTVWR-600-maint-A
2024-06-11 17:51:35 +03:00
2e41f5a35e
Try to get sign-and-package-windows job a runner to run on
2024-06-10 16:11:29 -07:00
a0b3021bdc
Trim trailing whitespace
...
Start trimming trailing whitespace, but limit the blast radius to a
handful of file types.
2024-05-29 08:10:00 -07:00
3a212d9608
Merge branch 'spaces-merge' into roxie/webrtc-voice
2024-05-20 12:59:59 -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
4af9128db1
Merge branch 'main' of https://github.com/secondlife/viewer into roxie/webrtc-voice
2024-05-06 16:40:12 -07: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
cac7023996
SL-20546: Append generated release notes body to our explicit body.
...
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 9e99bb04a3
2024-03-01 16:13:29 -05:00
e0ae227d0a
SL-20546: Add viewer channel and full version to GitHub release page.
...
(cherry picked from commit f71662225e
2024-03-01 16:13:28 -05:00
b242d696ba
Merge branch 'main' of github.com:secondlife/viewer
...
on promotion of DRTVWR-489 Emoji viewer.
2024-03-01 11:15:53 -05:00
1204468415
Merge DRTVWR-489 to main on promotion of Emoji viewer ( #673 ).
2024-03-01 10:23:56 -05:00
b42e01d7ac
Reference updated action-gh-release@v1
...
instead of the branch that got pulled.
2024-02-28 08:45:12 -05:00
27b298d8bc
Base generated release notes on new floating tag 'release'
...
instead of on the current tag 7.1.2-release.
2024-02-26 17:05:56 -05:00
88ebb92f05
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.
2024-02-26 15:51:31 -05:00
4edd78f2e5
Try basing release notes on github.sha rather than github.ref_name.
2024-02-26 13:26:29 -05:00
c6a6db8488
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"}]
2024-02-26 12:20:31 -05:00
a908b4cfa9
Try to generate release notes for this specific branch.
...
Also try to cross-reference release page and build page.
2024-02-26 11:23:47 -05:00
ae6aa3fc41
Merge branch 'main' into DRTVWR-588-maint-W
2024-02-23 19:16:08 +02:00
0f2248ea12
Improving issue templates. ( #877 )
...
making ordering explicit, and disabling blank issue submission to force
triage label to be set.
2024-02-22 13:01:49 -08:00
ffef19843b
Delete .github/ISSUE_TEMPLATE/issue_template.md
2024-02-22 11:28:44 -05:00
b9ac5e8433
Update issue_template.md
2024-02-22 11:26:54 -05:00
e452eeb816
Update issue_template.md
2024-02-22 11:24:55 -05:00
4b24b0d933
Create issue_template.md
...
Issue template for the "blank issue" option
2024-02-22 10:28:10 -05:00
6ae83f06d8
Merge branch 'main' into DRTVWR-588-maint-W
2024-02-21 22:01:44 +02:00
ff543b744e
Engage new viewer-build-util/which-branch with relnotes output.
...
Put whatever release notes we retrieve into the generated release page.
2024-02-15 11:21:31 -05:00
255bb8504d
Update cla.yaml allowlist to clear spurious errors ( #804 )
2024-02-14 09:54:46 -08:00
19b808316b
Merge branch 'main' of github.com:secondlife/viewer
2024-02-09 13:31:30 -05:00
9b51fee9bc
Rename config.yaml to config.yml
...
Issue template configuration is the only github configuration file I've found which does not support both `*.yaml` and `*.yml` extensions. Drat.
2024-02-07 13:24:35 -08:00
95f213115b
Add link to feedback portal
...
Provide a link to feedback.secondlife.com from the issue creation page.
2024-02-05 16:09:54 -08:00
27e3fdc957
build.yaml: Build shared branches
...
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-31 13:26:14 -08:00
71d0e6f400
Merge branch 'main' into DRTVWR-588-maint-W
2024-01-31 20:12:03 +02:00
c0861e9366
Merge pull request #692 from secondlife/vir-linden-issue-templates-1
...
Update enhancement.md
2024-01-30 09:35:03 -05:00
9f0a5a3385
Merge branch 'main' into DRTVWR-588-maint-W
2024-01-29 22:18:23 +02:00
00962fd397
Update enhancement.md
2024-01-29 12:42:28 -05:00
a9158943a8
Update bug.yaml
2024-01-29 12:38:11 -05:00
cb14e9a074
Create enhancement.md
2024-01-24 12:32:10 -06:00
bc4bf9e207
Create bug.yaml
2024-01-24 12:30:45 -06:00
6555fb3409
SL-20546: Use viewer-build-util@v1 instead of PR branch.
...
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-18 21:35:48 -05:00
834cc3d1e0
SL-20546: Test new viewer-build-util branch pr-branch.
2024-01-18 15:21:15 -05:00
dd0ec112fe
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.
2024-01-18 13:43:34 -05:00
09f66828ba
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.
2024-01-18 13:34:40 -05:00
ff1741ceca
DRTVWR-601: Use viewer-build-util/which-branch to determine branch.
...
(cherry picked from commit 2c5066f1fc
2024-01-18 13:29:39 -05:00
6e8d4f4846
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 b782ab73e6
2024-01-18 13:29:39 -05:00
fea1d9f4d2
SL-20546: Merge branch 'DRTVWR-588-maint-W' into sl-20546.
2024-01-18 13:15:32 -05:00
e2ba2f9c45
Move "team:viewer" label action to labeler.yaml.
...
This avoids the need for a separate job step.
2024-01-12 17:26:46 -05:00
0730681b8a
Fold PR labeling into existing label.yaml.
2024-01-12 17:26:46 -05:00
36fff90f90
Grant write permission for pull requests.
2024-01-12 17:26:46 -05:00
f5d6af9cfc
Add a workflow to auto-label new PRs with team:viewer.
...
When a PR appears on the QA board, QA wants to know whose team it came from.
So every PR on the viewer repo should be labeled with team:viewer.
2024-01-12 17:26:46 -05:00
793bed7d06
Merge branch 'main' into DRTVWR-489
...
# Conflicts:
# indra/newview/fonts/DejaVu-license.txt
# indra/newview/fonts/DejaVuSans-Bold.ttf
# indra/newview/fonts/DejaVuSans-BoldOblique.ttf
# indra/newview/fonts/DejaVuSans-Oblique.ttf
# indra/newview/fonts/DejaVuSans.ttf
# indra/newview/fonts/DejaVuSansMono.ttf
2023-12-15 07:06:15 +02:00
4b98ae6e8a
Merge branch 'DRTVWR-587-maint-V' into DRTVWR-588-maint-W
...
# Conflicts:
# indra/newview/llspatialpartition.cpp
2023-12-14 02:47:44 +02:00
eff5958c11
Fix formatting in autobuild.xml (indents in close tags)
2023-12-05 20:37:21 +01:00
c9cd5631e4
Merge branch 'main' into DRTVWR-489
2023-12-05 03:37:06 +01:00
5416d94d07
Merge branch 'DRTVWR-587-maint-V' into signal/simple-release
2023-11-21 08:07:20 -08:00
c0ab8b8f0c
Switch to viewer-build-util@v1
...
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-20 16:23:05 -08:00
9b50c50bf2
Only download release artifacts for release
...
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-20 08:13:59 -08:00
96deda3f63
SL-20546: build-variables viewer branch no longer exists.
2023-11-15 09:52:06 -05:00
819604d2ce
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.
2023-11-15 09:44:38 -05:00
6654ad14ee
SL-20546: Add PyGithub to installed Python packages.
2023-11-14 14:30:44 -05:00
59eeaed118
SL-20546: Try harder to infer the branch corresponding to build tag.
2023-11-14 14:20:51 -05:00
9e99bb04a3
SL-20546: Append generated release notes body to our explicit body.
...
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.
2023-11-14 04:09:56 -05:00
f71662225e
SL-20546: Add viewer channel and full version to GitHub release page.
2023-10-31 10:50:39 -04:00
0fe058f9b8
Fix build.yaml line that got dropped in the merge.
2023-10-26 10:37:19 -07:00
673b3309dd
Merge remote-tracking branch 'origin/main' into DRTVWR-559
2023-10-25 16:12:13 -07:00
e4d6a08941
SL-18837: Build all branches on GitHub now.
2023-10-25 14:39:31 -04:00
2e8e96cfbc
PIE-1057: viewer-build-util's azure branch has been merged to main.
2023-10-18 17:44:07 -04:00
f6d872a027
PIE-1057: Pass sign-pkg-windows@azure the Azure-related secrets.
2023-10-13 15:11:30 -04:00
549e56572b
PIE-1057: Engage viewer-build-util azure branch.
2023-10-12 17:25:30 -04:00
7648978397
SL-18837: Name the release for the build number to readily find it.
2023-10-05 15:25:54 -04:00
1684d62499
SL-19242: Remove signing and packaging from viewer_manifest.py
...
for Mac and Windows. That's now done by subsequent jobs in the GitHub build.
Remove workflow step to upload installers before signing and packaging jobs.
Remove from viewer_manifest.py conditionals for 32-bit Windows or Mac.
Also bump to actions/checkout@v4, per dependabot.
2023-10-03 19:02:40 -04:00
e2ea42cb6a
SL-19242: Expect and pass Apple "Team ID" rather than "ASC Provider".
...
"ASC Provider" was a credential accepted by altool, but switching from altool
to notarytool requires a Team ID instead.
Expect to find TEAM_ID in our repository secret NOTARIZE_CREDS_MACOS. Extract
it and pass it to sign-pkg-mac.
2023-10-02 16:52:11 -04:00
d2d3599080
Attempt to fix SL-19242 notarize creds secrets loading
2023-09-25 14:02:26 -07:00
50e3d4020d
SL-19242: Reference the actual stored GitHub repo secrets.
...
Add a Mac signing step to unpack the credentials bundled into
NOTARIZE_CREDS_MACOS so viewer-build-util/sign-pkg-mac need not know about
that peculiarity of our secrets formatting.
2023-09-25 11:19:38 -04:00
bb7f023aaa
Remove win32 build from DRTVWR-559 github build
2023-09-20 13:56:01 -07:00
e8dfbbaf88
SL-19242: Pass channel and imagename to sign-pkg-mac/action.yaml.
...
The viewer_manifest.py logic to determine the name of the viewer installer
.dmg is a little convoluted. Make it tell viewer-build-util/sign-pkg-mac that
name, rather than passing it all the relevant inputs and composing it
redundantly.
sign-pkg-mac also wants the viewer channel to determine the application name.
2023-09-20 11:34:56 -04:00
763fcb02b8
SL-19242: Move comments out of YAML parameter text.
2023-09-19 09:15:30 -04:00
bd8ecbb389
SL-19242: Typo in changing from inline to reusable action.
2023-09-18 22:43:16 -04:00
1184c383e2
SL-19242: release job now depends on package jobs
...
and uses new viewer-build-util/release-artifacts action.
2023-09-18 22:39:43 -04:00
7c351379fc
SL-19242: Retrieve and decode Windows signing cert, pass to action.
2023-09-15 15:17:40 -04:00
b02249546e
SL-19243: Directly reference action subdirs in viewer-build-util
...
instead of trying to checkout viewer-build-util (which doesn't work) and then
reference action subdirs from the filesystem.
Also engage (initial placeholder) actions to sign and package the
platform-specific application artifacts.
2023-09-12 16:28:09 -04:00
3e86f26b40
SL-19243: Try to convince GitHub that ./.util is really a path.
2023-09-12 13:55:08 -04:00
d795b49f16
SL-19243: Job step 'uses' must specify action.yaml file
...
instead of having it implied by specifying the containing directory.
2023-09-12 12:50:13 -04:00
0992a0af3b
SL-19243: Use consolidated viewer-build-util
...
instead of distinct viewer-post-bugsplat-{windows,mac} repos.
2023-09-12 12:46:28 -04:00
29300a1fd3
SL-19242: Try harder to post artifacts containing exactly app image.
...
In a Windows build tree, we don't actually have an app-named top directory, so
don't package its containing directory -- just the app dir itself, e.g.
"newview/Release".
In a Mac build tree, though we do have "Second Life Mumble.app", its parent
directory also contains other large stuff. Try posting a temp directory
containing a symlink to the .app.
Ditch the "!*.bat" exclusion: the presence of a second path (even an
exclusion) changes how upload-artifact nests its contents.
2023-09-11 10:07:51 -04:00
63d5d38e36
SL-18837: Stop failing build.sh if there's no installer.
...
This unblocks ReleaseOS builds, and also preps for SL-19242.
Streamline build.sh's Uploads section.
2023-09-08 17:24:04 -04:00
2d04cc14d3
SL-19242: Post -app artifact, not -exe, with entire install image.
...
Previously we posted Windows-exe, macOS-exe artifacts that were a little
inconsistent: Windows-exe contained just the Windows executable, whereas
macOS-exe contained the whole .app tree (but without the .app directory).
Change to post Windows-app, macOS-app artifacts that each contain the whole
viewer install image, including the top-level application name directory. This
is what we'll need to codesign and notarize.
2023-09-08 17:01:46 -04:00
c87d9c635b
SL-18837: Suppress ReleaseOS for now.
2023-09-08 14:30:05 -04:00
77227cf5c4
SL-18837: Suppress BUGSPLAT_DB for ReleaseOS builds.
2023-09-07 14:09:54 -04:00
bac73831c0
SL-18837: String literals are single-quoted in GitHub expressions.
2023-09-07 11:48:15 -04:00
949909013e
SL-18837: Segregate ReleaseOS artifacts; don't even upload.
...
Eliminate references to (no longer set) matrix.addrsize.
2023-09-07 11:38:00 -04:00
Brad Linden