On 28/06/2025 09:09, Andrew Bower wrote:
Hi all,
On Fri, Jun 27, 2025 at 09:12:02AM -0700, Soren Stoutner wrote:
On Friday, June 27, 2025 6:37:02 AM Mountain Standard Time Debian Bug Tracking
System wrote:
Please do not add default salsa config as a file but rather configure it >>> via Gitlab's web interface to reference the template.
Also it does not make much sense to have a CI config but no Vcs-Git.
Actually, adding a default Salsa CI config file is the recommended procedure.
https://salsa.debian.org/salsa-ci-team/pipeline#salsa-continuous-integration-ci--quality-assurance-for-debian-packaging
I adopted a package that had the CI configured in the Salsa UI but the problem with that was it would be triggered on the branches that didn't
have debian packaging files, such as upstream or 'pristine-tar'
branches. Those failures are unwelcome noise, but worse, if they happen
to get updated after the last push to a debian branch then the Debian dashboards show up the CI as having failed overall.
When I ran into this before, I found that there was a guard in the
recipe that looks for a "debian/" dir.
The only explanation for why the pipeline ran for upstream branch was
that I was pushing both branches in the same git call.
If I pushed the branches separately, salsa didn't run on upstream.
That's what I believe gbp does as well.
--
Regards,
Ahmad
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)