1a12f9caf854d471f40a3b0a82f8efa8c8f93f2c
rebased onto d2872b788d070c7654929bd7a25bb84263ef27c1
this is a same name as at line 6. it seems that it even does the same
Yes, it does the same, since first is BuildConfig applied, when it's not changed then it's fine and the block with trigger update is not executed. In case that BuildConfig is changed then it's updated with trigger only configuration, executed to apply changes in trigger and updated again to original version.
rebased onto 3c7969f7bcca3a6ec76ad7ac476ea3b554b10872
task names updated
Update build config On jenkins master
check if the build was updated
it needs delete Jenkins build which update only triggers
rebased onto 1179363377ce20da842556f623efe5b3db4f1d52
Updated
Doesn't make sense. a build update there is not neccesary to have build for {{ }}
build for {{ }}
a trigger update otherwise it is a verb
rebased onto d597312f8b8a534f037dde8623a731c88449fa60
from the previous step
one comment otherewise LGTM
rebased onto 1a12f9caf854d471f40a3b0a82f8efa8c8f93f2c
Pull-Request has been merged by mkovarik
Build 1a12f9caf854d471f40a3b0a82f8efa8c8f93f2c FAILED! Rebase or make new commits to rebuild.