Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

how to trigger build in jenkins when changes committed to submodule?

We have a git repository with external submodules. We have to trigger a build when submodule was changed. Could you advice to us how to poll changes on submodules with your xtrigger plugin. Is it better to use shell script or monitor files or something else?


more information about our build brocess. step #1. clone root repository with submodules step #2. execute job for each submodule step #2.1 (in submodule). switch to proper branch (for example, master) step #2.1 (in submodule). pull the latest sources for submodule

now if somebody commits to root repository, jenkins launches build for the app but if somebody commits to any submodule repository, jenkins doesn't launch anything

we need solution for the second case. in best case it should be done via standard jenkins functionality or via open source plugin.

like image 681
OJ287 Avatar asked Dec 05 '12 10:12

OJ287


People also ask

How do I trigger a build automatically in Jenkins?

Follow the steps as mentioned below to trigger a Jenkins job automatically based on GitHub's webhook configurations: Step 1: Go to the Configuration page of the respective job and under the build trigger section, check the "GitHub hook trigger for GITScm polling" checkbox and click on the Save button.

Which feature can be used to trigger the build of a Jenkins project upon a commit pushed in a git repository?

GitHub Webhook configuration to invoke a Jenkins build job. With the GitHub webhook to Jenkins configured as a trigger, push commits to your GitHub repository at will. The GitHub server will then invoke our Jenkins instance and your continuous integration build jobs will run.


1 Answers

When a git repository has a submodule it points to a specific commit in that submodule (say commit A). So even if the submodule changes and now has commit B as a child of A your top level repository is still pointing at commit A. You must explicitly update your top level repository to point at commit B in the submodule, it will not happen automatically.

Given this, the answer to your question is, just update your top level repository to point to the new commit B. This will cause a change in your repository which should trigger a Jenkins build just like it normally would, this will pick up the new commit B from the submodule.

--

Given the extra information I would add a Jenkins job that watches the submodule repositories. When a submodule changes do whatever submodule specific test you have then as a post build step trigger the main repository job.

like image 70
asm Avatar answered Nov 15 '22 22:11

asm