Skip to content
Snippets Groups Projects
Commit b0f5998e authored by Simon McVittie's avatar Simon McVittie
Browse files

Re-brand from soldier to sniper

parent c0590681
No related branches found
No related tags found
No related merge requests found
...@@ -28,7 +28,7 @@ default: ...@@ -28,7 +28,7 @@ default:
checkout: checkout:
image: registry.gitlab.steamos.cloud/steamrt/soldier/sdk image: registry.gitlab.steamos.cloud/steamrt/sniper/sdk
stage: checkout stage: checkout
before_script: before_script:
script: script:
......
# Proton (soldier) SDK # Proton (sniper) SDK
This project builds Docker images based on This project builds Docker images based on
<https://gitlab.steamos.cloud/steamrt/soldier/sdk>, with the addition <https://gitlab.steamos.cloud/steamrt/sniper/sdk>, with the addition
of Proton build-dependencies. of Proton build-dependencies.
This is mostly just a CI script, which clones This is mostly just a CI script, which clones
...@@ -12,26 +12,26 @@ CI runs on Google Compute instances. ...@@ -12,26 +12,26 @@ CI runs on Google Compute instances.
## Using this image ## Using this image
Choose a suitable version number, for example 0.20210126.1-0, according Choose a suitable version number, for example 0.20230102.3-0, according
to the `PROTONSDK_VERSION` in Proton's `docker/Makefile`. Then: to the `PROTONSDK_VERSION` in Proton's `docker/Makefile`. Then:
docker pull registry.gitlab.steamos.cloud/proton/soldier/sdk:0.20210126.1-0 docker pull registry.gitlab.steamos.cloud/proton/sniper/sdk:0.20230102.3-0
and use that image for your builds. and use that image for your builds.
At the moment the `registry.gitlab.steamos.cloud/proton/soldier/sdk:latest` At the moment the `registry.gitlab.steamos.cloud/proton/sniper/sdk:latest`
tag will change frequently and will not always point to a usable SDK image, tag will change frequently and will not always point to a usable SDK image,
so please don't use that for anything. so please don't use that for anything.
Other Docker images whose names start with Other Docker images whose names start with
`registry.gitlab.steamos.cloud/proton/soldier/sdk/` are built as a `registry.gitlab.steamos.cloud/proton/sniper/sdk/` are built as a
side-effect of building this image, but those should not be relied on. side-effect of building this image, but those should not be relied on.
## Corresponding source code ## Corresponding source code
Source code for all the packages that go into the Steam Runtime Source code for all the packages that go into the Steam Runtime
base image can be found in the appropriate subdirectory of base image can be found in the appropriate subdirectory of
<https://repo.steampowered.com/steamrt-images-soldier/snapshots/> (look <https://repo.steampowered.com/steamrt-images-sniper/snapshots/> (look
in the sources/ directory). in the sources/ directory).
Source code for the packages added for the Proton SDK can be found in Source code for the packages added for the Proton SDK can be found in
...@@ -43,7 +43,7 @@ Source code for the packages added for the Proton SDK can be found in ...@@ -43,7 +43,7 @@ Source code for the packages added for the Proton SDK can be found in
To trigger a new build and publish a new test image, update the To trigger a new build and publish a new test image, update the
`PROTON_COMMIT` variable in `.gitlab-ci.yml`, commit, push to `PROTON_COMMIT` variable in `.gitlab-ci.yml`, commit, push to
`proton/soldier/sdk` as a branch with a name other than `master`, `proton/sniper/sdk` as a branch with a name other than `master`,
and wait. Using a branch named `wip/yourtopic` or `wip/yourname/yourtopic` and wait. Using a branch named `wip/yourtopic` or `wip/yourname/yourtopic`
is suggested, replacing *yourtopic* and *yourname* as appropriate. is suggested, replacing *yourtopic* and *yourname* as appropriate.
...@@ -61,8 +61,8 @@ this project, and therefore is ignored. ...@@ -61,8 +61,8 @@ this project, and therefore is ignored.
When you are happy with your test-build, merge it to `master`, tag the When you are happy with your test-build, merge it to `master`, tag the
resulting commit and push the tag, for example: resulting commit and push the tag, for example:
git tag -m "Proton SDK image v0.20210126.1-0" -a v0.20210126.1-0 git tag -m "Proton SDK image v0.20230102.3-0" -a v0.20230102.3-0
git push origin v0.20210126.1-0 git push origin v0.20230102.3-0
A new CI pipeline will run for the git tag. This time, the Docker image A new CI pipeline will run for the git tag. This time, the Docker image
version tag that will be created is the git tag, with the "v" prefix version tag that will be created is the git tag, with the "v" prefix
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment