CODEWITHSUNDEEP
gitcontinuous-integrationjenkinssonarqube
Robert Munteanu
Robert Munteanu

Reputation: 68268

Build project periodically only if changes are found in the repository

I have the following setup active and working:

Both jobs share the same git repository.

This allows me to build my project for each commit and then each day, only if the project has changed, run the Sonar analysis.

I've recently set up the git repository to send notifications to Jenkins when a project has changed, as per Push notifications from repository . This builds both projects immediately, but I want only the quick ( project ) job to build. If I move the project-sonar to be built periodically, the sonar analysis will be run even if there are no code changes, which is wasteful.

How can I retain

?

Upvotes: 7

Views: 9161

Answers (3)

Steven Schoch
Steven Schoch

Reputation: 71

I have my regular project and a second one called "project-daily" that runs daily.

"Project" takes a parameter named "RELEASE_TAG", which is passed as the branch specifier in the git section. The git plugin will also allow a tag to be specified here.

When "project" starts, it saves $COMMIT to a file named latest/$PROJECT.$BRANCH. ($BRANCH is set to $RELEASE_TAG, unless $RELEASE_TAG is a tag, in which case $BRANCH is set to "master".) This file is read by "project-daily".

"Project-daily" is a pipeline script. It does not have a repository. To save space, it runs "git clone --bare ...", and then "git log -n 1 --format=format:%H daily". It reads "latest/$PROJECT.daily" to get the latest build (attempt). If that commit is different than the "git log" output, then it calls "build job:'project'", with parameter "RELEASE_TAG" set to "daily".

We push our working code to the daily branch. When it's time for a release build, we merge to master, tag it, and then run "project" manually with the tag (which specifies the version).

Upvotes: 1

Robert Munteanu
Robert Munteanu

Reputation: 68268

I've solved this using the following approach:

  1. All jenkins projects are named after their git repository ( I use gitolite )
  2. I have activated only Trigger builds remotely for the base builds

  3. I have added a post-receive hook in gitolite which does something like

    $CURL --silent --netrc --insecure --connect-timeout 2 "$GIT_REMOTE_TRIGGER_URL/$GL_REPO/build?token=$JENKINS_BUILD_TOKEN" > /dev/null

  4. Scheduled all sonar jobs to poll the SCM every 24 hours

Upvotes: 1

Dennis S.
Dennis S.

Reputation: 2121

I implemented something very much like what you're looking at using the "Run Condition" plugin to jenkins. https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin

I made the sonar job a follow-on to the polling/build/test job, with conditions so it only runs once a day.

Upvotes: 3

Related Questions