.github/workflows/build.yml #88
build.yml
on: workflow_dispatch
Matrix: build-and-push-base / build
Matrix: build-and-push
Annotations
6 errors and 74 warnings
build-and-push (images/c/ToolDockerfile, ., ghcr.io/ls1intum/theia/c, 2024-11-11) / Build Docker Image for ghcr.io/ls1intum/theia/c
buildx failed with: ERROR: failed to solve: process "/bin/sh -c apt update && apt upgrade -y --autoremove && apt install -y --no-install-recommends gcc clang git gdb make findutils bzip2 e2fsprogs sudo adduser && apt clean && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100
|
build-and-push (images/rust/ToolDockerfile, ., ghcr.io/ls1intum/theia/rust, 2024-11-11) / Build Docker Image for ghcr.io/ls1intum/theia/rust
buildx failed with: ERROR: failed to solve: process "/bin/sh -c apt update && apt upgrade -y --autoremove && apt install -y --no-install-recommends curl adduser build-essential && apt clean && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100
|
build-and-push (images/rust/ToolDockerfile, ., ghcr.io/ls1intum/theia/rust, 2024-11-11) / Build Docker Image for ghcr.io/ls1intum/theia/rust
buildx failed with: ERROR: failed to solve: process "/bin/sh -c apt update && apt upgrade -y --autoremove && apt install -y --no-install-recommends curl adduser build-essential && apt clean && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100
|
build-and-push (images/c/ToolDockerfile, ., ghcr.io/ls1intum/theia/c, 2024-11-11) / Build Docker Image for ghcr.io/ls1intum/theia/c
buildx failed with: ERROR: failed to solve: process "/bin/sh -c apt update && apt upgrade -y --autoremove && apt install -y --no-install-recommends gcc clang git gdb make findutils bzip2 e2fsprogs sudo adduser && apt clean && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100
|
build-and-push (images/swift/ToolDockerfile, ., ghcr.io/ls1intum/theia/swift, "BUILDER_IMAGE=swif... / Build Docker Image for ghcr.io/ls1intum/theia/swift
buildx failed with: ERROR: failed to solve: process "/bin/sh -c swift build ${SWIFT_FLAGS} --product swiftlint" did not complete successfully: exit code: 1
|
build-and-push (images/swift/ToolDockerfile, ., ghcr.io/ls1intum/theia/swift, "BUILDER_IMAGE=swif... / Build Docker Image for ghcr.io/ls1intum/theia/swift
buildx failed with: ERROR: failed to solve: process "/bin/sh -c swift build ${SWIFT_FLAGS} --product swiftlint" did not complete successfully: exit code: 1
|
The 'as' keyword should match the case of the 'from' keyword:
images/base-ide/BaseDockerfile#L3
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Legacy key/value format with whitespace separator should not be used:
images/base-ide/BaseDockerfile#L11
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/base-ide/BaseDockerfile#L11
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
The 'as' keyword should match the case of the 'from' keyword:
images/base-ide/BaseDockerfile#L3
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
build-and-push-base / merge
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
The 'as' keyword should match the case of the 'from' keyword:
images/python/ToolDockerfile#L2
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/python/ToolDockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/python/ToolDockerfile#L26
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Legacy key/value format with whitespace separator should not be used:
images/python/ToolDockerfile#L10
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/python/ToolDockerfile#L75
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/python/ToolDockerfile#L77
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
The 'as' keyword should match the case of the 'from' keyword:
images/javascript/ToolDockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/javascript/ToolDockerfile#L25
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Legacy key/value format with whitespace separator should not be used:
images/javascript/ToolDockerfile#L10
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/javascript/ToolDockerfile#L60
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/javascript/ToolDockerfile#L64
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
The 'as' keyword should match the case of the 'from' keyword:
images/javascript/ToolDockerfile#L2
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/javascript/ToolDockerfile#L25
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Legacy key/value format with whitespace separator should not be used:
images/javascript/ToolDockerfile#L10
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/javascript/ToolDockerfile#L60
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/javascript/ToolDockerfile#L64
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
The 'as' keyword should match the case of the 'from' keyword:
images/javascript/ToolDockerfile#L2
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/javascript/ToolDockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
build-and-push (images/javascript/ToolDockerfile, ., ghcr.io/ls1intum/theia/javascript, 2024-11-11) / merge
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Legacy key/value format with whitespace separator should not be used:
images/java-17/ToolDockerfile#L66
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/java-17/ToolDockerfile#L68
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
The 'as' keyword should match the case of the 'from' keyword:
images/java-17/ToolDockerfile#L2
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/java-17/ToolDockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/java-17/ToolDockerfile#L25
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Legacy key/value format with whitespace separator should not be used:
images/java-17/ToolDockerfile#L10
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
The 'as' keyword should match the case of the 'from' keyword:
images/python/ToolDockerfile#L2
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/python/ToolDockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/python/ToolDockerfile#L26
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Legacy key/value format with whitespace separator should not be used:
images/python/ToolDockerfile#L10
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/python/ToolDockerfile#L75
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/python/ToolDockerfile#L77
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
The 'as' keyword should match the case of the 'from' keyword:
images/java-17/ToolDockerfile#L2
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/java-17/ToolDockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/java-17/ToolDockerfile#L25
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Legacy key/value format with whitespace separator should not be used:
images/java-17/ToolDockerfile#L10
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/java-17/ToolDockerfile#L66
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/java-17/ToolDockerfile#L68
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
build-and-push (images/java-17/ToolDockerfile, ., ghcr.io/ls1intum/theia/java-17, 2024-11-11) / merge
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build-and-push (images/python/ToolDockerfile, ., ghcr.io/ls1intum/theia/python, 2024-11-11) / merge
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Legacy key/value format with whitespace separator should not be used:
images/haskell/ToolDockerfile#L62
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/haskell/ToolDockerfile#L74
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/haskell/ToolDockerfile#L99
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
The 'as' keyword should match the case of the 'from' keyword:
images/haskell/ToolDockerfile#L2
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/haskell/ToolDockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/haskell/ToolDockerfile#L26
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Legacy key/value format with whitespace separator should not be used:
images/haskell/ToolDockerfile#L10
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/haskell/ToolDockerfile#L99
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
The 'as' keyword should match the case of the 'from' keyword:
images/haskell/ToolDockerfile#L2
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/haskell/ToolDockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/haskell/ToolDockerfile#L26
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Legacy key/value format with whitespace separator should not be used:
images/haskell/ToolDockerfile#L10
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/haskell/ToolDockerfile#L62
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/haskell/ToolDockerfile#L74
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
The 'as' keyword should match the case of the 'from' keyword:
images/ocaml/ToolDockerfile#L10
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/ocaml/ToolDockerfile#L13
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/ocaml/ToolDockerfile#L33
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Legacy key/value format with whitespace separator should not be used:
images/ocaml/ToolDockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/ocaml/ToolDockerfile#L53
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/ocaml/ToolDockerfile#L67
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/ocaml/ToolDockerfile#L86
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
The 'as' keyword should match the case of the 'from' keyword:
images/ocaml/ToolDockerfile#L10
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/ocaml/ToolDockerfile#L13
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
The 'as' keyword should match the case of the 'from' keyword:
images/ocaml/ToolDockerfile#L33
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Legacy key/value format with whitespace separator should not be used:
images/ocaml/ToolDockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/ocaml/ToolDockerfile#L53
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/ocaml/ToolDockerfile#L67
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
images/ocaml/ToolDockerfile#L86
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
build-and-push (images/haskell/ToolDockerfile, ., ghcr.io/ls1intum/theia/haskell, 2024-11-11) / merge
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build-and-push (images/ocaml/ToolDockerfile, ., ghcr.io/ls1intum/theia/ocaml, 2024-11-11) / merge
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
digests-ghcr.io-ls1intum-theia-base-linux-amd64
Expired
|
244 Bytes |
|
digests-ghcr.io-ls1intum-theia-base-linux-arm64
Expired
|
244 Bytes |
|
digests-ghcr.io-ls1intum-theia-haskell-linux-amd64
Expired
|
244 Bytes |
|
digests-ghcr.io-ls1intum-theia-haskell-linux-arm64
Expired
|
244 Bytes |
|
digests-ghcr.io-ls1intum-theia-java-17-linux-amd64
Expired
|
244 Bytes |
|
digests-ghcr.io-ls1intum-theia-java-17-linux-arm64
Expired
|
244 Bytes |
|
digests-ghcr.io-ls1intum-theia-javascript-linux-amd64
Expired
|
244 Bytes |
|
digests-ghcr.io-ls1intum-theia-javascript-linux-arm64
Expired
|
244 Bytes |
|
digests-ghcr.io-ls1intum-theia-ocaml-linux-amd64
Expired
|
244 Bytes |
|
digests-ghcr.io-ls1intum-theia-ocaml-linux-arm64
Expired
|
244 Bytes |
|
digests-ghcr.io-ls1intum-theia-python-linux-amd64
Expired
|
244 Bytes |
|
digests-ghcr.io-ls1intum-theia-python-linux-arm64
Expired
|
244 Bytes |
|
ls1intum~artemis-theia-blueprints~2A0GRY.dockerbuild
|
45.4 KB |
|
ls1intum~artemis-theia-blueprints~6FQCTW.dockerbuild
|
104 KB |
|
ls1intum~artemis-theia-blueprints~7HPPUN.dockerbuild
|
69.1 KB |
|
ls1intum~artemis-theia-blueprints~8VXF5I.dockerbuild
|
68.5 KB |
|
ls1intum~artemis-theia-blueprints~KDEMPC.dockerbuild
|
101 KB |
|
ls1intum~artemis-theia-blueprints~LM51TN.dockerbuild
|
45.9 KB |
|
ls1intum~artemis-theia-blueprints~M6Q2QM.dockerbuild
|
64.6 KB |
|
ls1intum~artemis-theia-blueprints~N1LMWW.dockerbuild
|
45.9 KB |
|
ls1intum~artemis-theia-blueprints~NYQGVB.dockerbuild
|
97.8 KB |
|
ls1intum~artemis-theia-blueprints~OLZOVH.dockerbuild
|
46.1 KB |
|
ls1intum~artemis-theia-blueprints~PFIG5Y.dockerbuild
|
64.9 KB |
|
ls1intum~artemis-theia-blueprints~PVQL57.dockerbuild
|
159 KB |
|
ls1intum~artemis-theia-blueprints~R20P93.dockerbuild
|
107 KB |
|
ls1intum~artemis-theia-blueprints~RT2JV3.dockerbuild
|
102 KB |
|
ls1intum~artemis-theia-blueprints~SM0ZZX.dockerbuild
|
97.1 KB |
|
ls1intum~artemis-theia-blueprints~TEZ8BI.dockerbuild
|
124 KB |
|
ls1intum~artemis-theia-blueprints~U32GZG.dockerbuild
|
161 KB |
|
ls1intum~artemis-theia-blueprints~Z1NN15.dockerbuild
|
120 KB |
|