no one generating docs?
On Wed, Feb 6, 2013 at 9:01 AM, Ilko Iliev wrote:
> Hi,
>
> I think I'm running into the issues described in JENKINS-6681[1], however
> I have slightly different problem. As described in the issue if I run mvn
> clean deploy site on a multi module pr
Hi,
I think I'm running into the issues described in JENKINS-6681[1], however I
have slightly different problem. As described in the issue if I run mvn
clean deploy site on a multi module project the link gives 401 and there is
no way to get to the combined reports. After that I splitted the goals
I've missed the "Use custom workspace" option under the maven advanced
configuration - I can use this to set up a "remedy" job for the real job,
which operates on the workspace of the real job.
On Tue, Feb 5, 2013 at 8:25 AM, Ilko Iliev wrote:
> Thanks for the info
Thanks for the info.
Wipe out the workspace will leave the versions as changed during the
prepare stage. IMHO this feature will be very helpful to revert to a stable
stage w/out too much extra "magic". It's true that the tag must be removed
manually, if it has been created, but in our case this co
Hi,
I came accross the request for release:rollback on failed release[1],
however it is still marked as opened. From the wiki of the plugin[2] I
can't figure out, if this feature is implemented or not and the RFE is one
and half year old. Can someone give me an info? Or is there some other way
to
Hi,
we experience very long build times after we've done the upgrade to
1.480.2. Our infrastructure hasn't changed and as far as I can see no any
resource issues can be seen (cpu, memory usage, swapping). The build time
increased by factor of appr. 3-4 times - a job taking 11 mins before the
upgra
nobody? should I file a bug for this?
On Wed, Sep 19, 2012 at 12:26 PM, Ilko Iliev wrote:
> yes - that's correct, this is the root user. Additional info: jenkins is
> running in WebSphere on the same machine:
>
r?
>
> Richard.
>
> On Wed, Sep 19, 2012 at 8:16 PM, Ilko Iliev wrote:
> >
> > Hi,
> >
> > I'm getting failed: -1 from ln -s at the end of each build. I saw
> > JENKINS-4301 and JENKINS-4820, which I think is more related to my
> > installatio
Hi,
I'm getting failed: -1 from ln -s at the end of each build. I saw
JENKINS-4301 and JENKINS-4820, which I think is more related to my
installation. I assume this is related to my "exotic" OS:
Linux 3.0.13-0.27-default #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b)
s390x s390x s390x GNU/Linux
J
the xml specifications allows single root elem only - that is why the
parser complains about not well-formed markup
On Wed, Jul 11, 2012 at 3:23 PM, CB wrote:
> Thanks for the information. This confirmed my guess that only 1 per
> file was the answer. I refactored the test source to make
> m
It looks like bug in the JVM. I'd suggest to report this issue to the IBM
support.
On Thu, May 31, 2012 at 11:15 AM, Gildas Cuisinier <
gildas.cuisin...@gcuisinier.net> wrote:
> Hi,
>
> I wanted to install Jenkins on WAS 7.0.
> As I read on the wiki, Jenkins was not working on version before 7.0.
ry_abc"
> My branch name is "Release1"
>
> Where I need to change the URL??
>
> --
> View this message in context:
> http://jenkins.361315.n4.nabble.com/Need-to-checkout-from-Branch-and-build-the-project-tp4403930p4403954.html
> Sent from the Jenkins users mail
12 matches
Mail list logo
