fresh-continent-76371
10/17/2023, 12:20 PM$ pants ....
Bootstrapping Pants 2.16.0rc3
Installing pantsbuild.pants==2.16.0rc3 into a virtual environment at /root/.cache/nce/68f5608a60df9b97aab453d453817a4ded400d1d8ec7ede7ec14bcac83421a7b/bindings/venvs/2.16.0rc3
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.1/2.1 MB 27.0 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 819.3/819.3 KB 25.0 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 64.8/64.8 KB 10.1 MB/s eta 0:00:00
New virtual environment successfully created at /root/.cache/nce/68f5608a60df9b97aab453d453817a4ded400d1d8ec7ede7ec14bcac83421a7b/bindings/venvs/2.16.0rc3.
(I of course could just run pants, but at docker build time, the "version" pants is using, is not "with" the docker build.
I am looking for something like
pants -preseed 2.16.0rc3,2.17
to run in the docker build phase.gorgeous-winter-99296
10/17/2023, 12:29 PMENV PANTS_VERSION 2.17.0
RUN touch pants.toml && pants --help && rm pants.toml
gorgeous-winter-99296
10/17/2023, 1:10 PMENV
here; since that'll stick in the container... I'd have to experiment, but something like RUN PANTS_VERSION=2.17.0touch pants.toml && pants --help && rm pants.toml
would be safe.)enough-analyst-54434
10/17/2023, 1:31 PMhelp
to deal with this and other things (like update of scie-pants).curved-manchester-66006
10/17/2023, 2:10 PM# Pants
RUN /var/tmp/get-pants.sh --bin-dir /usr/local/bin/ --version 0.10.3
And then use GitLab caching for the versions of Pants it self (the nce
cache)fresh-continent-76371
10/17/2023, 7:13 PMcurved-manchester-66006
10/17/2023, 7:19 PMcache:
- &cache_pants_nce
key: "pants.toml"
paths:
- "${CI_PROJECT_DIR}/.cache/nce"
- &cache_pants_named_caches
key:
files:
- "**/pants*.toml"
- "3rdparty/**/*.lock"
paths:
- "${CI_PROJECT_DIR}/.cache/pants/named_caches"