nch". Then you configure Subversion SCM to check out the URL "
> http://evc.io.comcast.net/chimps/branches/$RCBranch";. Use the same
> credentials. If there's a validation error ("$RCBranch" doesn't exist")
> ignore it and/or configure Subversion SCM
I'm trying to build a selectable subversion branch. When I select the
branch from the dropdown, and kick off the build it fails because it hasn't
actually pulled the code from svn and so the workspace is empty.
This seems like the simplest use case, so I don't understand why it doesn't
work.
Jenk
but in the
meantime I learned how to set up and run hyperic agent and hyperic server
which will likely prove valuable.
On Wed, Sep 26, 2012 at 5:09 AM, Ed Young wrote:
>
> I'm trying unsuccessfully to deploy from jenkins to the Spring Insight
> server (embedded tomcat 7) usi
I should probably mention that this is Spring Insight version VMware
vFabric tc Runtime 2.7.1.RELEASE/6.0.35.B.RELEASE.
On Wed, Sep 26, 2012 at 5:09 AM, Ed Young wrote:
>
> I'm trying unsuccessfully to deploy from jenkins to the Spring Insight
> server (embedded tomcat 7) usi
I'm trying unsuccessfully to deploy from jenkins to the Spring Insight
server (embedded tomcat 7) using the Jenkins Deploy to Container plugin
https://wiki.jenkins-ci.org/display/JENKINS/Deploy+Plugin
Is this the right plugin or is there another for Spring Insight?
I've used it to deploy succes
ou have,
> so it should always keep the most recent successful build, no matter how
> old.
>
> Note that this might not occur properly with multiconfiguration builds, as
> I've seen them not clean up properly, but don't know if that's fixed
> recently or not.
>
> Scot
at hudson.model.Run.run(Run.java:1488)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> at
> hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:239)
>
> The job did not retry
ntroller.java:88)
> at hudson.model.Executor.run(Executor.java:239)
>
> The job did not retry.
>
> Can you submit a bug against the Naginator plugin?
>
> Thanks,
> Mark Waite
>
> --
> *From:* Ed Young
> *To:* jenkinsci-user
ild red (failed) or yellow (unstable)?
>
> Mark Waite
>
>
> From: Sami Tikka
> To: "jenkinsci-users@googlegroups.com"
> Sent: Sunday, September 16, 2012 11:08 AM
>
> Subject: Re: retry build upon failure?
>
> Could you p
ci-users@googlegroups.com] On Behalf Of nicolas de loof
> Sent: Friday, September 14, 2012 6:16 AM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: retry build upon failure?
>
>
>
> see http://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin
>
> 2012/9/14 Ed Young
>
that test coverage has dropped, for
example, I can go back and see where that happened. I'm not sure of
any other way to track this kind of thing without keeping a large
number of builds.
On Fri, Sep 14, 2012 at 6:11 AM, Lars Nordin wrote:
> -Original Message-----
> From: Ed Young
&g
Is it possible to retry a build upon a failure? Maybe with a retry count?
iconfiguration builds, as
> I've seen them not clean up properly, but don't know if that's fixed
> recently or not.
>
> Scott
>
>
> On Thu, Sep 13, 2012 at 4:03 PM, Ed Young wrote:
>>
>> I need to clear out some drive space on our build machine by delet
I need to clear out some drive space on our build machine by deleting
old builds, but manually selecting each one and deleting it is too
painful.
If I change Max # of builds to keep from 100 to 10, will Jenkins
automatically delete the 90 that I no longer want, or do I need to
delete them by hand?
14 matches
Mail list logo