First off, jenkins-view-builder is awesome. Thanks for that. :sparkling_heart:
I noticed that repeated update calls fire HTML to stdout about a view already existing with the name. This is under jenkins-view-builder==0.5.0 and Jenkins 1.642.1.
First run:
Updating view data in Jenkins
Starting new HTTP connection (1): 127.0.0.1
Creating view panama
Starting new HTTP connection (1): 127.0.0.1
Starting new HTTP connection (1): 127.0.0.1
Creating view package
Starting new HTTP connection (1): 127.0.0.1
Starting new HTTP connection (1): 127.0.0.1
Creating view locust
Starting new HTTP connection (1): 127.0.0.1
Starting new HTTP connection (1): 127.0.0.1
Creating view identity
Starting new HTTP connection (1): 127.0.0.1
Starting new HTTP connection (1): 127.0.0.1
Creating view func-tests
Starting new HTTP connection (1): 127.0.0.1
Starting new HTTP connection (1): 127.0.0.1
Creating view environment
Starting new HTTP connection (1): 127.0.0.1
Starting new HTTP connection (1): 127.0.0.1
Creating view chef
Starting new HTTP connection (1): 127.0.0.1
Starting new HTTP connection (1): 127.0.0.1
Creating view check-env
Starting new HTTP connection (1): 127.0.0.1
I think it was taken care of in the update command of jenkins-view-builder. It looks like we may have broken something. I'll have a look. Thanks for reporting this issue.
Hello --
First off, jenkins-view-builder is awesome. Thanks for that. :sparkling_heart:
I noticed that repeated
update
calls fire HTML to stdout about a view already existing with the name. This is underjenkins-view-builder==0.5.0
and Jenkins1.642.1
.First run:
Second run:
It would be awesome if subsequent
update
calls accounted for theA view already exists with the name ${name}
.