Triggering a jenkins build upon change in a file

Question

0.00/5 (No votes)

See more:

Hello All,

For a particular scenario my requirement is, lets suppose we have 2 folders:
Folder 1
Folder 2
If there is a change in a file of "Folder 1", then the Jenkins build should trigger, otherwise it should not. I am using Git repository to maintain my code.

I would request any help if someone has been through this scenario.

Thanks and Regards,
Rahul

What I have tried:

Gone through many solutions online for ex:
https://stackoverflow.com/questions/28332780/how-to-trigger-a-jenkins-build-in-gerrit-trigger-on-change-to-project-subdirecto[^]

In Jenkin's under "dynamic source triggering" option, specified "file path", "forbidden file path" option. However, i see that my Jenkins Job is getting triggered for changes within both Folder-1 and Folder-2.

The configuration which i have set is:
GERRIT TRIGGER:
Trigger On:
- Draft Published
- Patchset Created

DYNAMIC TRIGGER CONFIGURATION:
Gerrit Project: name of repo: repo_name
Branches: path of the branch : for ex: /path
Add File path: Folder-1/**

Reading the documentation part, i saw that in Forbidden file paths, if there is a change in only the forbidden file, the Job wont trigger. But, somehow it doesnot seem to work.

Also, please note, that i use a sparse checkout, to checkout specific folders from the repository. I dont know, if that can affect...

Posted 9-Mar-23 20:57pm

Rahul VB

Updated 19-Mar-23 2:32am

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Rahul VB · Answer 1 · 2023-03-19T02:32:00

Hello All,

I got it to work, by doing the below:
1. Remove forbidden file path - There is no need of that
2. Just keep the file path - Specify the path of the folder within which you want your to trigger if there is some change for ex:
mypath/**

Now, when you update a file within the required folder i.e Folder1 in my case, then a gerrit review is created and the first patchset is upload and subsequently my Job is triggered.

Then, when i update a file within Folder2, then the 2nd patchset is uploaded and even then my Job is triggered. This is because the required file is still in my Gerrit review.

For, my job to stop triggering, i removed my file from the review and it started behaiving properly.

If any one has any other opinion, please post.

Thanks