I had a number of jobs linked to a cifs share, and it became necessary to switch to a new share. I added the new share, and deleted the old one from the main configuration UI.
When I would then go to view the jobs that were previously using the deleted share, it would show the new share in the configuration UI. However, if I look in the job configuration xml, I could see that they were still assigned to the old share until I clicked save on the job (without making changes). The jobs would fail to publish artifacts due to the fact that the cifs share they were tied to was no longer available. The error was "Could not retrieve the selected share, please check global configuration for CIFS shares."
I think that it should generate an error in the UI if the CIFS share is no longer available at the global level, instead of automatically switching to the next available.
I had a number of jobs linked to a cifs share, and it became necessary to switch to a new share. I added the new share, and deleted the old one from the main configuration UI.
When I would then go to view the jobs that were previously using the deleted share, it would show the new share in the configuration UI. However, if I look in the job configuration xml, I could see that they were still assigned to the old share until I clicked save on the job (without making changes). The jobs would fail to publish artifacts due to the fact that the cifs share they were tied to was no longer available. The error was "Could not retrieve the selected share, please check global configuration for CIFS shares."
I think that it should generate an error in the UI if the CIFS share is no longer available at the global level, instead of automatically switching to the next available.
Originally reported by b2jrock, imported from: CIFS UI in job configuration misleading after deleting cifs share.