3
3
#
4
4
# The images are pushed to the LLVM package registry at https://github.com/orgs/llvm/packages
5
5
# and tagged appropriately. The selection of which Docker image version is used by the libc++
6
- # CI nodes at any given point is controlled by the libc++ maintainers using a mechanism that
7
- # is not publicly visible for safety purposes.
6
+ # CI nodes at any given point is controlled from the workflow files themselves.
8
7
9
8
name : Build Docker images for libc++ CI
10
9
@@ -27,25 +26,29 @@ jobs:
27
26
steps :
28
27
- uses : actions/checkout@v4
29
28
29
+ - name : Build the Linux builder image and the Android builder image
30
+ working-directory : libcxx/utils/ci
31
+ run :
32
+ - docker compose build actions-builder
33
+ - docker compose build android-buildkite-builder
34
+
30
35
- name : Log in to GitHub Container Registry
31
36
uses : docker/login-action@v3
32
37
with :
33
38
registry : ghcr.io
34
39
username : ${{ github.actor }}
35
40
password : ${{ secrets.GITHUB_TOKEN }}
36
41
37
- - name : Build and push the Linux builder image
42
+ - name : Push the Linux builder image
38
43
working-directory : libcxx/utils/ci
39
44
run :
40
- - docker compose build actions-builder
41
45
- docker compose push actions-builder
42
46
env :
43
47
TAG : libcxx-linux-builder:${{ github.sha }}
44
48
45
- - name : Build and push the Android builder image
49
+ - name : Push the Android builder image
46
50
working-directory : libcxx/utils/ci
47
51
run :
48
- - docker compose build android-buildkite-builder
49
52
- docker compose push android-buildkite-builder
50
53
env :
51
54
TAG : libcxx-android-builder:${{ github.sha }}
0 commit comments