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.

Sign up for GitHub

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

Jump to bottom

(Re-)Run checkout script if workspace was modified #549

Merged
merged 2 commits into from
Jan 10, 2024
Merged

(Re-)Run checkout script if workspace was modified #549

merged 2 commits into from
Jan 10, 2024

Commits on Jan 9, 2024

  1. builder: checkout modifications trigger rebuild 

    If there is a checkoutScript or some checkoutAssert's and the checkout
workspace was changed since the last time, we must re-run the step.

This fixes a problem on Jenkins builds where the checkoutScript modifies
a git repository. This change will be squashed by the Jenkins git plugin
every time the job runs. Now if the script was marked deterministic, Bob
still has to run it again to re-apply any modifications.

Another example are code generators that should probably be run again if
the workspace has changed. In fact, if the script was enabled for
checkout-only updates (checkoutUpdateIf), then such modifications would
already trigger the re-run if the workspace was modified.
    @jkloetzke
    jkloetzke committed Jan 9, 2024
    Configuration menu
    Copy the full SHA
    bacfca0 View commit details
    Browse the repository at this point in the history

  2. builder: print checkout reason 

    Sometimes its hard to know why a checkout step was executed because
there are a couple of possible reasons. Let the user know why exactly
the checkout as triggered instead of guessing.
    @jkloetzke
    jkloetzke committed Jan 9, 2024
    Configuration menu
    Copy the full SHA
    f04e34f View commit details
    Browse the repository at this point in the history