Reputation: 1864
i have two questions.
why Jenkins automatically picks up the downstream projects? how to stop jenkins automatically picking up downstream projects?
where does jenkins stores (in the file system) the downstream & upstream project of any project? if I know this I can probably go and edit the necessary configuration according to my need?
note: the projects mentioned above are maven projects which build java code
Upvotes: 1
Views: 7567
Reputation: 1003
There is another possibility of triggering downstream projects through project relationships. These relationships are set whenever the project fingerprints are recorded (both on the upstream and on the downstream projects). From the project relationship page:
When you have projects that depend on each other, Jenkins can track which build of the upstream project is used by which build of the downstream project, by using the records created by the fingerprint support.
For this feature to work, the following conditions need to be met:
The upstream project records the fingerprints of its build artifacts The downstream project records the fingerprints of the upstream files it uses This allows Jenkins to correlate two projects.
On the maven project expand the Build settings by clicking on the Advanced button. You can disable the automatic trigger on the downstream projects by unchecking the option "Enable triggering of downstream projects".
Upvotes: 1
Reputation: 22089
As I know, there are 2 ways jenkins can set up downstream project.
Add Post Build Action --> Build other projects(manual step)
Add Post Build Action --> Trigger parameterized build on other projects
It is easy to configure when or whether to trigger downstream project.
Upvotes: 2