-
Bug
-
Resolution: Incomplete
-
Minor
-
None
-
Jenkins v1.614
Publish over CIFS 0.3
os.name Linux
os.version 3.16.0-4-amd64
java.runtime.version 1.8.0_45-b14
Hi,
i had a cifs share working with jenkins using the Publish Over CIFS plugin. I needed a second cifs share with a similar name and changed the name of the current cifs share in the global configuration.
old name of cifs share: "server1"
new name : "server1 trunk share"
After changing the name i added the second cifs share with name "server1 tags share"
Now all jobs who used the old "server1" share are showing the correct new "server1 trunk share" in their config. But these jobs are marked "UNSTABLE" after running because they could not find the old cifs share with name "server1".
Problem:
The jobs showing the correct cifs share name in their config page but are using the old name internally.
Workaround:
go to jobs config page and select another cifs share, press save. Now change the cfis share back to what it should be. Then save the config again. Now it's using the correct cifs share.