Build Queue
No builds in the queue.
 master
1Idle
 osm-cicd-1
1Idle
2Idle
3Idle
4Idle
5Idle
6Idle
7Idle
8Idle
9Idle
10Idle
11Idle
12Idle
 osm-cicd-10
1Idle
2Idle
3Idle
4Idle
5Idle
6Idle
7Idle
8Idle
 osm-cicd-2
1#240
2#237
3Idle
4#311
5#686
6Idle
 osm-cicd-3
1Idle
2Idle
3Idle
4Idle
5Idle
6Idle
 osm-cicd-4
1#246
2#243
3Idle
4Idle
5#735
6#318
 osm-cicd-5
1Idle
2Idle
3Idle
4Idle
5Idle
6Idle
7Idle
8Idle
9Idle
10Idle
11Idle
12Idle
 osm-cicd-6
1Idle
2Idle
3Idle
4Idle
5Idle
6Idle
7Idle
8Idle
9Idle
10Idle
11Idle
12Idle
 osm-cicd-7
1Idle
2Idle
3Idle
4Idle
 osm-cicd-8
1Idle
2Idle
3Idle
4Idle
5Idle
6Idle
7Idle
8Idle
9Idle
10Idle
11Idle
12Idle
13Idle
14Idle
15Idle
16Idle
 osm-cicd-9
1Idle
2Idle
3Idle
4Idle
5Idle
6Idle
7Idle
8Idle
9Idle
10Idle
11Idle
12Idle
13Idle
14Idle
15Idle
16Idle

What’s "project relationship"?

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:

  1. The upstream project records the fingerprints of its build artifacts.
  2. The downstream project records the fingerprints of the upstream files it uses.

This allows Jenkins to correlate two projects.