I think you'd have to use the system groovy build step to do this, but it
should be possible there.
A.
On Tue, Mar 20, 2012 at 10:08 AM, Nicky Ramone wrote:
> Hi.
>
> Is it possible to obtain the upstream build objects in a groovy script
> executed by the Groovy Plugin?
> You can do this in the
Hi,
I already tried that using the MAVEN_OPTS configuration field. But Maven
still uses the old home directory.
On Tuesday, March 20, 2012 7:20:56 PM UTC+1, domi wrote:
>
> add "-Duser.home=/oath/toNewDir" to the options
> /Domi
>
>
> On 20.03.2012, at 13:53, Michael Wieland wrote:
>
> Hi,
>
>
Sorry, Maybe I'm just blind...
xUnit accepts XML-Files like
https://github.com/jenkinsci/xunit-plugin/blob/master/src/test/resources/org/jenkinsci/plugins/xunit/types/check/testcase1/result.xml
I'd like to have a documentation for these files: which elements and
attributes are supported and wh
add "-Duser.home=/oath/toNewDir" to the options
/Domi
On 20.03.2012, at 13:53, Michael Wieland wrote:
> Hi,
>
> thanks for your reply but that didn't solved the problem. :(
>
> This option only changes the location of the local repository. The path to
> the .m2 directory does not change by us
Hi,
I faced a similar issue today on a debian server.
We had some nework problems yesterday. Master was not able to
communicate with the slaves.
After the network establishment the jobs where still stuck.
I tried to reeboot server & slaves but still faced the same issue.
When you stop jenkins a
On Tue, Mar 20, 2012 at 12:54 PM, Tony P wrote:
> Hi,
>
> I have to say "Template" is not quite the right word but I can't
> currently think of a better one..
>
> We have quite a few builds that are based on the same "template", they
> are all clones of a particular build I have called
> "Generic
Hi,
I have to say "Template" is not quite the right word but I can't
currently think of a better one..
We have quite a few builds that are based on the same "template", they
are all clones of a particular build I have called
"Generic_Ivy_Module_Template". All these jobs are identical to the
gener
Hi.
Is it possible to obtain the upstream build objects in a groovy script
executed by the Groovy Plugin?
You can do this in the Groovy Post Build Plugin with:
manager.build.getUpstreamBuilds()
Is there a similar way of doing it?
Thanks
Regards.
FYI I solved this and fixed the bug in the CVS client being used
(https://github.com/mc1arke/cvsclient/pull/1). Do I need to raise a
JIRA issue to make sure it is included in the next plugin release?
Thanks,
James
On Mon, Mar 19, 2012 at 12:59 PM, James Carr wrote:
> Hi All,
>
> I recently upgra
Dear Jan,
Unfortunately, deleting and recreating the nodes did not help in my
case. I am using Linux and not Windows, so the second solution does
not seem to be what I could use.
Regards,
Daniel
On Mar 20, 1:01 pm, Jan Seidel wrote:
> Hi Daniel,
>
> I have had a similar issue some weeks ago.
>
Hi,
On 20/03/2012 11:52, Wilfred Springer wrote:
It turns out that mod_proxy is dropping the 'n' header on its way out. I
tried a number of things to make sure it's getting preserved, but it
isn't. After that, I tried nginx. On the plus side, nginx *does*
preserve the n header on its way out. At
Hi,
We use jenkins with one server and 3 slaves where the builds are done.
There are more than 40 jobs with configuration matrix (up to 16
configurations per job)
Our git repo is big, we cannot have a clone in each workspace.
For that reason on each slave, the repo is in a common directory for
all
Jenkins Users - http://www.ichineseflashcards.com will help you learn
Chinese (Mandarin) faster by using flashcards with pictures, thanks
Hi,
thanks for your reply but that didn't solved the problem. :(
This option only changes the location of the local repository. The path to
the .m2 directory does not change by using this option.
A build fails with this error message:
ERROR: Failed to create /not/existing/user/dir/.m2
I've loo
Hi,
You question is best addressed to jenkinsci-users@googlegroups.com.
jenkinsci-issues@ is used for automated JIRA messages.
That said I've answered your question below etc. and posted to -users
for others to comment as appropriate.
On 20/03/2012 11:39, Programie wrote:
Hi,
I'm using Jenk
The problem is https://issues.jenkins-ci.org/browse/JENKINS-12994. Can you add
a comment to that ticket to say you also have the problem, and possibly vote
for it? At the moment the ticket is unassigned, yet it’s blocking some people
moving to the latest release which has a security fix.
Matthew
Hi Daniel,
I have had a similar issue some weeks ago.
The jobs tied to a specific got stuck for infinite time but the node
was available. Also the configuration was fine. Actually did nothing
change.
I have been researching and troubleshooting quite a while and learned
that deleting and recreating
Now the stuck job got released when I deleted a job that was after it
in the queue. The jobs seem to get stuck in packs, never alone.
On Mar 20, 12:45 pm, Daniel Tkatch wrote:
> Recently, I am experiencing a weird issue.
>
> I have a job whose execution is restricted to a specific node. This
> jo
It turns out that mod_proxy is dropping the 'n' header on its way out. I
tried a number of things to make sure it's getting preserved, but it isn't.
After that, I tried nginx. On the plus side, nginx *does* preserve the n
header on its way out. At the other hand, now all of a sudden Jenkins
sta
Recently, I am experiencing a weird issue.
I have a job whose execution is restricted to a specific node. This
job keeps waiting in the queue even though the node became active. It
seems to be stuck in the queue for a while (several minutes) and gets
released after some time. Hmm..
Any idea what
sorry for the gibberish in the text. I'm a bit tired and in a
hurry ...
e.g fugred instead of figured ;)
On 20 Mrz., 11:56, Jan Seidel wrote:
> Hi folks, thanks for you replies :)
>
> @shanz just fugred it out tonight, was just a bit late to let you
> know.
>
> @Didier your approach won't work as
Hi folks, thanks for you replies :)
@shanz just fugred it out tonight, was just a bit late to let you
know.
@Didier your approach won't work as the env variables you are pointing
to are somewhat static. You can't modiefy them from within a job at
build time.
This would require 3 stages. Manipulat
Oh yes, you need to define subject up near the top of the script and
change the final call to send_mail().
Eg:
import smtplib
import os
from email.MIMEMultipart import MIMEMultipart
from email.MIMEBase import MIMEBase
from email.MIMEText import MIMEText
from email.Utils import COMMASPACE, formatdat
It also happens for the latest version of Jenkins.
In addition, I should say that this only happens if we access the server
through Apache, and that - in that case - I see that the requests sometimes
set the 'n' header (whatever it may be) to 'null':
1. Accept:
text/javascript, text/html, application/xml, text/xml, */*
2. Accept-Charse
All,
We are running Jenkins 1.449, and for some crazy reason for all of our jobs
the job status stops updating after the first update.
Looking with the Chrome developer tools, it turns out that the first call to
/jenkins/job/PQD_BRANCH/buildHistory/ajax
*does* return a table that says that t
26 matches
Mail list logo