Skip to content
Built-In Node
1Idle
macys
1#751
2#751
3#751
4#751
macys_VM
1Idle
2Idle
3Idle
4Idle
reynolds
1Idle
2#9752
3#751
4Idle
5
6Idle
7Idle
8Idle
9Idle
10Idle
11Idle
12Idle
13#751
14Idle
15#751
16#751
17Idle
18#751
19Idle
20Idle
21Idle
22#751
23#9752
24#9752
25
26#9752
27
28
29
30#9752
31Idle
32Idle
33Idle
34Idle
35Idle
36Idle
37Idle
38Idle
39Idle
40Idle
41Idle
42Idle
43Idle
44Idle
#751
#9752
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
1#751
2#751
3#751
4#751
5#751
6#751
7#751
8#751
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.