@@ -96,26 +96,26 @@ Feature: Pipeline Templates
96
96
| test -distrusted -pipeline -template | distrusted | publish -distrusted |
97
97
98
98
Scenario : Use pipeline template
99
- Given a "third" pipeline using a "test-pipeline-template" @ "1.0.0 " pipeline template
99
+ Given a "third" pipeline using a "test-pipeline-template" @ "latest " pipeline template
100
100
When user starts the job that uses pipeline template
101
101
And the pipeline executes what is specified in the pipeline template
102
102
103
103
Scenario : Pipeline shared config takes precedence over template config
104
- Given a "fourth" pipeline using a "test-pipeline-template" @ "1.0.0 " pipeline template
104
+ Given a "fourth" pipeline using a "test-pipeline-template" @ "latest " pipeline template
105
105
And user defined shared settings
106
106
And the pipeline template has overwritten shared settings
107
107
When user starts the job that uses pipeline template
108
108
Then job settings are the template command
109
109
110
110
Scenario : Pipeline exists job config takes precedence over template config
111
- Given a "fifth" pipeline using a "test-pipeline-template" @ "1.0.0 " pipeline template
111
+ Given a "fifth" pipeline using a "test-pipeline-template" @ "latest " pipeline template
112
112
And user defined exists jobs settings
113
113
And the pipeline template has overwritten jobs settings
114
114
When user starts the job that uses pipeline template
115
115
Then job settings are the user command
116
116
117
117
Scenario : Pipeline user defined job config takes precedence over template config
118
- Given a "sixth" pipeline using a "test-pipeline-template" @ "1.0.0 " pipeline template
118
+ Given a "sixth" pipeline using a "test-pipeline-template" @ "latest " pipeline template
119
119
And user defined additional jobs settings
120
120
And the pipeline template has additional jobs settings
121
121
When user starts the additional job that uses pipeline template
0 commit comments