Skip to content
Build Queue
No builds in the queue.
Built-In Node
1Idle
macys
1Idle
2Idle
3Idle
4Idle
macys_VM
1Idle
2Idle
3Idle
4Idle
reynolds
1#119
2#119
3#119
4#119
5#119
6#119
7#119
8#119
9#119
10#119
11#119
12#119
13#119
14Idle
15Idle
16Idle
17Idle
18Idle
19Idle
20Idle
21Idle
22Idle
23Idle
24Idle
25Idle
26Idle
27Idle
28Idle
29Idle
30Idle
31Idle
32Idle
33Idle
34Idle
35Idle
36Idle
37Idle
38Idle
39Idle
40Idle
41Idle
42Idle
43Idle
44Idle
#119
reynolds-centOS7
1Idle
2Idle
3Idle
reynolds-centOS8
1Idle
2Idle
3Idle
reynolds-rhel7
1Idle
2Idle
reynolds-ubuntu16
1Idle
2Idle
3Idle
reynolds-ubuntu18
1Idle
2Idle
3Idle
reynolds-ubuntu20
1Idle
2Idle
3Idle
viggen
1Idle
2Idle
3Idle
4Idle
5Idle
6Idle
7Idle
8Idle
windows10x64
1Idle
2Idle
3Idle
4Idle
5Idle
6Idle
7Idle
8Idle

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.