I can, but not till tomorrow. Thanks for looking into it with me. -Ed
On Sun, Sep 16, 2012 at 10:29 PM, Mark Waite wrote:
> I see that you've already submitted Jenkins-15184. Can you investigate if
> your failure mode is the same failure mode as the one I describe below?
>
> If it is the same,
In our ERP structure, modules folder is there, which contains inbuilt
modules aswellas customized modules. Only customized modules exist in the
repository..so any commit comes to this, i have to put it in one job copy
to module folder of other jobs. if i do direct checkout to modules folder,
it wil
I see that you've already submitted Jenkins-15184. Can you investigate if your
failure mode is the same failure mode as the one I describe below?
If it is the same, then you can attach this information to the bug report (and
you can use it as a work around).
If it is not the same, then I can
done:
https://issues.jenkins-ci.org/browse/JENKINS-15184
I'll do some more investigating, as well.
Thanks,
Ed
On Sun, Sep 16, 2012 at 10:09 PM, Mark Waite wrote:
> I think you've found a bug. At least, my initial experiments seem to
> confirm the same results you reported.
>
> I had never e
I further simplified my configuration by removing Jenkins and its configuration
files completely from a test computer, then I installed Jenkins 1.466.2,
installed the Naginator plugin, and confirmed it was the only plugin installed.
I created a new Jenkins job with a shell command "exit 1" and
You may be able to do something with groovy scripting, other than
that, I am not sure if there would be an automated way to do it. This
is one of the major bummers of the split, some large divergences have
crept in.
slide
On Sat, Sep 15, 2012 at 7:08 PM, Stefan Schwoegler wrote:
> kinda with the
I think you've found a bug. At least, my initial experiments seem to confirm
the same results you reported.
I had never experimented with the Naginator plugin before. I installed it into
a Jenkins 1.466.2 installation and created a new free style project with a
single build step, a shell with
Sounds like we have some terminology differences. These are test
failures, which I consider a failed builds. I've experimented with the
configuration in many different ways and it never results in a retry,
even when I set it to retry after "unstable" builds (test failure I
guess)
If the build pass
For a start, jenkins saves its configurations in a folder so to be independant
of each other you need to override it for each instance :
https://wiki.jenkins-ci.org/display/JENKINS/Tomcat
Also other options to set the http port and others are specified here :
https://wiki.jenkins-ci.org/display
Hello everyone. I'm sorry if what I am about to ask will sound completely
retarded, but then so be it.
Okay, first off, I have no idea what I'm doing and the only reason I'm
doing it is because I want to be able to provide free jenkins's for people
that want them, specifically within the minecr
The configuration only (as far as I'm aware) allows for a directory to
be given so if thats given it should only archive stuff below that
folder.
So I'm guessing that if you put your html file in a folder by itself
you should be able to simply point at that folder.
Richard.
On Fri, Sep 14, 2012
I'm guessing the server isn't internet connected and needs to go via a
proxy server? Check out the advanced settings in the Manage Plugins
area to set the proxy server up.
Richard.
On Fri, Sep 14, 2012 at 6:58 PM, Anba wrote:
> Hi All,
>
> I'm new to Jenkins.Today only i have started to learn C
I guess the question I have is what is the purpose of the first job?
Why would job #2 do the checkout of the source code?
Richard.
On Thu, Sep 13, 2012 at 6:42 PM, Varghese Renny
wrote:
> Hi
> Two jobs
> 1 job- taking pull with update from one repository and copying it to the
> workspace
Hi all,
I noticed that a new LTS was released on the 13th Sep - v1.466.2. Is there a
changelog for this release. http://jenkins-ci.org/changelog-stable has 1.466.1
as the latest changelog.
Cheers
Adam
This e-mail is sent by Suncorp Group Limited ABN 66 145
When Ed says the build is a"hard failure", I assumed that meant the build
status was "Failed" and would be marked red. However, in parentheses he says
"(test failures)". Typically, test failures mark the build as "unstable", not
as "failed". If the build is unstable, I would not expect a "ret
Could you post exactly what you see in the console log of the failed build?
Also, it might help if you could post your job config.xml or put in
pastebin/gist so we could take a look.
-- Sami
Ed Young kirjoitti 14.9.2012 kello 22.38:
> I installed the Naginator Plugin (v1.8) because the retry
16 matches
Mail list logo
