I do have access to the target repo where the GIT submodule is. It's just
that it asks for a password since it is shared repo accessible to
developers via SSH. Seems the GIT plugin breaks on trying to clone the
gitsubmodule since it has no way of knowing the SSH password, basically the
GIT
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
Just to confirm (as some people forget), are you trying the ln -s
command on the command line whilst logged in as the same user that
Jenkins is running under?
Richard.
On Wed, Sep 19, 2012 at 8:16 PM, Ilko Iliev ilkomil...@gmail.com wrote:
Hi,
I'm getting failed: -1 from ln -s at the end of
yes - that's correct, this is the root user. Additional info: jenkins is
running in WebSphere on the same machine:
Product List
ND installed
Installed Product
what is the correct to get the stack trace?
1) failed_test.errorStackTrace
or
2) failed_test.getErrorStackTrace()
I try it with the second and it does not work :-(
JellyException: Could not parse Jelly script : null
Am Donnerstag, 13. Oktober 2011 13:27:12 UTC+2 schrieb Maxime Lemanissier:
Hi Erik,
I personally wouldn’t recommend putting MAVEN_HOME in a profile, rather it is
better to let Jenkins managed this by specifying the version of maven to use.
You can configure this in the Jenkins main config (and then override per slave
if needs be.)
See
Hi James,
In my case, the problem occurs even if we set a specific version of Maven
in build and release configuration. We have 2 Maven versions configured in
Jenkins configuration (Maven 2.2.1 and 3.0.3).
I guess my configuration is very specific : the problem occurs with a *Maven
type jobs*
Hi Michaël
The maven job type plugin at one point never inserted MAVEN_HOME and didn’t add
maven to the path and so the m2release plugin did this to work around this
issue. It sounds like that functionality may have once again disappeared from
the Maven jobtype plugin
/James
From:
Is it a good idea then to not use the GIT plugin and instead clone the
project and update the submodule in a Jenkins build step directly?
Thanks
On Wednesday, September 19, 2012 12:12:25 PM UTC+3, Nicolas De loof wrote:
Indeed,
I've plan to integrate git-plugin with ssh-credentials plugin
Hi All,
I'm setting some environment variables in the Jenkins Master (Manage
Jenkins Configure System Global Properties) but, using the parameterized
build plugin, I'm setting up some new string variables and wanting to use these
global vars as the default values but it doesn't seem to
Hi Erik,
Does the slave machine have MAVEN_HOME set in is environment (either in the OS
or on the Jenkins slave properties)?
Any chance of a log output of a release build with debug logging ( add the -X
flag on the release goals ), and a copy of the maven-release-plugin
configuration you are
Hello,
I'm trying to use Jenkins to poll SCM and run a big series of unit and
integration tests that were parallelized using a Perl program written using
Log::Log4Perl, Parallel::ForkManager, and IPC::Run.
I have version 1.424.6 on Ubuntu Server 12.04.
Strange lockups on writes to STDOUT and
I want to use Jenkins to build projects, that are used by other projects.
How should it be done?
Should I use a matrix build?
I would prefer small jobs that only build one project, and then can trigger
others, if they are using it. - I can easily trigger the build between
jobs, but how should
13 matches
Mail list logo
