Implementation plan for implementing alternative coordination mode using redis

[rsandell]

Just a suggested plan.

Testing done

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests that demonstrate the feature works or the issue is fixed

[panicking]

@rsandell If we support webhook, is really need to have a redis DB?

[rsandell]

If you put some form of router in front of Jenkins then you will distribute the events evenly. But for example if a new patchset event is delivered to a different Jenkins controller than the one that is building the previous one you won't get the build current patchset only functionality because there is no way for the other controller to know that there is a new patchset and cancel the current builds.

[panicking]

If you put some form of router in front of Jenkins then you will distribute the events evenly. But for example if a new patchset event is delivered to a different Jenkins controller than the one that is building the previous one you won't get the build current patchset only functionality because there is no way for the other controller to know that there is a new patchset and cancel the current builds.

You are right I was not really think about all those features. I will follow up later about other points, now I start to understand the whole story