[Help wanted] Trigger manually

[Pasupathi-Rajamanickam]

I searched all issues and documents, I don't find answer. I see few PR test has not been started. How do I manually trigger for new PR number. For existing on which was already ran, I can retry the build. For new PR if the pipeline not started how could I start one?

[jtarchie]

@PasupathiRajamanickam can you show us what you've tried, the actual YAML of the pipeline?

[jacob-hd]

I experience this as well. No matter how long I wait, it just won't start building some PRs:

It's been like this for days.

[jtarchie]

And are you you using version: every?

[jacob-hd]

We were not!

I just applied version: every to the get:

   - get: app-catalog-gateway
     resource: pull-request
     trigger: true
+    version: every

...and re-triggered a check, but it did not help. I'm going to uninstall and re-install the pipeline, and hope that solves it...

[jtarchie]

yeah you have to do that. Concourse does not trigger every after it has already detected versions.

[jacob-hd]

Got it, thanks @jtarchie !

[jacob-hd]

@jtarchie -

Even after deleting and re-set'ing the entire pipeline:

It still will not run some of the PRs:

:cry:

[jacob-hd]

Evidently, after 15 minutes, they all kicked off at once:

This is incredibly confusing to me. It checked the resource at least 15 times before it finally kicked them off..

But, at least it's doing it now.

[Pasupathi-Rajamanickam]

For me some times when I retry Build 10 -> pointing PR 405 on 4th may The retried build pointing to PR 415 Confusing

[jacob-hd]

This issue is recurring insidiously for us, even after applying version: every. It may be unrelated to this resource, and an issue with Concourse itself.

I've documented the issue further here: https://github.com/quotecenter/concourse-issue

The issue includes our full pipeline for scrutiny.