Hi,
It seems that particular class
"org.sonatype.guice.bean.locators.MutableBeanLocator"
wasn't loaded in your jenkins instance for some reason, probably that
plugin is using that transitive dependency from another library.
What sauce-ondemand version are you using? Have you tried to upgrade i
Hi,
Do you use the junit plugin
(https://wiki.jenkins-ci.org/display/JENKINS/JUnit+Plugin) in your jenkins
job?
Cheers
On Wednesday, 6 January 2016 05:23:30 UTC+1, foolhunger Hsiao wrote:
>
> Hi, all
>
> I was trying to use groovy postbuild plugin to get test failure count, and
> test pass c
Increase number of executors to 2 or 3.
This will allow parallel executions of jenkins tasks.
On Friday, March 9, 2012 at 1:26:10 PM UTC+5:30, matthew...@diamond.ac.uk
wrote:
>
> The problem is https://issues.jenkins-ci.org/browse/JENKINS-12994. Sami,
> can you add a comment to that ticket to s
Yes. I have done everything. This affects all users. Uninstalled and
re-installed the plugin. Removed the plugin. Restarted the service.
Restarted the server. Should there not be a .xml or java file I can tweak?
On Tuesday, January 5, 2016 at 4:01:39 PM UTC-5, Baptiste Mathus wrote:
>
> J
I had a friend at the office compile the master branch of the git plugin on
his MacOS machine with maven 3.3.1 and Java 1.8.0_60. No test failures for
him either. I truly don't know what's different about your environment
that causes the tests to fail.
Mark Waite
On Tue, Jan 5, 2016 at 9:01 PM
Thanks Victor
I think I have found the issue, it works with maven style jobs but doesn't work
with freestyle ones, not sure whether that's intentional or a bug
Maybe I should open a Jira issue for this
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users
IMO, freestyle jobs don't know what a test means unless there are some post
build actions to parse those *unit files, therefore you shouldn't raise a
ticket since that's the expected behavior I guess so.
Cheers
--
You received this message because you are subscribed to the Google Groups
"Jenk
If you use Eclipse, make sure you do a clean build in maven. Not doing so
will result in odd failures with all things related to annotation
processing, such as the error message you are getting.
Vincent
2016-01-06 17:22 GMT+01:00 Mark Waite :
> I had a friend at the office compile the master bra
Really appreciate the suggestions.
To eliminate eclipse, I cloned https://github.com/jenkinsci/git-plugin.git
to a new directory and built with maven. Same issue. Wonder if this is
caused by my version of OS X (10.11.2) El Capitan.I'm going to check
the maven groups.
On Wednesday, Januar
Maybe it is the way how it works, many thanks, really helps
On Thursday, January 7, 2016 at 2:14:54 AM UTC+8, Victor Martinez wrote:
>
> IMO, freestyle jobs don't know what a test means unless there are some
> post build actions to parse those *unit files, therefore you shouldn't
> raise a ticke
I've solved the build issue. Actually, I managed to work around it.
Ultimately, I deleted my local maven repo (~/.m2/repository/*) and reran
the build. The subsequent build ran, suggesting that one or more of the
existing artifacts in my local maven repo was causing the problem, or
perhaps w
Hi Yarden.
No reason I didn't use it, just a) didn't know about it and b) probably
didn't think to look. at the time I found systemd rather frustrating to
diagnose so keeping the directives used fairly minimal worked for me (this
was quite a few years ago when systemd was still a bit controver
12 matches
Mail list logo
