16 |
17 |
We created the seed job for you, but you have to run it. When you do
18 | run it, you have to provide some properties. By default we create a seed that
19 | has all the properties options, but you can delete most of it. If you
20 | set the properties as global environment variables, you have to remove them from the
21 | seed.
22 |
23 |
24 |
To run the demo, provide a comma-separated
25 | list of the URLs of the two aforementioned forks (github-webhook and github-analytics') in the `REPOS variable.
26 |
27 |
28 |
The following images shows the steps involved:
29 |
30 |
34 |
35 |
36 |

37 |
38 |
Step 1: Click the 'jenkins-pipeline-seed-cf' job for Cloud Foundry and jenkins-pipeline-seed-k8s for Kubernetes
39 |
40 |
44 |
45 |
46 |

47 |
48 |
Step 2: Click the 'Build with parameters'
49 |
50 |
54 |
55 |
56 |

57 |
58 |
Step 3: The REPOS parameter should already contain your forked repos (you’ll have more properties than the ones in the screenshot)
59 |
60 |
64 |
65 |
66 |

67 |
68 |
Step 4: This is how the results of seed should look like
69 |
70 |
71 |