Hi,
I've run in similar problems and found there is an issue in Jira. Here the
link to my original post with reference to the issue:
https://groups.google.com/d/topic/jenkinsci-users/0MCof-NrzCE/discussion
If you find some direct working solution beside of "Archive artifacts" I'll
be glad if y
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
gin
${maven-javadoc-plugin.version}
In reactor there are only the module references defined and the scm section
for the release goals (these will be run in a separate job)
Or shoud I report it to JENKINS-6681
TIA,
Ilko
[1] https://issues.jenkins-ci.org/browse/JENKINS-6
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
ete the tag if it created it anyway - so depending on
what failed you may well need to do something by hand anyway.
Regards,
/James
On Monday, 4 February 2013 16:58:34 UTC, Ilko wrote:
>
> Hi,
>
> I came accross the request for release:rollback on failed release[1],
> howev
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
(SCMTrigger.java:420)
[1/8/13 23:15:54:586 CET] 000e1396 SystemErr R at
hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
TIA,
Ilko
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
- r11_20120322_22976
GC - R26_Java626_SR2_20120322_1722_B106210
J9CL - 20120322_106210)
JCL - 20120316_01
Jenkins at 1.447.2
ln -s from command line works as expected.
I can't find any log entries in the log files.
Someone aware of this problem and fix for it?
TIA,
Ilko
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
13 matches
Mail list logo
