Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(jenkins): Don't kick off multiples of the same build #863

Merged
merged 3 commits into from
Sep 22, 2020

Commits on Sep 16, 2020

  1. fix(jenkins): Don't kick off multiples of the same build

    The issue here is that when an operation takes a long time (e.g. talking to jenkins to kick off a build)
    this prolonged time can cause orca to try to resubmit the request multiple times thus kicking off multiple (or infinite number of) builds.
    
    We solve this, but setting a flag that a given request (keyed of X-SPINNAKER-REQUEST-ID and master/job/param) is being processed so if an identical
    request comes in the controller can detect that and respond with 202 ACCEPTED. This will cause orca to retry (corresponding PR coming).
    When the job is finally kicked off, the resulting build number will be stored in the cache and next time orca queries it will get the build number back
    marchello2000 committed Sep 16, 2020
    Configuration menu
    Copy the full SHA
    379c39c View commit details
    Browse the repository at this point in the history

Commits on Sep 21, 2020

  1. Configuration menu
    Copy the full SHA
    7d1fb6d View commit details
    Browse the repository at this point in the history

Commits on Sep 22, 2020

  1. Configuration menu
    Copy the full SHA
    b653cd4 View commit details
    Browse the repository at this point in the history