What does a 'ls -l /jenkins/tools/JDK/jdk-1.6.24/jdk.sh' say?
It should report the executable bits on i.e.:
-rwxr-xr-x 1 tomcat6 tomcat6
Replace tomcat6 with the respective group and user of your environment.
regards
Dirk
On 10.11.2012 17:22, Fábio Uechi wrote:
> Hi,
>
> I'm running
Hi,
the static analysis plugins hold their state in Maps. At least this has
been the state of affairs last tie i looked. Kohsuke supplied patches
that reduce this amount but when you have the count of warnings you
mentioned it is simply a problem of allocating memory to your
application server ins
Hi,
i cloned your project from github and created a job for it in my jenkins
instance.
The job is of type maven 2/3, git is configured to a repository location
of file:///tmp/murmur-events.
I left the build configuration at default values (maven 3: a local maven
3 installation) and the default r
a.io.FileNotFoundException:
> C:\rob\comp\workspace\murmur-events\target\checkstyle-suppressions.xml
>
> I looked in the target subdirectory and the analysis xml files are not
> there.
>
> How should I configure analysis?
>
> Thanks,
> Rob
>
> -Original Message-
7;. I think that is everything to describe
> my setup...
>
> Rob
>
> -Original Message- From: Dirk Weigenand
> Sent: Thursday, October 04, 2012 8:24 AM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: no code analysis showing up
ference these tools. Is there a
> better example that has a POM setup to use these tools? I poked around
> a bit but I did not find anything.
>
> Rob
>
> -Original Message- From: Dirk Weigenand
> Sent: Thursday, October 04, 2012 7:42 AM
> To: jenkinsci-users@googlegr
Hi,
have a look at how the analysis-plugin family is structured. All plugins
depend on this plugin:
https://github.com/jenkinsci/analysis-config-plugin
which holds the configuration for the various maven static source code
analysis plugins used throughout the build.
regards
Dirk
On 04.10.2012
Hi,
On 03.10.2012 16:21, Rob Withers wrote:
> I stopped using git and went back to what was working before, which was
> setting up a maven2 project. Now I develop in eclipse and I can launch
> a build manually, whenever I want to build the jar and run the tests.
> To get it working, I set the gl
Hi,
i guess this problem is related to files still opened by Jenkins or
another process.
I experience this problem only on Windows when cleaning the workspace.
You should use the equivalent of 'lsof' to find out what file is still
in use by which process.
regards
Dirk
On 03.10.2012 03:51, Rob
Add the timeout property (http://ant.apache.org/manual/Tasks/junit.html) to
your junit ant task (iff you use ant). This will terminate unit tests
taking longer than the specified amount in milliseconds.
For the surefire maven plugin the relevant property is described hier:
http://maven.apache.o
10 matches
Mail list logo