Configure Hudson to only execute Build or Post Build actions if changes in SVN are detected

13,248

You can have Hudson poll the SCM for changes and only do things if it finds changes.

Poll SCM: Configure Hudson to poll changes in SCM.

Note that this is going to be an expensive operation for CVS, as every polling requires Hudson to scan the entire workspace and verify it with the server. Consider setting up a "push" trigger to avoid this overhead, as described in this document

You can also add something to your SCM post-commit hooks that will fire off a Hudson build.

Trigger builds remotely (e.g., from scripts): Enable this option if you would like to trigger new builds by accessing a special predefined URL (convenient for scripts).

One typical example for this feature would be to trigger new build from the source control system's hook script, when somebody has just committed a change into the repository, or from a script that parses your source control email notifications.

You'll need to provide an authorization token in the form of a string so that only those who know it would be able to remotely trigger this project's builds.

Share:
13,248
ken
Author by

ken

Updated on June 16, 2022

Comments

  • ken
    ken almost 2 years

    Is there a way to configure Hudson to only execute Build or Post Build actions if there are changes in SVN/CVS

    Thank you

  • ken
    ken over 14 years
    Using Poll SCM as you mentionned is quite expensive operation for SVN. I was more thinking about triggering the build manually and then only if there are changes to SVN that the Build process get executed. Sometimes there are minor changes to SVN that doesn't necessitate a new Build
  • Michael Donohue
    Michael Donohue over 14 years
    Polling a subversion repository is incredibly cheap - the server returns the latest changelist number, which can be compared against the last version Hudson built. What makes you think it is expensive?