- Jul 20, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jul 05, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jul 01, 2021
-
-
Simon McVittie authored
We exercise scout via the .deb packaging, there's little point in doing a redundant set of builds. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 30, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 17, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 15, 2021
-
-
Simon McVittie authored
scan-build doesn't understand `__attribute__((cleanup))` (see https://bugs.llvm.org/show_bug.cgi?id=3888 ) so it will report increasingly many false-positive memory leaks in this codebase. It's sufficiently time-consuming that it doesn't make sense to run it as part of our usual pipeline. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This build pass takes long enough that it makes sense to parallelize. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
The SteamLinuxRuntime scripts have phased out support for populating a depot directory with a mixture of scout and soldier, because that doesn't really make sense for a game or a compat tool: each native Linux game, and each compat tool used to run non-native games, expects to run in one particular environment (scout or soldier or something else) and using any other environment would be incorrect. However, tests/pressure-vessel/containers.py currently expects to work with a directory that contains both scout and soldier. For now, we'll download scout and soldier separately, then mash them together into the same directory. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 09, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 08, 2021
-
-
Simon McVittie authored
When we push to master it's usually for one of three reasons: 1. We merged a merge request 2. We pushed the "release vX.Y.Z" commit, together with a tag 3. We pushed some other trivial change directly When we merged a merge request, immediately running CI is not necessarily very helpful, because we already ran it for the branch that's getting merged. If we pushed a release commit and a tag, we want the CI pipeline for the tag to take priority over the CI pipeline for the release commit. If we pushed a trivial change, it might not even need CI (if it's just a change to a README, or similar), but if it does, we can trigger it manually. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
If we avoid running pipelines for merge requests, then the status of the pipeline for the branch will show up. The pipeline for the branch can be more comprehensive because it has access to project-specific masked and protected variables. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
To get the deploy job to run, the tags need to be configured as protected so they get to see all the necessary variables. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
It's confusing for it to appear in the job graph when we won't be launching it the majority of the time. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
When combined with changes to SteamLinuxRuntime scripts, this will let us do a new pressure-vessel release and incorporate it into soldier/sniper/etc. depots, without having to do a whole release of scout to provide the new pressure-vessel. These releases don't include anything that we didn't already publish in Gitlab artifacts, and they're relatively small, so they might as well be public immediately (unlike the full scout releases, which we avoid publishing before they are final, both because they are rather large and because game developers could get compatibility issues if they build against a non-finalized scout runtime). Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 07, 2021
-
-
Simon McVittie authored
The production build uses dpkg packages, built with -O2 -g and stripped. This is similar to what we currently extract from a scout SDK build; but if we do it here, we can decouple the pressure-vessel release process from the scout release process, making it possible to issue a new pressure-vessel release for use with pre-existing scout/soldier runtimes much quicker than the time needed to do an entire scout release. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 04, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 01, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- May 26, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- May 18, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- May 11, 2021
-
-
Simon McVittie authored
By including this in libsteam-runtime-tools-0-helpers, we reduce the number of modules we need to manage and keep in sync. The rest of libcapsule isn't actively used yet, so this is a significant simplification. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- May 07, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Apr 30, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Apr 21, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We never actually ran this, because it doesn't have machine-readable output. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We now use our own check-vulkan executable instead of vulkaninfo, because it can give us more machine-readable information about non-default GPUs. A side benefit is one less dependency. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Apr 19, 2021
-
-
Simon McVittie authored
The latest version in SteamLinuxRuntime requires a ${source_dir}/common directory available. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Apr 15, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Apr 14, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Apr 12, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Mar 31, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-