In our gitlab project, we use some "schedules" jobs running a "fake pipeline" to do some other tasks (like checking dependencies update, or vulnerabilities) .
And some time, this "fake pipeline" run nearly a real pipeline ... and : (the "fake pipeline" is only one job)
the sonar-scanner is run in the pipeline #8735 but publish on the #8736 ...
I'm searching about, I don't know, maybe a configuration to pass the pipeline id for this, but I found nothing ...
So, I don't know if it's a miss configuration, or a bug (or a feature request) .
In our gitlab project, we use some "schedules" jobs running a "fake pipeline" to do some other tasks (like checking dependencies update, or vulnerabilities) .
And some time, this "fake pipeline" run nearly a real pipeline ... and : (the "fake pipeline" is only one job)
the sonar-scanner is run in the pipeline #8735 but publish on the #8736 ...
I'm searching about, I don't know, maybe a configuration to pass the pipeline id for this, but I found nothing ...
So, I don't know if it's a miss configuration, or a bug (or a feature request) .