-
Bug
-
Resolution: Fixed
-
Major
-
None
Update to Jenkins 2.102 caused problem with cifs-plugin.
The error is:
ERROR: Failed to find configuration named [] check the global configuration
When I open settings of a job the configuration looks empty and I cannot select share - the select is empty, field label also missing:
- duplicates
-
-
- Resolved
-
- is related to
-
-
- Resolved
-
[JENKINS-49023] Cannot upload file using cifs-plugin
Jiri Meluzin
added a comment - Yes, it is regression bug. It worked before upgrade to 2.102.
Anyway, where is storage of share configuration from the global config? I mean where is file that stores global config?
Jiri Meluzin
added a comment - Yes, it is regression bug. It worked before upgrade to 2.102.
Anyway, where is storage of share configuration from the global config? I mean where is file that stores global config?
Jiri Meluzin
added a comment - I have found workaround, the Job's config contained empty name (which is caused by the bug in the configuration - no shares are available to select), so I updated the config with correct name on filesystem and reload config of jobs. Then it works.
Jiri Meluzin
added a comment - I have found workaround, the Job's config contained empty name (which is caused by the bug in the configuration - no shares are available to select), so I updated the config with correct name on filesystem and reload config of jobs. Then it works. 
Andre S.
added a comment - jiri_meluzin Could you screen shot the workaround you did? I am running into the same issue. Where did you update the config with the filesystem etc? Thank you in advance.
Andre S.
added a comment - jiri_meluzin Could you screen shot the workaround you did? I am running into the same issue. Where did you update the config with the filesystem etc? Thank you in advance. Andre S.
added a comment - Thanks for responding,
slide_o_mix I am using Jenkins ver. 2.89.3, which is recently updated, and no see issue in the javascript console. I am running into the same issue jiri_meluzin is getting. I tried to manually editing the job's config.xml file element <configName> by manual placing the CIFS name in, but the field is still blank when I try running the job. I dont know if i have to restart my service. The error I am getting is:
ERROR: Failed to find configuration named [] check the global configuration
Andre S.
added a comment - Thanks for responding,
slide_o_mix I am using Jenkins ver. 2.89.3, which is recently updated, and no see issue in the javascript console. I am running into the same issue jiri_meluzin is getting. I tried to manually editing the job's config.xml file element <configName> by manual placing the CIFS name in, but the field is still blank when I try running the job. I dont know if i have to restart my service. The error I am getting is:
ERROR: Failed to find configuration named [] check the global configuration Can you post your global config xml and specific job config.xml? Please scrub it of anything that someone on the internet should not see.
Jiri Meluzin
added a comment - Andre S. - config.xml must be edited manually and then the configuration of the job must not be edited via Jenkins GUI. After you updated the config.xml you must reload all jobs configs from filesystem via Jenkins GUI
https://i.stack.imgur.com/TqKv7.png
Afterwards the job should be able to upload file.
Jiri Meluzin
added a comment - Andre S. - config.xml must be edited manually and then the configuration of the job must not be edited via Jenkins GUI. After you updated the config.xml you must reload all jobs configs from filesystem via Jenkins GUI
https://i.stack.imgur.com/TqKv7.png
Afterwards the job should be able to upload file. Andre S.
added a comment - jiri_meluzin Thank you, I will try your workaround, hopefully within a few days 
slide_o_mix Whenever I get a chance I will upload the necessary documents/screenshot to help. But I think the initial screenshots that Jiri Meluzin uploaded has the same exact settings as I have. Only difference is that the job name and config name are different, but still the CIFS issue where I cannot get the configuration job name to load is happening.
Andre S.
added a comment - jiri_meluzin Thank you, I will try your workaround, hopefully within a few days
slide_o_mix Whenever I get a chance I will upload the necessary documents/screenshot to help. But I think the initial screenshots that Jiri Meluzin uploaded has the same exact settings as I have. Only difference is that the job name and config name are different, but still the CIFS issue where I cannot get the configuration job name to load is happening. setsunafseisei The screenshots aren't very helpful sadly, I am looking for the config.xml FILES which will show me much more information.
Jiri Meluzin
added a comment - Here is the problematic part from config.xml from given job:
<jenkins.plugins.publish__over__cifs.CifsPublisher> <configName></configName> <verbose>false</verbose> <transfers> <jenkins.plugins.publish__over__cifs.CifsTransfer> <remoteDirectory>eai\repo\ear\change</remoteDirectory> <sourceFiles>${BRANCH}/*.ear,${BRANCH}/*.xml,${BRANCH}/*.csv</sourceFiles> <excludes></excludes> <removePrefix></removePrefix> <remoteDirectorySDF>false</remoteDirectorySDF> <flatten>false</flatten> <cleanRemote>false</cleanRemote> <noDefaultExcludes>false</noDefaultExcludes> <makeEmptyDirs>false</makeEmptyDirs> <patternSeparator>[, ]+</patternSeparator> </jenkins.plugins.publish__over__cifs.CifsTransfer> </transfers> <useWorkspaceInPromotion>false</useWorkspaceInPromotion> <usePromotionTimestamp>false</usePromotionTimestamp> </jenkins.plugins.publish__over__cifs.CifsPublisher>
And the problem is caused by the empty tag <configName>. Workaround is to update content of this element with correct value from jenkins.plugins.publish_over_cifs.CifsPublisherPlugin.xml - from element /jenkins.plugins.publish_overcifs.CifsPublisherPlugin-Descriptor/hostConfigurations/jenkins.plugins.publish_over_cifs.CifsHostConfiguration/name .
Jiri Meluzin
added a comment - Here is the problematic part from config.xml from given job:
<jenkins.plugins.publish__over__cifs.CifsPublisher>
<configName> </configName>
<verbose> false </verbose>
<transfers>
<jenkins.plugins.publish__over__cifs.CifsTransfer>
<remoteDirectory> eai\repo\ear\change </remoteDirectory>
<sourceFiles> ${BRANCH}/*.ear,${BRANCH}/*.xml,${BRANCH}/*.csv </sourceFiles>
<excludes> </excludes>
<removePrefix> </removePrefix>
<remoteDirectorySDF> false </remoteDirectorySDF>
<flatten> false </flatten>
<cleanRemote> false </cleanRemote>
<noDefaultExcludes> false </noDefaultExcludes>
<makeEmptyDirs> false </makeEmptyDirs>
<patternSeparator> [, ]+ </patternSeparator>
</jenkins.plugins.publish__over__cifs.CifsTransfer>
</transfers>
<useWorkspaceInPromotion> false </useWorkspaceInPromotion>
<usePromotionTimestamp> false </usePromotionTimestamp>
</jenkins.plugins.publish__over__cifs.CifsPublisher>
And the problem is caused by the empty tag <configName>. Workaround is to update content of this element with correct value from jenkins.plugins.publish_over_cifs.CifsPublisherPlugin.xml - from element /jenkins.plugins.publish_ over cifs.CifsPublisherPlugin -Descriptor/hostConfigurations/jenkins.plugins.publish_ over _cifs.CifsHostConfiguration/ name . 
Corneil du Plessis
added a comment - I found that when configuring a Post Build Action the list of shares does display properly.
Hopefully, this info may help someone in tracking down the problem.
Corneil du Plessis
added a comment - I found that when configuring a Post Build Action the list of shares does display properly.
Hopefully, this info may help someone in tracking down the problem. Not sure which issue to post in because I see there are several on this subject.
I am having the same issue as those above. I did notice I am getting an error in the JS console
Here are my global, project and plugin configs. Cleansed of course. If you need any more info please let me know
I believe I have a fix for this, I need to test out some stuff and make sure.
Matthew Klepeis
added a comment - slide_o_mix Any update on this? We are having a similar issue. Send files to a windows share works as a Post Build step but not as a "Build" step.
Matthew Klepeis
added a comment - slide_o_mix Any update on this? We are having a similar issue. Send files to a windows share works as a Post Build step but not as a "Build" step. klepeis Can you try the HPI file from https://ci.jenkins.io/job/Plugins/job/publish-over-cifs-plugin/job/master/?
Matthew Klepeis
added a comment - slide_o_mix Thanks! That did the trick.
For your information, all publish-over-cifs component type JENKINS issues related to the Publish Over CIFS plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-cifs-plugin/issues
Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-cifs-plugin/issues/77
And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-cifs-plugin/issues?q=%22JENKINS-49023%22
(Note: this is an automated bulk comment)
Did you create a share configuration in the global config?