add ability to force schedule pipeline for every change

[srinivasupadhya]

currently Go merges multiple modifications of a material for scheduling pipeline.

So if pipeline A watches git repo G and the last run was for g1. Now there are 3 new commits into G - g2, g3, g4. Go would schedule A be merging them into one instance, thus saving time.

But sometimes it would be useful to force Go to schedule 3 different instances of A (1 for each change)

This will be useful to support feature-branch / PR build plugins. reference

[alexouzounis]

hey guys! Are there any plans in integrating this to mainline and end up in a release ?

Alex

[msdisme]

+1

[uprial]

+1

[aselus-hub]

+1

[jamescorbett]

+1

[virtuald]

+1

[juhasipo]

+1 We have a pipeline for Gerrit review builds. Apparently since Go merges commits it doesn't always build all the submitted patch sets and therefore doesn't mark them as verified/failed.

[aselus-hub]

i'm just surprised this is not a high priority core feature... since it's integral to the most common workflow of 'check builds before merging to master/dev'...

[aleksihakli]

+1

We're using Go with Gerrit to build feature branches. This commit merging behaviour prevents us from reliably building every change, hence making it unfeasible to track Gerrit changes. This should be fixed with a high priority - a lot of companies use Gerrit and get a LOT of commits into build queue. We need build and test information on EVERY broken commit, not just for the latest one made.

[virtuald]

We use jenkins for building pull requests, because of so many problems with building pull requests with GoCD. It's a shame.

[hartjus]

+1

[darrenr]

+1

[fragsalat]

:+1:

[juhasipo]

It really is a shame that GoCD doesn't support this yet. We were able to achieve this with a custom plugin but I think that it isn't the ideal way to implement this. The plugin requires an access to the GoCD API which is uses to poll GoCD to check if the pipeline is clear for the next commit.

This feels more like a hack and it would make a lot more sense if GoCD itself would be able to handle this. Then all the material plugins wouldn't need to implement the same feature every time and the plugins wouldn't need the API credentials in their settings.

[vivekprahlad]

Hi GoCD team, is this issue on your radar? All of the GoCD PR plugins would be a lot more usable if this problem were addressed.

[arvindsv]

@vivekprahlad - A full re-look at PR plugins (and what they can do) is going to happen soon and I suspect this will be a part of it. I don't see how it cannot.

[sghill]

@arvindsv any updates on PR plugins and force scheduling pipelines per change?

[leonmaia]

Hey, after spending hours trying to figure out how to address this for my company needs (we use feature branches) I ended up creating a simple service that notifies GoCD when certain changes happen using their official APIs. This solves our issue, for now, ofc would be way better to have an official solution but for now, it works. If anyone wants to give a look or use please be my guest: https://github.com/leonmaia/gocd-pr-notifier There's still some need to write more unit tests and etc but this is the binary that is running today in our server :)

[wonderhoss]

@arvindsv Support for reliable PR builds is probably the single most important thing most users of CI/CD pipelines need. Is there anything at all that can be done to speed up the decision-making process around this?

It's difficult to convince people to adopt GoCD until there is at least a plan and timeline around this question.

[dbalakirev]

Users at our company also still ask about this. For us it would be vital to know, if this is something to be expected or not at all.

[Panajev]

This is my biggest reason, well this and not even having a basic plugin manager, to stick with Jenkins... yes, even without BlueOcean...

[andrewcampbell]

Hi GoCD team - is it possible to get an update on this feature request?

[kbalante]

This issue has resulted in hours wasted come code freeze time when lots of pr's are submitted at the same time resulting in some being ignored. This issue is made worse for larger teams.

Please fix thanks :)

[ZukkyBaig]

++1

[stale[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 90 days. If you can still reproduce this error on the master branch using local development environment or on the latest GoCD Release, please reply with all of the information you have about it in order to keep the issue open. Thank you for all your contributions.

[joelsdc]

Any updates on this?

[mlsm-trl]

Updates?

[CreatiCoding]

😭 Any updates..?

[chadlwilson]

There are no updates here. https://www.gocd.org/2023/02/13/gocd-project-status/ might be of interest.