Yes, you should really open your own thread so people could see your issue On Monday, September 23, 2013 1:43:20 PM UTC+3, Manjunath D G wrote:
> Hye Sorry to miss lead this tread... > > > > *From:* Manjunath DG <[email protected] <javascript:>> > *To:* "[email protected] <javascript:>" < > [email protected] <javascript:>> > *Sent:* Monday, September 23, 2013 4:02 PM > *Subject:* Re: Jenkins with P4 over Assembla - Unable to check workspace > against depot > Hi All, > There are three projects for which Jenkins is automatically deleting the > logs despite the fact settings are otherwise, The logs are getting deleted > hourly only specific to those 3 projects. Rest all other projects are not > having any concern.Unable to find the root cause of this issue. Can > someone please help us to fix this and if noticed the same in past. > Our environment is with Jenkins version 1.522 and running on Ubuntu Os. > I have all set with Discard Old Builds, But still noticing the logs are > not stored. This is not the case with other projects. I have almost 100 > projects and out of this only 3 projects are having issue. > > Discard Old Builds > > <https://jenkins-swcoe.india.ti.com/view/VAYU/job/VAYU_BSP_AUTO/configure> > > Strategy > Log Rotation > > > Days to keep builds > if not empty, build records are only kept up to this number of days > > Max # of builds to keep > if not empty, only up to this number of build records are kept > > > Thank you and Best Regards*,* > *Manjunath D G* > > *From:* "[email protected] <javascript:>" <[email protected]<javascript:> > > > *To:* [email protected] <javascript:> > *Sent:* Monday, September 23, 2013 3:24 PM > *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] 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] 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.
