The build fails although it doesn't do much of anything, but I never thought about checking if that is the reason, just realized if there's a red error sentence it's probably this.. Well you were right. Everything works now despite of that weird error.
On Monday, September 23, 2013 3:43:57 PM UTC+3, rginga wrote: > > Is this causing a problem? I have seen it on all the builds I have > created. I let Jenkins handle the workspaces for all our builds now. > > > > But I seem to remember that it always worked although it complained. > > > > *From:* [email protected] <javascript:> [mailto: > [email protected] <javascript:>] *On Behalf Of * > [email protected] <javascript:> > *Sent:* Monday, September 23, 2013 5:55 AM > *To:* [email protected] <javascript:> > *Subject:* Jenkins with P4 over Assembla - Unable to check workspace > against depot > > > > I'm trying to connect my Jenkins server with perforce. The depot is > sitting on Assembla's servers. > > I managed to install p4v with all the settings and everything work. > > Jenkins throws the "Unable to check workspace against depot" error > whenever I try to define a workspace (i'm using one which is already > defined and has a path on this computer). > > Is there a way to at least find out what the problem is? Why is Jenkins > unable to check workspace against depot? (And yes, I added the correct path > to p4 under the configuration menu) > > Thank you! > > -- > 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 [email protected] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
