Otto Kekäläinen

Thanks for spotting that, I filed now MR to fix it: https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/577 I also tested that the build indeed proceeds past this point now. Next thing it fails on this:...

Thanks, indeed, with `gitlab-ci-local --file debian/salsa-ci.yml --variable RELEASE=unstable --variable CI_BUILDS_DIR=/gcl-builds` I get the builds to progress further now. In fact, when I removed the non-amd64 build jobs I got the...

Another example: ``` gbp clone --verbose https://salsa.debian.org/debian/trend.git cd trend nano debian/salsa-ci.yml include: - - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml + - https://salsa.debian.org/otto/salsa-ci-pipeline/-/raw/fix-hard-coded-builds-path/salsa-ci.yml + - https://salsa.debian.org/otto/salsa-ci-pipeline/-/raw/fix-hard-coded-builds-path/pipeline-jobs.yml gitlab-ci-local --file debian/salsa-ci.yml --variable RELEASE=unstable --variable CI_BUILDS_DIR=/gcl-builds ... PASS...

Next thing I am trying to debug is why it only runs the 'provisioning' and 'build' stages, but not the 'test' stage. Compare the above jobs completed to full pipeline...

As #1489 got merged last week, testing again: ``` $ dpkg -l gitlab-ci-local Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-===============-============-============-============================================= ii gitlab-ci-local 4.58.0 amd64...

## Moving ccache dir emits error When running rebuilds, I can see that the local [ccache](https://ccache.dev/) is used, and hit rate is 100%, but there is an error message `mv:...

In the examples above I have used packages [trend](https://salsa.debian.org/debian/trend) and [entr](https://salsa.debian.org/debian/entr) as examples. The [pipeline of trend](https://salsa.debian.org/debian/trend/-/blob/master/debian/salsa-ci.yml) is a vanilla [Salsa CI pipeline](https://salsa.debian.org/salsa-ci-team/pipeline) with no customizations: ```yaml --- include: -...

> https://salsa.debian.org/maciej.lew/lifelines/-/commits/build-pipeline I don't see a single pipeline run on any commits here. Please make sure Salsa CI itself works for the package in general before testing local builds or...

That would work > Message ID: ***@***.***> >

Looks good to me!