Re: Publish over CIFS configuration

2017-09-21 Thread Slide 
The issue with publish-over-cifs right now is that it only supports very
old SMB protocol versions (jCIFS, the library used to do the CIFS accesses
only supports those old protocols). I am in the process of updating to
using SMBJ, which only supports the newer protocols, but I have not made a
lot of headway at this point.

On Thu, Sep 21, 2017 at 7:36 AM OxyOX  wrote:

> I have a similar error. What is the reason? help me please
>
>
> An exception was caught when invoking perform
> jcifs.smb.SmbException: Failed to connect: 0.0.0.0<00>/172.26.28.113
> jcifs.util.transport.TransportException
> java.net.SocketException: Connection reset
> at java.net.SocketInputStream.read(Unknown Source)
> at java.net.SocketInputStream.read(Unknown Source)
> at jcifs.util.transport.Transport.readn(Transport.java:29)
> at jcifs.smb.SmbTransport.peekKey(SmbTransport.java:388)
> at jcifs.smb.SmbTransport.negotiate(SmbTransport.java:288)
> at jcifs.smb.SmbTransport.doConnect(SmbTransport.java:319)
> at jcifs.util.transport.Transport.run(Transport.java:241)
> at java.lang.Thread.run(Unknown Source)
>
> at jcifs.util.transport.Transport.run(Transport.java:258)
> at java.lang.Thread.run(Unknown Source)
>
> at jcifs.smb.SmbTransport.connect(SmbTransport.java:309)
> at jcifs.smb.SmbTree.treeConnect(SmbTree.java:156)
> at jcifs.smb.SmbFile.doConnect(SmbFile.java:911)
> at jcifs.smb.SmbFile.connect(SmbFile.java:954)
> at jcifs.smb.SmbFile.connect0(SmbFile.java:880)
> at jcifs.smb.SmbFile.exists(SmbFile.java:1415)
> at
>
> jenkins.plugins.publish_over_cifs.CifsHostConfiguration.testConfig(CifsHostConfiguration.java:203)
> Caused: jenkins.plugins.publish_over.BapPublisherException: Exception when
> testing config. URL [smb://172.26.28.113/jenkis/], Message: [Failed to
> connect: 0.0.0.0<00>/172.26.28.113]
> at
>
> jenkins.plugins.publish_over_cifs.CifsHostConfiguration.testConfig(CifsHostConfiguration.java:206)
> at
>
> jenkins.plugins.publish_over_cifs.CifsHostConfiguration.createClient(CifsHostConfiguration.java:97)
> at
>
> jenkins.plugins.publish_over_cifs.CifsHostConfiguration.createClient(CifsHostConfiguration.java:47)
> at
>
> jenkins.plugins.publish_over.BPHostConfiguration.createClient(BPHostConfiguration.java:96)
> at
>
> jenkins.plugins.publish_over.BapPublisher$Performer.perform(BapPublisher.java:229)
> at
>
> jenkins.plugins.publish_over.BapPublisher$Performer.access$000(BapPublisher.java:205)
> at
> jenkins.plugins.publish_over.BapPublisher.perform(BapPublisher.java:158)
> at
>
> jenkins.plugins.publish_over_cifs.CifsPublisher.perform(CifsPublisher.java:63)
> at
>
> jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:64)
> Caused: jenkins.plugins.publish_over.BapPublisherException: Exception when
> publishing, exception message [Exception when testing config. URL
> [smb://172.26.28.113/jenkis/], Message: [Failed to connect:
> 0.0.0.0<00>/172.26.28.113]]
> at
>
> jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:68)
> at
>
> jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:37)
> at hudson.FilePath.act(FilePath.java:998)
> at hudson.FilePath.act(FilePath.java:976)
> at
>
> jenkins.plugins.publish_over.BPInstanceConfig.perform(BPInstanceConfig.java:138)
> at jenkins.plugins.publish_over.BPPlugin.perform(BPPlugin.java:111)
> at
>
> jenkins.plugins.publish_over_cifs.CifsBuilderPlugin.perform(CifsBuilderPlugin.java:61)
> at
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> at
>
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735)
> at hudson.model.Build$BuildExecution.build(Build.java:206)
> at hudson.model.Build$BuildExecution.doRun(Build.java:163)
> at
>
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:490)
> at hudson.model.Run.execute(Run.java:1735)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> at
> hudson.model.ResourceController.execute(ResourceController.java:97)
> at hudson.model.Executor.run(Executor.java:405)
>
>
>
>
>
> --
> Sent from:
> http://jenkins-ci.361315.n4.nabble.com/Jenkins-users-f361316.html
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1505989782623-0.post%40n4.nabble.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are

Re: Publish over CIFS configuration

2017-09-21 Thread OxyOX 
I have a similar error. What is the reason? help me please 


An exception was caught when invoking perform
jcifs.smb.SmbException: Failed to connect: 0.0.0.0<00>/172.26.28.113
jcifs.util.transport.TransportException
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.net.SocketInputStream.read(Unknown Source)
at jcifs.util.transport.Transport.readn(Transport.java:29)
at jcifs.smb.SmbTransport.peekKey(SmbTransport.java:388)
at jcifs.smb.SmbTransport.negotiate(SmbTransport.java:288)
at jcifs.smb.SmbTransport.doConnect(SmbTransport.java:319)
at jcifs.util.transport.Transport.run(Transport.java:241)
at java.lang.Thread.run(Unknown Source)

at jcifs.util.transport.Transport.run(Transport.java:258)
at java.lang.Thread.run(Unknown Source)

at jcifs.smb.SmbTransport.connect(SmbTransport.java:309)
at jcifs.smb.SmbTree.treeConnect(SmbTree.java:156)
at jcifs.smb.SmbFile.doConnect(SmbFile.java:911)
at jcifs.smb.SmbFile.connect(SmbFile.java:954)
at jcifs.smb.SmbFile.connect0(SmbFile.java:880)
at jcifs.smb.SmbFile.exists(SmbFile.java:1415)
at
jenkins.plugins.publish_over_cifs.CifsHostConfiguration.testConfig(CifsHostConfiguration.java:203)
Caused: jenkins.plugins.publish_over.BapPublisherException: Exception when
testing config. URL [smb://172.26.28.113/jenkis/], Message: [Failed to
connect: 0.0.0.0<00>/172.26.28.113]
at
jenkins.plugins.publish_over_cifs.CifsHostConfiguration.testConfig(CifsHostConfiguration.java:206)
at
jenkins.plugins.publish_over_cifs.CifsHostConfiguration.createClient(CifsHostConfiguration.java:97)
at
jenkins.plugins.publish_over_cifs.CifsHostConfiguration.createClient(CifsHostConfiguration.java:47)
at
jenkins.plugins.publish_over.BPHostConfiguration.createClient(BPHostConfiguration.java:96)
at
jenkins.plugins.publish_over.BapPublisher$Performer.perform(BapPublisher.java:229)
at
jenkins.plugins.publish_over.BapPublisher$Performer.access$000(BapPublisher.java:205)
at 
jenkins.plugins.publish_over.BapPublisher.perform(BapPublisher.java:158)
at
jenkins.plugins.publish_over_cifs.CifsPublisher.perform(CifsPublisher.java:63)
at
jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:64)
Caused: jenkins.plugins.publish_over.BapPublisherException: Exception when
publishing, exception message [Exception when testing config. URL
[smb://172.26.28.113/jenkis/], Message: [Failed to connect:
0.0.0.0<00>/172.26.28.113]]
at
jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:68)
at
jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:37)
at hudson.FilePath.act(FilePath.java:998)
at hudson.FilePath.act(FilePath.java:976)
at
jenkins.plugins.publish_over.BPInstanceConfig.perform(BPInstanceConfig.java:138)
at jenkins.plugins.publish_over.BPPlugin.perform(BPPlugin.java:111)
at
jenkins.plugins.publish_over_cifs.CifsBuilderPlugin.perform(CifsBuilderPlugin.java:61)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:490)
at hudson.model.Run.execute(Run.java:1735)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:405)





--
Sent from: http://jenkins-ci.361315.n4.nabble.com/Jenkins-users-f361316.html

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1505989782623-0.post%40n4.nabble.com.
For more options, visit https://groups.google.com/d/optout.

Re: Publish over CIFS configuration

2017-09-05 Thread Ted 
After some examination of logs & discussion on IRC.  Slide & I determined
that the problem is that I am requiring a min protocol of SMB2.  While this
is an important feature (protects against WannaCry), it is not implemented
in jcifs, which is the library currently used for the smbclient
connection.  He suggested that there are some Java libraries that may
support protocols above SMB1 (e.g. smbj), but for now that is what we've
run into.  I will be looking into alternative ways to publish my builds.

On Tue, Sep 5, 2017 at 5:22 PM Ted  wrote:

> this is the full stack trace:
>
> jenkins.plugins.publish_over.BapPublisherException: 
> jenkins.plugins.publish_over.BapPublisherException: Exception when testing 
> config. URL [smb://192.168.1.201/shared/], Message: [Failed to connect: 
> 0.0.0.0<00>/192.168.1.201]
>   at 
> jenkins.plugins.publish_over_cifs.CifsHostConfiguration.testConfig(CifsHostConfiguration.java:206)
>   at 
> jenkins.plugins.publish_over_cifs.CifsHostConfiguration.createClient(CifsHostConfiguration.java:97)
>   at 
> jenkins.plugins.publish_over_cifs.descriptor.CifsPublisherPluginDescriptor.doTestConnection(CifsPublisherPluginDescriptor.java:158)
>   at 
> java.lang.invoke.MethodHandle.invokeWithArguments(java.base@9-internal/MethodHandle.java:636)
>   at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)
>   at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)
>   at 
> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)
>   at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129)
>   at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
>   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)
>   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)
>   at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248)
>   at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
>   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)
>   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)
>   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
>   at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
>   at 
> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)
>   at 
> hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:138)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
>   at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:80)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
>   at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
>   at 
> hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
>   at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>   at 
> jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
>   at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>   at 
> org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
>   at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>   at 
> org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
>   at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>   at 
> org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
>   at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>   at 
> jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:92)
>   at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>   at 
> org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
>   at 
> hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
>   at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>   at 
> hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90)
>   at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
>   at 
>

Re: Publish over CIFS configuration

2017-09-05 Thread Ted 
this is the full stack trace:

jenkins.plugins.publish_over.BapPublisherException:
jenkins.plugins.publish_over.BapPublisherException: Exception when
testing config. URL [smb://192.168.1.201/shared/], Message: [Failed to
connect: 0.0.0.0<00>/192.168.1.201]
at 
jenkins.plugins.publish_over_cifs.CifsHostConfiguration.testConfig(CifsHostConfiguration.java:206)
at 
jenkins.plugins.publish_over_cifs.CifsHostConfiguration.createClient(CifsHostConfiguration.java:97)
at 
jenkins.plugins.publish_over_cifs.descriptor.CifsPublisherPluginDescriptor.doTestConnection(CifsPublisherPluginDescriptor.java:158)
at 
java.lang.invoke.MethodHandle.invokeWithArguments(java.base@9-internal/MethodHandle.java:636)
at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)
at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)
at 
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:138)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:80)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at 
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:92)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at 
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at 
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at 
org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at

Re: Publish over CIFS configuration

2017-09-04 Thread Slide 
I have uploaded a version of the plugin to
https://earl-of-code.com/publish-over-cifs.hpi that should give the whole
stack trace for the error when using the check connection. Please let me
know the full exception message and I'll see what I can find in the code.

On Sat, Sep 2, 2017 at 12:02 PM Slide  wrote:

> I and on the jenkins irc channel, though not at the moment or today most
> likely. If you get on there look for slide-o-mix
>
> On Sat, Sep 2, 2017, 09:11 Ted  wrote:
>
>> is there a live chat we can do? irc or something?  I'd even be willing to
>> screen share if necessary.
>>
>> On Sat, Sep 2, 2017 at 12:09 PM Slide  wrote:
>>
>>> Ok, I'll try and get something up soon with some additional logging.
>>>
>>> On Sat, Sep 2, 2017, 08:43 Ted  wrote:
>>>
 I'd be willing to try whatever you need.  I am unable to track down the
 logs from the crash last time.  As I said, it's not doing it now.

 On Sat, Sep 2, 2017 at 11:27 AM Slide  wrote:

> If you are willing, I can provide a plugin hpi file with additional
> logging to see if we can't figure out what the problem is. Would you be
> willing to do that? What is in the logs when Jenkins crashes completely?
>
> On Sat, Sep 2, 2017, 08:11 Ted  wrote:
>
>> nothing on that log either, though it didn't crash this time.
>>
>> On Sat, Sep 2, 2017 at 10:57 AM Ted Winslow 
>> wrote:
>>
>>> Nope.  Nada. I can tell you that I have tested a bit more.  When I
>>> add the functionality anyway (in spite of the errors) running the build
>>> results in a crash of Jenkins altogether.  I can check if that logs
>>> anything if that will help.
>>>
>>> I'm working with samba shares, in case you're curious.
>>>
>>> Also, I apologize for taking so long to reply.  I thought I had
>>> email notifications on for this thread and apparently I did not.  I do 
>>> now
>>> so it shouldn't be a problem.
>>>
>>> On Tuesday, August 29, 2017 at 9:10:33 PM UTC-4, slide wrote:

 I've recently taken over maintaining this plugin, I am not super
 familiar with it yet. Is there anything in the Jenkins logs?

 On Tue, Aug 29, 2017, 13:29 Ted Winslow  wrote:

> Bump.  Anybody?
>
>
> On Saturday, August 26, 2017 at 12:24:05 AM UTC-4, Ted Winslow
> wrote:
>>
>> I don't seem to be understanding the configuration of the Publish
>> over CIFS plugin.
>>
>> I installed the plugin and am trying to add a CIFS node to no
>> avail.  It is showing every field as invalid as I look at the 
>> configuration
>> page, which I am guessing is not relevant.  I am trying to publish to
>> another server and I even went so far as to mount the drive locally 
>> to
>> verify everything was working.  Unfortunately, when I click "Test
>> Configuration" I get this error:
>>
>> Cannot read share (or directory on share)
>>
>> jenkins.plugins.publish_over.BapPublisherException: Exception when 
>> testing config. URL [smb://192.168.1.201/shared/], Message: [Failed 
>> to connect: 0.0.0.0<00>/192.168.1.201]
>>
>>
>> Any idea what I'm doing wrong?
>>
>> I can tell you that it is a guest share with public Read/Write
>> that I was able to mount as guest in fstab (but it required the ver=3
>> flag).  I didn't enter any username or password for that reason.  I 
>> want to
>> copy my builds over to my deployment server so it can deploy the 
>> builds
>> after they complete.
>>
>>
>> 
>>
>> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/11e8057a-1082-4adf-a0ac-d44cd5e91f70%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>>
>> You received this message because you are subscribed to a topic in
>>> the Google Groups "Jenkins Users" group.
>>> To unsubscribe from this topic, visit
>>>

Re: Publish over CIFS configuration

2017-09-02 Thread Slide 
I and on the jenkins irc channel, though not at the moment or today most
likely. If you get on there look for slide-o-mix

On Sat, Sep 2, 2017, 09:11 Ted  wrote:

> is there a live chat we can do? irc or something?  I'd even be willing to
> screen share if necessary.
>
> On Sat, Sep 2, 2017 at 12:09 PM Slide  wrote:
>
>> Ok, I'll try and get something up soon with some additional logging.
>>
>> On Sat, Sep 2, 2017, 08:43 Ted  wrote:
>>
>>> I'd be willing to try whatever you need.  I am unable to track down the
>>> logs from the crash last time.  As I said, it's not doing it now.
>>>
>>> On Sat, Sep 2, 2017 at 11:27 AM Slide  wrote:
>>>
 If you are willing, I can provide a plugin hpi file with additional
 logging to see if we can't figure out what the problem is. Would you be
 willing to do that? What is in the logs when Jenkins crashes completely?

 On Sat, Sep 2, 2017, 08:11 Ted  wrote:

> nothing on that log either, though it didn't crash this time.
>
> On Sat, Sep 2, 2017 at 10:57 AM Ted Winslow 
> wrote:
>
>> Nope.  Nada. I can tell you that I have tested a bit more.  When I
>> add the functionality anyway (in spite of the errors) running the build
>> results in a crash of Jenkins altogether.  I can check if that logs
>> anything if that will help.
>>
>> I'm working with samba shares, in case you're curious.
>>
>> Also, I apologize for taking so long to reply.  I thought I had email
>> notifications on for this thread and apparently I did not.  I do now so 
>> it
>> shouldn't be a problem.
>>
>> On Tuesday, August 29, 2017 at 9:10:33 PM UTC-4, slide wrote:
>>>
>>> I've recently taken over maintaining this plugin, I am not super
>>> familiar with it yet. Is there anything in the Jenkins logs?
>>>
>>> On Tue, Aug 29, 2017, 13:29 Ted Winslow  wrote:
>>>
 Bump.  Anybody?


 On Saturday, August 26, 2017 at 12:24:05 AM UTC-4, Ted Winslow
 wrote:
>
> I don't seem to be understanding the configuration of the Publish
> over CIFS plugin.
>
> I installed the plugin and am trying to add a CIFS node to no
> avail.  It is showing every field as invalid as I look at the 
> configuration
> page, which I am guessing is not relevant.  I am trying to publish to
> another server and I even went so far as to mount the drive locally to
> verify everything was working.  Unfortunately, when I click "Test
> Configuration" I get this error:
>
> Cannot read share (or directory on share)
>
> jenkins.plugins.publish_over.BapPublisherException: Exception when 
> testing config. URL [smb://192.168.1.201/shared/], Message: [Failed 
> to connect: 0.0.0.0<00>/192.168.1.201]
>
>
> Any idea what I'm doing wrong?
>
> I can tell you that it is a guest share with public Read/Write
> that I was able to mount as guest in fstab (but it required the ver=3
> flag).  I didn't enter any username or password for that reason.  I 
> want to
> copy my builds over to my deployment server so it can deploy the 
> builds
> after they complete.
>
>
> 
>
> --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Users" group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to jenkinsci-use...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-users/11e8057a-1082-4adf-a0ac-d44cd5e91f70%40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>> --
>>
> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-users/O-DH2XUBRt8/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-users+unsubscr...@googlegroups.com.
>
>
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/081ed5fa-1f83-4cb6-9aa5-8c59ec3cbca2%40googlegroups.com
>>

Re: Publish over CIFS configuration

2017-09-02 Thread Ted 
is there a live chat we can do? irc or something?  I'd even be willing to
screen share if necessary.

On Sat, Sep 2, 2017 at 12:09 PM Slide  wrote:

> Ok, I'll try and get something up soon with some additional logging.
>
> On Sat, Sep 2, 2017, 08:43 Ted  wrote:
>
>> I'd be willing to try whatever you need.  I am unable to track down the
>> logs from the crash last time.  As I said, it's not doing it now.
>>
>> On Sat, Sep 2, 2017 at 11:27 AM Slide  wrote:
>>
>>> If you are willing, I can provide a plugin hpi file with additional
>>> logging to see if we can't figure out what the problem is. Would you be
>>> willing to do that? What is in the logs when Jenkins crashes completely?
>>>
>>> On Sat, Sep 2, 2017, 08:11 Ted  wrote:
>>>
 nothing on that log either, though it didn't crash this time.

 On Sat, Sep 2, 2017 at 10:57 AM Ted Winslow 
 wrote:

> Nope.  Nada. I can tell you that I have tested a bit more.  When I add
> the functionality anyway (in spite of the errors) running the build 
> results
> in a crash of Jenkins altogether.  I can check if that logs anything if
> that will help.
>
> I'm working with samba shares, in case you're curious.
>
> Also, I apologize for taking so long to reply.  I thought I had email
> notifications on for this thread and apparently I did not.  I do now so it
> shouldn't be a problem.
>
> On Tuesday, August 29, 2017 at 9:10:33 PM UTC-4, slide wrote:
>>
>> I've recently taken over maintaining this plugin, I am not super
>> familiar with it yet. Is there anything in the Jenkins logs?
>>
>> On Tue, Aug 29, 2017, 13:29 Ted Winslow  wrote:
>>
>>> Bump.  Anybody?
>>>
>>>
>>> On Saturday, August 26, 2017 at 12:24:05 AM UTC-4, Ted Winslow wrote:

 I don't seem to be understanding the configuration of the Publish
 over CIFS plugin.

 I installed the plugin and am trying to add a CIFS node to no
 avail.  It is showing every field as invalid as I look at the 
 configuration
 page, which I am guessing is not relevant.  I am trying to publish to
 another server and I even went so far as to mount the drive locally to
 verify everything was working.  Unfortunately, when I click "Test
 Configuration" I get this error:

 Cannot read share (or directory on share)

 jenkins.plugins.publish_over.BapPublisherException: Exception when 
 testing config. URL [smb://192.168.1.201/shared/], Message: [Failed to 
 connect: 0.0.0.0<00>/192.168.1.201]


 Any idea what I'm doing wrong?

 I can tell you that it is a guest share with public Read/Write that
 I was able to mount as guest in fstab (but it required the ver=3 
 flag).  I
 didn't enter any username or password for that reason.  I want to copy 
 my
 builds over to my deployment server so it can deploy the builds after 
 they
 complete.


 

 --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>> send an email to jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/11e8057a-1082-4adf-a0ac-d44cd5e91f70%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>
 You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/O-DH2XUBRt8/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.


> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/081ed5fa-1f83-4cb6-9aa5-8c59ec3cbca2%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
 --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Users" group.

>>> To unsubscribe from this

Re: Publish over CIFS configuration

2017-09-02 Thread Slide 
Ok, I'll try and get something up soon with some additional logging.

On Sat, Sep 2, 2017, 08:43 Ted  wrote:

> I'd be willing to try whatever you need.  I am unable to track down the
> logs from the crash last time.  As I said, it's not doing it now.
>
> On Sat, Sep 2, 2017 at 11:27 AM Slide  wrote:
>
>> If you are willing, I can provide a plugin hpi file with additional
>> logging to see if we can't figure out what the problem is. Would you be
>> willing to do that? What is in the logs when Jenkins crashes completely?
>>
>> On Sat, Sep 2, 2017, 08:11 Ted  wrote:
>>
>>> nothing on that log either, though it didn't crash this time.
>>>
>>> On Sat, Sep 2, 2017 at 10:57 AM Ted Winslow  wrote:
>>>
 Nope.  Nada. I can tell you that I have tested a bit more.  When I add
 the functionality anyway (in spite of the errors) running the build results
 in a crash of Jenkins altogether.  I can check if that logs anything if
 that will help.

 I'm working with samba shares, in case you're curious.

 Also, I apologize for taking so long to reply.  I thought I had email
 notifications on for this thread and apparently I did not.  I do now so it
 shouldn't be a problem.

 On Tuesday, August 29, 2017 at 9:10:33 PM UTC-4, slide wrote:
>
> I've recently taken over maintaining this plugin, I am not super
> familiar with it yet. Is there anything in the Jenkins logs?
>
> On Tue, Aug 29, 2017, 13:29 Ted Winslow  wrote:
>
>> Bump.  Anybody?
>>
>>
>> On Saturday, August 26, 2017 at 12:24:05 AM UTC-4, Ted Winslow wrote:
>>>
>>> I don't seem to be understanding the configuration of the Publish
>>> over CIFS plugin.
>>>
>>> I installed the plugin and am trying to add a CIFS node to no
>>> avail.  It is showing every field as invalid as I look at the 
>>> configuration
>>> page, which I am guessing is not relevant.  I am trying to publish to
>>> another server and I even went so far as to mount the drive locally to
>>> verify everything was working.  Unfortunately, when I click "Test
>>> Configuration" I get this error:
>>>
>>> Cannot read share (or directory on share)
>>>
>>> jenkins.plugins.publish_over.BapPublisherException: Exception when 
>>> testing config. URL [smb://192.168.1.201/shared/], Message: [Failed to 
>>> connect: 0.0.0.0<00>/192.168.1.201]
>>>
>>>
>>> Any idea what I'm doing wrong?
>>>
>>> I can tell you that it is a guest share with public Read/Write that
>>> I was able to mount as guest in fstab (but it required the ver=3 flag). 
>>>  I
>>> didn't enter any username or password for that reason.  I want to copy 
>>> my
>>> builds over to my deployment server so it can deploy the builds after 
>>> they
>>> complete.
>>>
>>>
>>> 
>>>
>>> --
>> You received this message because you are subscribed to the Google
>> Groups "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to jenkinsci-use...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/11e8057a-1082-4adf-a0ac-d44cd5e91f70%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --

>>> You received this message because you are subscribed to a topic in the
 Google Groups "Jenkins Users" group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/jenkinsci-users/O-DH2XUBRt8/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to
 jenkinsci-users+unsubscr...@googlegroups.com.
>>>
>>>
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-users/081ed5fa-1f83-4cb6-9aa5-8c59ec3cbca2%40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/CAPOFNUwFE53gU7K4MZW07MuqALy78x_G7231YOT%3DMU00JZDNWg%40mail.gmail.com
>>>

Re: Publish over CIFS configuration

2017-09-02 Thread Ted 
I'd be willing to try whatever you need.  I am unable to track down the
logs from the crash last time.  As I said, it's not doing it now.

On Sat, Sep 2, 2017 at 11:27 AM Slide  wrote:

> If you are willing, I can provide a plugin hpi file with additional
> logging to see if we can't figure out what the problem is. Would you be
> willing to do that? What is in the logs when Jenkins crashes completely?
>
> On Sat, Sep 2, 2017, 08:11 Ted  wrote:
>
>> nothing on that log either, though it didn't crash this time.
>>
>> On Sat, Sep 2, 2017 at 10:57 AM Ted Winslow  wrote:
>>
>>> Nope.  Nada. I can tell you that I have tested a bit more.  When I add
>>> the functionality anyway (in spite of the errors) running the build results
>>> in a crash of Jenkins altogether.  I can check if that logs anything if
>>> that will help.
>>>
>>> I'm working with samba shares, in case you're curious.
>>>
>>> Also, I apologize for taking so long to reply.  I thought I had email
>>> notifications on for this thread and apparently I did not.  I do now so it
>>> shouldn't be a problem.
>>>
>>> On Tuesday, August 29, 2017 at 9:10:33 PM UTC-4, slide wrote:

 I've recently taken over maintaining this plugin, I am not super
 familiar with it yet. Is there anything in the Jenkins logs?

 On Tue, Aug 29, 2017, 13:29 Ted Winslow  wrote:

> Bump.  Anybody?
>
>
> On Saturday, August 26, 2017 at 12:24:05 AM UTC-4, Ted Winslow wrote:
>>
>> I don't seem to be understanding the configuration of the Publish
>> over CIFS plugin.
>>
>> I installed the plugin and am trying to add a CIFS node to no avail.
>> It is showing every field as invalid as I look at the configuration page,
>> which I am guessing is not relevant.  I am trying to publish to another
>> server and I even went so far as to mount the drive locally to verify
>> everything was working.  Unfortunately, when I click "Test 
>> Configuration" I
>> get this error:
>>
>> Cannot read share (or directory on share)
>>
>> jenkins.plugins.publish_over.BapPublisherException: Exception when 
>> testing config. URL [smb://192.168.1.201/shared/], Message: [Failed to 
>> connect: 0.0.0.0<00>/192.168.1.201]
>>
>>
>> Any idea what I'm doing wrong?
>>
>> I can tell you that it is a guest share with public Read/Write that I
>> was able to mount as guest in fstab (but it required the ver=3 flag).  I
>> didn't enter any username or password for that reason.  I want to copy my
>> builds over to my deployment server so it can deploy the builds after 
>> they
>> complete.
>>
>>
>> 
>>
>> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/11e8057a-1082-4adf-a0ac-d44cd5e91f70%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>>
>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Jenkins Users" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/jenkinsci-users/O-DH2XUBRt8/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> jenkinsci-users+unsubscr...@googlegroups.com.
>>
>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/081ed5fa-1f83-4cb6-9aa5-8c59ec3cbca2%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>>
> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CAPOFNUwFE53gU7K4MZW07MuqALy78x_G7231YOT%3DMU00JZDNWg%40mail.gmail.com
>> 
>> .
>
>
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because

Re: Publish over CIFS configuration

2017-09-02 Thread Slide 
If you are willing, I can provide a plugin hpi file with additional logging
to see if we can't figure out what the problem is. Would you be willing to
do that? What is in the logs when Jenkins crashes completely?

On Sat, Sep 2, 2017, 08:11 Ted  wrote:

> nothing on that log either, though it didn't crash this time.
>
> On Sat, Sep 2, 2017 at 10:57 AM Ted Winslow  wrote:
>
>> Nope.  Nada. I can tell you that I have tested a bit more.  When I add
>> the functionality anyway (in spite of the errors) running the build results
>> in a crash of Jenkins altogether.  I can check if that logs anything if
>> that will help.
>>
>> I'm working with samba shares, in case you're curious.
>>
>> Also, I apologize for taking so long to reply.  I thought I had email
>> notifications on for this thread and apparently I did not.  I do now so it
>> shouldn't be a problem.
>>
>> On Tuesday, August 29, 2017 at 9:10:33 PM UTC-4, slide wrote:
>>>
>>> I've recently taken over maintaining this plugin, I am not super
>>> familiar with it yet. Is there anything in the Jenkins logs?
>>>
>>> On Tue, Aug 29, 2017, 13:29 Ted Winslow  wrote:
>>>
 Bump.  Anybody?


 On Saturday, August 26, 2017 at 12:24:05 AM UTC-4, Ted Winslow wrote:
>
> I don't seem to be understanding the configuration of the Publish over
> CIFS plugin.
>
> I installed the plugin and am trying to add a CIFS node to no avail.
> It is showing every field as invalid as I look at the configuration page,
> which I am guessing is not relevant.  I am trying to publish to another
> server and I even went so far as to mount the drive locally to verify
> everything was working.  Unfortunately, when I click "Test Configuration" 
> I
> get this error:
>
> Cannot read share (or directory on share)
>
> jenkins.plugins.publish_over.BapPublisherException: Exception when 
> testing config. URL [smb://192.168.1.201/shared/], Message: [Failed to 
> connect: 0.0.0.0<00>/192.168.1.201]
>
>
> Any idea what I'm doing wrong?
>
> I can tell you that it is a guest share with public Read/Write that I
> was able to mount as guest in fstab (but it required the ver=3 flag).  I
> didn't enter any username or password for that reason.  I want to copy my
> builds over to my deployment server so it can deploy the builds after they
> complete.
>
>
> 
>
> --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Users" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to jenkinsci-use...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-users/11e8057a-1082-4adf-a0ac-d44cd5e91f70%40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>> --
>>
> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-users/O-DH2XUBRt8/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-users+unsubscr...@googlegroups.com.
>
>
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/081ed5fa-1f83-4cb6-9aa5-8c59ec3cbca2%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAPOFNUwFE53gU7K4MZW07MuqALy78x_G7231YOT%3DMU00JZDNWg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit

Re: Publish over CIFS configuration

2017-09-02 Thread Ted 
nothing on that log either, though it didn't crash this time.

On Sat, Sep 2, 2017 at 10:57 AM Ted Winslow  wrote:

> Nope.  Nada. I can tell you that I have tested a bit more.  When I add the
> functionality anyway (in spite of the errors) running the build results in
> a crash of Jenkins altogether.  I can check if that logs anything if that
> will help.
>
> I'm working with samba shares, in case you're curious.
>
> Also, I apologize for taking so long to reply.  I thought I had email
> notifications on for this thread and apparently I did not.  I do now so it
> shouldn't be a problem.
>
> On Tuesday, August 29, 2017 at 9:10:33 PM UTC-4, slide wrote:
>>
>> I've recently taken over maintaining this plugin, I am not super familiar
>> with it yet. Is there anything in the Jenkins logs?
>>
>> On Tue, Aug 29, 2017, 13:29 Ted Winslow  wrote:
>>
>>> Bump.  Anybody?
>>>
>>>
>>> On Saturday, August 26, 2017 at 12:24:05 AM UTC-4, Ted Winslow wrote:

 I don't seem to be understanding the configuration of the Publish over
 CIFS plugin.

 I installed the plugin and am trying to add a CIFS node to no avail.
 It is showing every field as invalid as I look at the configuration page,
 which I am guessing is not relevant.  I am trying to publish to another
 server and I even went so far as to mount the drive locally to verify
 everything was working.  Unfortunately, when I click "Test Configuration" I
 get this error:

 Cannot read share (or directory on share)

 jenkins.plugins.publish_over.BapPublisherException: Exception when testing 
 config. URL [smb://192.168.1.201/shared/], Message: [Failed to connect: 
 0.0.0.0<00>/192.168.1.201]


 Any idea what I'm doing wrong?

 I can tell you that it is a guest share with public Read/Write that I
 was able to mount as guest in fstab (but it required the ver=3 flag).  I
 didn't enter any username or password for that reason.  I want to copy my
 builds over to my deployment server so it can deploy the builds after they
 complete.


 

 --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/11e8057a-1082-4adf-a0ac-d44cd5e91f70%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/O-DH2XUBRt8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/081ed5fa-1f83-4cb6-9aa5-8c59ec3cbca2%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPOFNUwFE53gU7K4MZW07MuqALy78x_G7231YOT%3DMU00JZDNWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Publish over CIFS configuration

2017-09-02 Thread Ted Winslow 
Nope.  Nada. I can tell you that I have tested a bit more.  When I add the 
functionality anyway (in spite of the errors) running the build results in 
a crash of Jenkins altogether.  I can check if that logs anything if that 
will help.

I'm working with samba shares, in case you're curious.

Also, I apologize for taking so long to reply.  I thought I had email 
notifications on for this thread and apparently I did not.  I do now so it 
shouldn't be a problem.

On Tuesday, August 29, 2017 at 9:10:33 PM UTC-4, slide wrote:
>
> I've recently taken over maintaining this plugin, I am not super familiar 
> with it yet. Is there anything in the Jenkins logs? 
>
> On Tue, Aug 29, 2017, 13:29 Ted Winslow  
> wrote:
>
>> Bump.  Anybody?
>>
>>
>> On Saturday, August 26, 2017 at 12:24:05 AM UTC-4, Ted Winslow wrote:
>>>
>>> I don't seem to be understanding the configuration of the Publish over 
>>> CIFS plugin.
>>>
>>> I installed the plugin and am trying to add a CIFS node to no avail.  It 
>>> is showing every field as invalid as I look at the configuration page, 
>>> which I am guessing is not relevant.  I am trying to publish to another 
>>> server and I even went so far as to mount the drive locally to verify 
>>> everything was working.  Unfortunately, when I click "Test Configuration" I 
>>> get this error:
>>>
>>> Cannot read share (or directory on share)
>>>
>>> jenkins.plugins.publish_over.BapPublisherException: Exception when testing 
>>> config. URL [smb://192.168.1.201/shared/], Message: [Failed to connect: 
>>> 0.0.0.0<00>/192.168.1.201]
>>>
>>>
>>> Any idea what I'm doing wrong?
>>>
>>> I can tell you that it is a guest share with public Read/Write that I 
>>> was able to mount as guest in fstab (but it required the ver=3 flag).  I 
>>> didn't enter any username or password for that reason.  I want to copy my 
>>> builds over to my deployment server so it can deploy the builds after they 
>>> complete.
>>>
>>>
>>> 
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/11e8057a-1082-4adf-a0ac-d44cd5e91f70%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/081ed5fa-1f83-4cb6-9aa5-8c59ec3cbca2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Publish over CIFS configuration

2017-08-29 Thread Slide 
I've recently taken over maintaining this plugin, I am not super familiar
with it yet. Is there anything in the Jenkins logs?

On Tue, Aug 29, 2017, 13:29 Ted Winslow  wrote:

> Bump.  Anybody?
>
>
> On Saturday, August 26, 2017 at 12:24:05 AM UTC-4, Ted Winslow wrote:
>>
>> I don't seem to be understanding the configuration of the Publish over
>> CIFS plugin.
>>
>> I installed the plugin and am trying to add a CIFS node to no avail.  It
>> is showing every field as invalid as I look at the configuration page,
>> which I am guessing is not relevant.  I am trying to publish to another
>> server and I even went so far as to mount the drive locally to verify
>> everything was working.  Unfortunately, when I click "Test Configuration" I
>> get this error:
>>
>> Cannot read share (or directory on share)
>>
>> jenkins.plugins.publish_over.BapPublisherException: Exception when testing 
>> config. URL [smb://192.168.1.201/shared/], Message: [Failed to connect: 
>> 0.0.0.0<00>/192.168.1.201]
>>
>>
>> Any idea what I'm doing wrong?
>>
>> I can tell you that it is a guest share with public Read/Write that I was
>> able to mount as guest in fstab (but it required the ver=3 flag).  I didn't
>> enter any username or password for that reason.  I want to copy my builds
>> over to my deployment server so it can deploy the builds after they
>> complete.
>>
>>
>> 
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/11e8057a-1082-4adf-a0ac-d44cd5e91f70%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVczXcDb99%3DCaUvaJHVO0uO-jWFokARGdcU6LcD3yUfrdw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Publish over CIFS configuration

2017-08-29 Thread Ted Winslow 
Bump.  Anybody?

On Saturday, August 26, 2017 at 12:24:05 AM UTC-4, Ted Winslow wrote:
>
> I don't seem to be understanding the configuration of the Publish over 
> CIFS plugin.
>
> I installed the plugin and am trying to add a CIFS node to no avail.  It 
> is showing every field as invalid as I look at the configuration page, 
> which I am guessing is not relevant.  I am trying to publish to another 
> server and I even went so far as to mount the drive locally to verify 
> everything was working.  Unfortunately, when I click "Test Configuration" I 
> get this error:
>
> Cannot read share (or directory on share)
>
> jenkins.plugins.publish_over.BapPublisherException: Exception when testing 
> config. URL [smb://192.168.1.201/shared/], Message: [Failed to connect: 
> 0.0.0.0<00>/192.168.1.201]
>
>
> Any idea what I'm doing wrong?
>
> I can tell you that it is a guest share with public Read/Write that I was 
> able to mount as guest in fstab (but it required the ver=3 flag).  I didn't 
> enter any username or password for that reason.  I want to copy my builds 
> over to my deployment server so it can deploy the builds after they 
> complete.
>
>
> 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/11e8057a-1082-4adf-a0ac-d44cd5e91f70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Publish over CIFS configuration

2017-08-25 Thread Ted Winslow 
I don't seem to be understanding the configuration of the Publish over CIFS 
plugin.

I installed the plugin and am trying to add a CIFS node to no avail.  It is 
showing every field as invalid as I look at the configuration page, which I 
am guessing is not relevant.  I am trying to publish to another server and 
I even went so far as to mount the drive locally to verify everything was 
working.  Unfortunately, when I click "Test Configuration" I get this error:

Cannot read share (or directory on share)

jenkins.plugins.publish_over.BapPublisherException: Exception when testing 
config. URL [smb://192.168.1.201/shared/], Message: [Failed to connect: 
0.0.0.0<00>/192.168.1.201]


Any idea what I'm doing wrong?

I can tell you that it is a guest share with public Read/Write that I was 
able to mount as guest in fstab (but it required the ver=3 flag).  I didn't 
enter any username or password for that reason.  I want to copy my builds 
over to my deployment server so it can deploy the builds after they 
complete.



-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/843d2807-c0ec-427b-8520-f72fd2354800%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.