First off, jenkins-view-builder is awesome. Thanks for that. :sparkling_heart:
I noticed that a subsequent update call fails to lay down the regex outlined in the jvb yaml. This is under jenkins-view-builder==0.5.0 and Jenkins 1.642.1.
Steps to reproduce:
lay down jvb yaml via jenkins-view-builder update --conf /path/to/jenkins_jobs.ini /path/to/jvb/yaml/
edit the regex for a jvb-managed view in Jenkins UI
repeat above update call
observe regex is not corrected
Tooling like jenkins-job-builder accounts for out of band edits by enforcing declared values in jjb yaml via update calls (eg jenkins-jobs --conf /path/to/jenkins_jobs.ini --ignore-cache update /path/to/jjb/yaml/ --delete-old). The above is a good way to remove one-off jobs and hard set all managed jobs to the exact values in jjb yaml.
Hello --
First off, jenkins-view-builder is awesome. Thanks for that. :sparkling_heart:
I noticed that a subsequent
update
call fails to lay down the regex outlined in the jvb yaml. This is underjenkins-view-builder==0.5.0
and Jenkins1.642.1
.Steps to reproduce:
jenkins-view-builder update --conf /path/to/jenkins_jobs.ini /path/to/jvb/yaml/
update
callTooling like jenkins-job-builder accounts for out of band edits by enforcing declared values in jjb yaml via
update
calls (egjenkins-jobs --conf /path/to/jenkins_jobs.ini --ignore-cache update /path/to/jjb/yaml/ --delete-old
). The above is a good way to remove one-off jobs and hard set all managed jobs to the exact values in jjb yaml.Im not sure if https://github.com/piyush0101/jenkins-view-builder/issues/10 blocks the update from firing, but its highly likely.
Thanks @piyush0101 and team!