from:"Christoph Kutzinski"

Aw: Re: Re: Build Pipeline plugin and Build Flow plugin

2015-07-21 Thread Christoph Kutzinski

Am I right when saying the thebuildgraphview-plugin is a king of after the fact view of a pipeline run?

I.e. I can see the results of a pipeline afterwards, but I can not actively control a pipeline (lie in the Build Pipeline pluing):

- starting a new pipeline run

- re-running a build

- triggering manul steps

Gesendet:Dienstag, 21. Juli 2015 um 14:45 Uhr
Von:nicolas de loof nicolas.del...@gmail.com
An:jenkinsci-users@googlegroups.com jenkinsci-users@googlegroups.com
Betreff:Re: Re: Build Pipeline plugin and Build Flow plugin

build graph view do rely on upstreamCause so should handle most relations between builds
and for the others (including build-flow) do offer an extension point to discover other relations

2015-07-21 16:44 GMT+02:00 Christoph Kutzinski ku...@gmx.de:

Thanks!

I didnt know abouthttps://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin

Can I also define manual triggered steps in a setup of the Build-Flow plugin and the build-graphview-plugin like you can do with the build pipeline plugin?

Gesendet:Dienstag, 21. Juli 2015 um 14:37 Uhr
Von:nicolas de loof nicolas.del...@gmail.com
An:jenkinsci-users@googlegroups.com jenkinsci-users@googlegroups.com
Betreff:Re: Build Pipeline plugin and Build Flow plugin

build flow did introduce buildgraphview-plugin for this exact use case

build pipeline only can rendre static and mostly sequential pipelines

2015-07-21 16:19 GMT+02:00 Christoph Kutzinski ku...@gmx.de:

Hi,

Im trying to set up a CD pipeline with Jenkins where I can

I) concisely define the relationship (triggers) between the single pipeline steps (jobs)

II) have a nice visualisation of the full pipeline

The Build Flow plugin is a good fit for I, while the Build Pipeline plugin is a nice fit for II.

However, the Build Pipeline plugin doesnt seem to understand the job dependencies defined via the Build Flow plugin.

Does someone have experiences with similar setups? What is your solution for this?

cheers

Christoph

--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzm6OBmC7pgunTgTjFX8qmdjAjQWxwaw-QHpsNbyoPRX4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-6e98f37c-ab18-4f08-9ac4-6db9b3071625-1437490941266%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

Build Pipeline plugin and Build Flow plugin

2015-07-21 Thread Christoph Kutzinski

Hi,



Im trying to set up a CD pipeline with Jenkins where I can



I) concisely define the relationship (triggers) between the single pipeline steps (jobs)

II) have a nice visualisation of the full pipeline



The Build Flow plugin is a good fit for I, while the Build Pipeline plugin is a nice fit for II.

However, the Build Pipeline plugin doesnt seem to understand the job dependencies defined via the Build Flow plugin.



Does someone have experiences with similar setups? What is your solution for this?





cheers

Christoph





-- 
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

Aw: Re: Build Pipeline plugin and Build Flow plugin

2015-07-21 Thread Christoph Kutzinski

Yes,

but it doesnt have any visualisation, either (unless I use Jenkins Enterprise), has it?

Did you considered using workflow plugin ?

2015-07-21 16:37 GMT+02:00 nicolas de loof nicolas.del...@gmail.com:

build flow did introduce buildgraphview-plugin for this exact use case

build pipeline only can rendre static and mostly sequential pipelines

2015-07-21 16:19 GMT+02:00 Christoph Kutzinski ku...@gmx.de:

Hi,

Im trying to set up a CD pipeline with Jenkins where I can

I) concisely define the relationship (triggers) between the single pipeline steps (jobs)

II) have a nice visualisation of the full pipeline

The Build Flow plugin is a good fit for I, while the Build Pipeline plugin is a nice fit for II.

However, the Build Pipeline plugin doesnt seem to understand the job dependencies defined via the Build Flow plugin.

Does someone have experiences with similar setups? What is your solution for this?

cheers

Christoph

--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJz%3D%3DrnO8MxedwwrWBecgE%3Dz-vJVkAfgy%3DKZ04s8uqCBoAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-66b6d313-9f9c-4a6f-a975-d2550388efd6-1437489730953%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

Aw: Re: Build Pipeline plugin and Build Flow plugin

2015-07-21 Thread Christoph Kutzinski

Thanks!

I didnt know abouthttps://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin

Can I also define manual triggered steps in a setup of the Build-Flow plugin and the build-graphview-plugin like you can do with the build pipeline plugin?

build flow did introduce buildgraphview-plugin for this exact use case

build pipeline only can rendre static and mostly sequential pipelines

2015-07-21 16:19 GMT+02:00 Christoph Kutzinski ku...@gmx.de:

Hi,

Im trying to set up a CD pipeline with Jenkins where I can

I) concisely define the relationship (triggers) between the single pipeline steps (jobs)

II) have a nice visualisation of the full pipeline

The Build Flow plugin is a good fit for I, while the Build Pipeline plugin is a nice fit for II.

However, the Build Pipeline plugin doesnt seem to understand the job dependencies defined via the Build Flow plugin.

Does someone have experiences with similar setups? What is your solution for this?

cheers

Christoph

--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

Re: java process consumes up to 200% CPU while using the UI

2015-04-12 Thread Christoph Kutzinski

There's also the jstack tool which comes which each JDK which can take a 
stack trace of Jenkins. That might also help to figure out the original 
problem.



Am 11.04.2015 um 17:23 schrieb Brian J. Murrell:

On Fri, 2015-04-10 at 11:31 -0400, Brent Atkinson wrote:


You're right, but connecting locally should not require the remote ports
bound,


No.  You are right about that.  But the problem is that the complaint is
not isolated to the JMX report options.  *Any* JMX option yields a
complaint about duplicate options being found.


Anyone know why this doesn't work
out-of-the-box?


Yes, indeed.  Anyone at all?  Please.


At this point, you have options:

   * figure out how to enable remote JMX (why it's failing for you)
   * figure out how to enable local JMX (not sure what's involved)


Right.  These seem like the most fruitful paths but not really knowing
anything at all about how Java applications are developed or deployed
(i.e. I have no clue what a Jar is or what Winstone is, etc.) I'm kind
of grasping in the dark here.


* go another route, such as the monitoring plugin (can't vouch for it)


I suspect analysing it from outside (i.e. jconsole) will be more
fruitful that analysing from the inside.

I did manage to find out that performance is better, (but still not what
I would expect) with one of the following plugins disabled:

antisamy-markup-formatter.jpi.disabled
ant.jpi.disabled
cobertura.jpi.disabled
configurationslicing.jpi.disabled
credentials.jpi.disabled
cvs.jpi.disabled
external-monitor-job.jpi.disabled
git.jpi.disabled
javadoc.jpi.disabled
locks-and-latches.jpi.disabled
mapdb-api.jpi.disabled
scm-api.jpi.disabled
ssh-slaves.jpi.disabled
subversion.jpi.disabled
throttle-concurrents.jpi.disabled
translation.jpi.disabled
windows-slaves.jpi.disabled
xunit.jpi.disabled
xvnc.jpi.disabled

But brute-force is not really the most fruitful way to go about this,
particularly when disabling random plugins can actually prevent Jenkins
from starting up -- leading to a yak-shaving exercise in debugging
plugin dependencies.

Plus the fact that even with every single plugin we have installed
disabled, performance is still sluggish, just not as sluggish as with
one or more of the above plugins enabled.  With one or more of the above
plugins enabled, job-configure is particularly slow.

In any case, maybe time for a new thread on this list about how to
enable JMX with Jenkins...

Cheers,
b.



--
You received this message because you are subscribed to the Google Groups Jenkins 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/552A34ED.6050207%40gmx.de.
For more options, visit https://groups.google.com/d/optout.

Re: How to force an upstream job to be green

2015-01-10 Thread Christoph Kutzinski

If I understand your requirements correctly, I would use the build flow
plugin: https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin

Make the controller job a build flow job which calls the other 3 jobs in
a guard-rescue block each and let them re-run once if they fail in the
rescue block.

Other alternatives might be the workflow plugin
https://github.com/jenkinsci/workflow-plugin
or the build pipeline plugin
https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin

but I don't have much experience with them.

HTH
Christoph

Am 10.01.2015 um 00:05 schrieb Lam Le:

I have a job which act as a controller. It call subsequent job using
the 'Trigger/call builds on other projects' plugin. The controller call
3 other jobs, if any of these job fail, then it will rerun itself.

Controller:
J#1 - Pass
J#2 - Pass
J#3 - Fail, retry and Pass

In this case, the controller job will be marked as Failed on the
history. How do I force this to become green/successful? I am
currently using the promote plugin which only put a green star next to
failure in the history. The issue with this is in the upper view level,
it still show the controller as a RED/Fail unless someone click into it
to view the history. I want it to truly be green in the upper level view.

Thanks.

--
You received this message because you are subscribed to the Google
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-users+unsubscr...@googlegroups.com
mailto:jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/d723225c-4039-40fd-a51b-a78f30b7dfa4%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-users/d723225c-4039-40fd-a51b-a78f30b7dfa4%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups Jenkins
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/54B0FBA9.8000805%40gmx.de.
For more options, visit https://groups.google.com/d/optout.

Re: How to force an upstream job to be green

2015-01-10 Thread Christoph Kutzinski

Much better of course to use the retry statement of the build-flow plugin:

retry ( 3 ) {
build( this_job_may_fail )
}

Am 10.01.2015 um 11:15 schrieb Christoph Kutzinski:

If I understand your requirements correctly, I would use the build flow
plugin: https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin

Make the controller job a build flow job which calls the other 3 jobs in
a guard-rescue block each and let them re-run once if they fail in the
rescue block.

Other alternatives might be the workflow plugin
https://github.com/jenkinsci/workflow-plugin
or the build pipeline plugin
https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin
but I don't have much experience with them.

HTH
Christoph

Am 10.01.2015 um 00:05 schrieb Lam Le:

Controller:
J#1 - Pass
J#2 - Pass
J#3 - Fail, retry and Pass

Thanks.

https://groups.google.com/d/msgid/jenkinsci-users/d723225c-4039-40fd-a51b-a78f30b7dfa4%40googlegroups.com?utm_medium=emailutm_source=footer.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups Jenkins
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/54B0FC1F.40804%40gmx.de.
For more options, visit https://groups.google.com/d/optout.

Re: Urgent Need Java Resources Candidates, Immediate Interview

2014-12-26 Thread Christoph Kutzinski

I'd *really* like to work in a company which thinks of myself as a 
resource instead of a human!


Am 26.12.2014 um 17:25 schrieb david browse:


Urgent Need Java Resources Candidates, Immediate Interview

Contact id:_david@browseinfosolutions.com_ Number: _248 845 2142 ext: 303_

__

__

__


  Role:Java Resources

*Location:Saint Louis, MO ***

*Duration:**Long-term*

*Telecom Domain***

**

Client is looking for a sr. Java resource who can design and implement 
timely and reliable Software Solutions.


Develop configuration-driven, self-monitoring, scalable solutions that 
can easiy accomidate ongoing enhancements.


Provide subject matter expertise for production systems and document 
maintaince and support procedures.


**

*Job Summary***

8+ years (senior level) design and development experience in Java 
(Core Java, Spring, web services using CXF)


8+ years (senior level) design and development experience in Perl, 
specifically, the following skills:


-Application development (as opposed to strictly CGI or maintenance 
scripts)


-DBI/DBD, especially Sybase and Oracle; DBIx is a plus

-Usage as well as creation of Perl modules

Advanced SQL/database programming in one or more of the following 
commercial relational databases: MSSQL, Oracle, MySQL


- Experience with XML, HTML, VB Script, CGI, Java Script, AJAX

- Experience with Tomcat or JBoss and web technologies such as SOAP, 
REST and RMI


- Experience with source control packages such as Subversion or CVS

- Experience with J2EE (Servlets, JSP's, Custom Java Tags, etc.)

-Competency in basic Linux platform development and deployment activities

-Demonstrated experience with unit testing frameworks (e.g. JUnit, 
Test::More) and a solid understanding of unit testing fundamentals.


--
You received this message because you are subscribed to the Google 
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to jenkinsci-users+unsubscr...@googlegroups.com 
mailto:jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ce93b894-18d9-4fa1-838d-10fc2b33e5ef%40googlegroups.com 
https://groups.google.com/d/msgid/jenkinsci-users/ce93b894-18d9-4fa1-838d-10fc2b33e5ef%40googlegroups.com?utm_medium=emailutm_source=footer.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups Jenkins 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/549D9C37.40406%40gmx.de.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins ircbot leaking OutputThreads

2014-11-01 Thread Christoph Kutzinski

Would be great if you could test the build, I linked to the issue, 
before I cut a new release.


Am 01.11.2014 um 12:24 schrieb Luciano Furtado:

Hi Cristoph,

I see that a fix was commited , thank you so much.

Do you have any plans for a new release of the irc plugin ?

Best Regards.

On Tuesday, October 28, 2014 10:50:39 PM UTC, Luciano Rodrigues Furtado
wrote:

Hey Cristoph,


I have opened the ticket as requested JENKINS-25349 - Leaking ircbot
OutputThreads https://issues.jenkins-ci.org/browse/JENKINS-25349.


Please let me know if I can help in any way.


Cheers.

On Oct 28, 2014 9:17 PM, Christoph Kutzinski ku...@gmx.de
javascript: wrote:

Thanks for the info.
Can you open a new JIRA issue against the ircbot and attach the
information below?

thanks
Kutzi

Am 28.10.2014 um 22:02 schrieb Luciano Furtado:

Hi Everybody,


We have a Jenkins instance that connects to a irc server over
ipsec, the Jenkins server after running for over a week, ends
up with about 300 OutputThreads for the irc-plugin .

we are running on Jenkins Jenkins ver. 1.565.3
http://jenkins-ci.org/ with irc plugin 2.25

https://jnk04n.dev.tripadvisor.com/pluginManager/plugin/ircbot/thirdPartyLicenses
 /
CentOS 6.5 / OpenJdk 1.6

The connection to the irc server is bit flaky , so it seems to
get disconnected from time to time, our theory is that the
OutputThreads are not getting interrupted after the connection
is lost and re-established.

So everytime we reconnect another Outputthread is leaked.


When we take jstack dump  on the jenkins process this is what
we see below (I truncated the output to reduce the size of the
email), please let me know if any further info is need to
throubleshoot this issue:


Thanks in advance,
Luciano


--
bot283-output daemon prio=10 tid=0x7fd518159800
nid=0x7b3 waiting on condition [0x7fd3d62e1000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  0x0005912d31b0 (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at
java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
at

java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:386)
at org.pircbotx.OutputThread.run(OutputThread.java:101)

--
bot282-output daemon prio=10 tid=0x7fd518158800
nid=0x7ff0 waiting on condition [0x7fd3ca6a5000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  0x000590b18d98 (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at
java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
at

java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:386)
at org.pircbotx.OutputThread.run(OutputThread.java:101)

--
bot281-output daemon prio=10 tid=0x7fd518157800
nid=0x75c9 waiting on condition [0x7fd3cebea000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  0x000590219238 (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at
java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
at

java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:386)
at org.pircbotx.OutputThread.run(OutputThread.java:101)

--
bot280-output daemon prio=10 tid=0x7fd518156800
nid=0x6f40 waiting on condition [0x7fd3c9f9e000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  0x000587ad2da0 (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at
java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043

Re: Jenkins ircbot leaking OutputThreads

2014-10-28 Thread Christoph Kutzinski


Thanks for the info.
Can you open a new JIRA issue against the ircbot and attach the 
information below?


thanks
Kutzi

Am 28.10.2014 um 22:02 schrieb Luciano Furtado:

Hi Everybody,


We have a Jenkins instance that connects to a irc server over ipsec, 
the Jenkins server after running for over a week, ends up with about 
300 OutputThreads for the irc-plugin .


we are running on Jenkins Jenkins ver. 1.565.3 
http://jenkins-ci.org/ with irc plugin 2.25 
https://jnk04n.dev.tripadvisor.com/pluginManager/plugin/ircbot/thirdPartyLicenses / 
CentOS 6.5 / OpenJdk 1.6


The connection to the irc server is bit flaky , so it seems to get 
disconnected from time to time, our theory is that the OutputThreads 
are not getting interrupted after the connection is lost and 
re-established.


So everytime we reconnect another Outputthread is leaked.


When we take jstack dump  on the jenkins process this is what we see 
below (I truncated the output to reduce the size of the email), please 
let me know if any further info is need to throubleshoot this issue:



Thanks in advance,
Luciano


--
bot283-output daemon prio=10 tid=0x7fd518159800 nid=0x7b3 
waiting on condition [0x7fd3d62e1000]

   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  0x0005912d31b0 (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at 
java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
at 
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:386)

at org.pircbotx.OutputThread.run(OutputThread.java:101)

--
bot282-output daemon prio=10 tid=0x7fd518158800 nid=0x7ff0 
waiting on condition [0x7fd3ca6a5000]

   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  0x000590b18d98 (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at 
java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
at 
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:386)

at org.pircbotx.OutputThread.run(OutputThread.java:101)

--
bot281-output daemon prio=10 tid=0x7fd518157800 nid=0x75c9 
waiting on condition [0x7fd3cebea000]

   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  0x000590219238 (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at 
java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
at 
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:386)

at org.pircbotx.OutputThread.run(OutputThread.java:101)

--
bot280-output daemon prio=10 tid=0x7fd518156800 nid=0x6f40 
waiting on condition [0x7fd3c9f9e000]

   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  0x000587ad2da0 (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at 
java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
at 
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:386)

at org.pircbotx.OutputThread.run(OutputThread.java:101)


--
You received this message because you are subscribed to the Google 
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to jenkinsci-users+unsubscr...@googlegroups.com 
mailto:jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups Jenkins 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Examine Jenkins thread state with Dumpling

2014-09-22 Thread Christoph Kutzinski


Looks like a nice tool!

Am 22.09.2014 um 18:28 schrieb oliver gondža:

Hi,

There is a plugin that bring Dumpling DSL into Jenkins:
https://wiki.jenkins-ci.org/display/JENKINS/Dumpling+Plugin

What's Dumpling?

Domain model and DSL to query thread state. Read more here:
https://olivergondza.github.io/dumpling/



--
You received this message because you are subscribed to the Google Groups Jenkins 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem Perform Maven Release

2014-08-16 Thread Christoph Kutzinski

A simpler - and IMHO much cleaner - way would be to add the target 
folder to svn:ignore.
You shouldn't have any local modifications during the release process, 
otherwise you're doing it wrong!



Am 16.08.2014 um 07:17 schrieb Adam Guja:

You can use checkModificationExcludes
as stated
here 
http://stackoverflow.com/questions/16199154/maven-releaseprepare-cannot-prepare-the-release-because-you-have-local-modifi
if the changes are done during the release

W dniu czwartek, 14 sierpnia 2014 18:35:43 UTC+2 użytkownik Leandro
Andrade napisał:

Hi guys.
I have a problem when I try to do Perform Maven Release:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare (default-cli) on 
project test: Cannot prepare the release because you have local modifications :
[ERROR] [target/apidocs:unknown]
[ERROR] [target/classes:unknown]
[ERROR] [target/test-1.5.30-SNAPSHOT:unknown]
[ERROR] [target/test-1.5.30-SNAPSHOT-javadoc.jar:unknown]
[ERROR] [target/test-1.5.30-SNAPSHOT-sources.jar:unknown]
[ERROR] [target/test-1.5.30-SNAPSHOT.war:unknown]
[ERROR] [target/generated-sources:unknown]
[ERROR] [target/javadoc-bundle-options:unknown]
[ERROR] [target/maven-archiver:unknown]
[ERROR] [target/test-classes:unknown]
[ERROR] - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.



What's the problem?

Thanks.

--
You received this message because you are subscribed to the Google
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-users+unsubscr...@googlegroups.com
mailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups Jenkins 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Experiences with automatically creating/configuring Jenkins jobs from command line

2014-05-12 Thread Christoph Kutzinski

Hi all,



we want to create a project template to make it easier to create new services from scratch.

As part of this template we want to have a single step to create a new Jenkins job for this service.

For example, this should be a simple Gradle call: gradle createJenkinsJob which would create a new Job and configure it to some defaults -

e.g. e-mail notification settings, Checkstyle/FindBugs/Warnings report.

Additionally, It would be good to be able to create a build pipeline - e.g. compile/test - integration test - deploy - release



Does anyone have experiences with this and can provide some tips?

What Ive found so far:



- Job-DSL-Plugin:https://github.com/jenkinsci/job-dsl-plugin

Looks very nice for configuring jobs. Could be combined withhttps://github.com/ghale/gradle-jenkins-plugin/



- Literate plugin:https://github.com/jenkinsci/literate-plugin

Looks also very nice. I like especially the fact that the Build steps are defined in Markdown with additional comments allowed.

However, it doesnt seem to cover the automatically create job part. Youd still have to create the job once manually in the Jenkins GUI right?





thanks

Kutzi









-- 
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: A question about Subversion Plugin 2.3

2014-05-02 Thread Christoph Kutzinski


Hi,

no JENKINS-18574 has nothing to do with credentials. It's only changelog 
related AFAIK.

JENKINS-18574 wasn't even mentioned in the changelog of 2.0.

Am 02.05.2014 09:25, schrieb David Aldrich:

Hi

I see that Subversion Plugin 2.3 was released yesterday.  The change log
states:

*Note:*Version 2.0 contained a fix for issue #18574
http://issues.jenkins-ci.org/browse/JENKINS-18574. However, the fix
caused 2 regressions, so it was reverted in this version

Now, I know that from version 2.0 it was necessary to specify
'additional credentials' for svn externals.  So I am wondering whether
the fix that has been reverted was related to that new restriction. I.e.
with 2.3 is it still necessary to specify 'additional credentials' for
all svn externals, even if the credentials for the external are the same
as for the main project?

Best regards

David

--
You received this message because you are subscribed to the Google
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-users+unsubscr...@googlegroups.com
mailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups Jenkins 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: NullPointerException after minor dependency change to a pom.xml file

2013-12-08 Thread Christoph Kutzinski


Looks like a bug in the Maven Info Plugin.
Can you open a new JIRA issue for this with a description on how to 
reproduce it?


Am 08.12.2013 04:58, schrieb Stephane Odul:
I managed to get out of the issue by cleaning up my pom.xml. It seems 
that Jenkins is a little more sensitive about the pom files. In our 
case here it had to do with dependency versions and/or typos in the 
custom properties.


On Friday, December 6, 2013 9:49:04 PM UTC-8, Stephane Odul wrote:

00:00:02.778 ERROR: Processing failed due to a bug in the code.
Please report this to jenkinsci-users@googlegroups.com
mailto:jenkinsci-users@googlegroups.com
00:00:02.780 java.lang.NullPointerException
00:00:02.780 at

jenkins.plugins.maveninfo.extractor.properties.PomPropertiesFinder.findProperties(PomPropertiesFinder.java:38)
00:00:02.780 at

jenkins.plugins.maveninfo.extractor.MavenInfoExtractor.extract(MavenInfoExtractor.java:58)
00:00:02.780 at

jenkins.plugins.maveninfo.extractor.MavenInfoEnvironment.tearDown(MavenInfoEnvironment.java:42)
00:00:02.780 at

hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:852)
00:00:02.780 at

hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566)
00:00:02.780 at hudson.model.Run.execute(Run.java:1677)
00:00:02.780 at
hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509)
00:00:02.780 at
hudson.model.ResourceController.execute(ResourceController.java:88)
00:00:02.780 at hudson.model.Executor.run(Executor.java:231)
00:00:02.780
project=hudson.maven.MavenModuleSet@4c7b39a1[build-realtimedlp-trunk]
00:00:02.781

project.getModules()=[hudson.maven.MavenModule@11b9981a[build-realtimedlp-trunk/com.shn.dlp:realtimedlp][build-realtimedlp-trunk/com.shn.dlp:realtimedlp][relativePath:]]
00:00:02.781

project.getRootModule()=hudson.maven.MavenModule@11b9981a[build-realtimedlp-trunk/com.shn.dlp:realtimedlp][build-realtimedlp-trunk/com.shn.dlp:realtimedlp][relativePath:]
00:00:02.781 FATAL: null
00:00:02.781 java.lang.NullPointerException
00:00:02.781 at

jenkins.plugins.maveninfo.extractor.properties.PomPropertiesFinder.findProperties(PomPropertiesFinder.java:38)
00:00:02.781 at

jenkins.plugins.maveninfo.extractor.MavenInfoExtractor.extract(MavenInfoExtractor.java:58)
00:00:02.781 at

jenkins.plugins.maveninfo.extractor.MavenInfoEnvironment.tearDown(MavenInfoEnvironment.java:42)
00:00:02.781 at

hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:852)

Happened with 1.542 so I rolledback to 1.538 and I still get the
issue. Rolling back the change gets me a working build again. The
change is simply to change an internal dependency from an old
release (0.4.1) to a newer 0.5.0-SNAPSHOT version. This is a
trivial change, yet triggers the null pointer exception.

--
You received this message because you are subscribed to the Google 
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.


--
You received this message because you are subscribed to the Google Groups Jenkins 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Maven Dependency Update trigger not working for version ranges

2013-11-15 Thread Christoph Kutzinski


Do you have a test case to reproduce it?
Maven version ranges should be supported since Jenkins 1.481

(see https://issues.jenkins-ci.org/browse/JENKINS-12735)


Am 15.11.2013 12:18, schrieb Bacon, Keith:

Does anyone else wish this would work for version ranges?
Is there a good reason why it doesn’t or can’t?
Thanks,
Keith

--
You received this message because you are subscribed to the Google
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


--
You received this message because you are subscribed to the Google Groups Jenkins 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Aw: Re: jenkins maven project executes maven deploy even when tests fail

2013-11-06 Thread Christoph Kutzinski

No, its much simpler IMO.

The Maven job type always sets maven.test.failure.ignore to true (http://maven.apache.org/maven-1.x/plugins/test/properties.html),

so the build can run to the end and Jenkins can record the test results and set the build result to UNSTABLE -instead of FAILURE which would happen ifmaven.test.failure.ignore wouldnt be set.

Workarounds:

- setmaven.test.failure.ignore explicitely to false. AFAIK Jenkins should detect this and not override it

- use the deploy option of jenkins to deploy the artifact instead of using the deploy goals - though Ive experienced to not being very stable in the past, but that was some years ago.

Gesendet:Mittwoch, 06. November 2013 um 12:22 Uhr
Von:Stephen Connolly stephen.alan.conno...@gmail.com
An:jenkinsci-users@googlegroups.com jenkinsci-users@googlegroups.com
Betreff:Re: jenkins maven project executes maven deploy even when tests fail

http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html

I am willing to bet that it is the Maven Job types evil hooks that are causing your issues... I believe there is some turd polishing hack on top of a hack that lets the Maven job type intercept the deploy and then do it all at the end...

On 6 November 2013 07:02, David Gang michaelg...@gmail.com wrote:

Hi all,

When i run maven deploy with eclipse and the tests fail, it does not continue to deploy.
When a run the same project through jenkins with the target deploy, it continues to deploy.
How can i prevent it from happening?

Thanks,
David

Aw: Re: Re: jenkins maven project executes maven deploy even when tests fail

2013-11-06 Thread Christoph Kutzinski

As part of the Maven goals and options:

-Dmaven.test.failure.ignore=false

Gesendet:Mittwoch, 06. November 2013 um 15:19 Uhr
Von:David Gang michaelg...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Re: Re: jenkins maven project executes maven deploy even when tests fail

Hi,

I wanted to try the first option of setting maven.test.failure.ignore=false.
Where can i set this option?
I looked through the configure system page and did not find a place where to edit it.

Thanks,
David

On Wednesday, November 6, 2013 2:17:57 PM UTC+2, kutzi wrote:

No, its much simpler IMO.

The Maven job type always sets maven.test.failure.ignore to true (http://maven.apache.org/maven-1.x/plugins/test/properties.html),

so the build can run to the end and Jenkins can record the test results and set the build result to UNSTABLE -instead of FAILURE which would happen ifmaven.test.failure.ignore wouldnt be set.

Workarounds:

- setmaven.test.failure.ignore explicitely to false. AFAIK Jenkins should detect this and not override it

- use the deploy option of jenkins to deploy the artifact instead of using the deploy goals - though Ive experienced to not being very stable in the past, but that was some years ago.

http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html

On 6 November 2013 07:02, David Gang wrote:

Hi all,

Thanks,
David

Aw: build failed due to bug in code

2013-11-01 Thread Christoph Kutzinski


What is your Jenkins and your maven-plugin versions?



From the error it looks like theres a problem with the configured maven installation to use for this job (Maven home seems to be empty).

Can you check that configuration?



Gesendet:Freitag, 01. November 2013 um 15:10 Uhr
Von:William Pughe willpu...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:build failed due to bug in code


A Jenkins build of code that builds from the command line and in other Jenkins instances produced:

Checking out Revision 3f7b2aebae0b87940b806423bb5d55e634e93a3b (origin/master)
First time build. Skipping changelog.
ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com
java.lang.NullPointerException
	at java.io.File.init(File.java:277)
	at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58)
	at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41)
	at hudson.FilePath.act(FilePath.java:1004)
	at hudson.maven.MavenModuleSetBuildMavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605)
	at hudson.model.AbstractBuildAbstractBuildExecution.run(AbstractBuild.java:562)
	at hudson.model.Run.execute(Run.java:1665)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:230)
project=hudson.maven.MavenModuleSet@66f11134[first]
project.getModules()=[]
project.getRootModule()=null
FATAL: null
java.lang.NullPointerException
	at java.io.File.init(File.java:277)
	at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58)
	at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41)
	at hudson.FilePath.act(FilePath.java:1004)
	at hudson.maven.MavenModuleSetBuildMavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605)
	at hudson.model.AbstractBuildAbstractBuildExecution.run(AbstractBuild.java:562)
	at hudson.model.Run.execute(Run.java:1665)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:230)



--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.






-- 
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Aw: Re: build failed due to bug in code

2013-11-01 Thread Christoph Kutzinski

Nice :)

Could you create a JIRA issue for this, so we can produce a better error message the next time someone hits this problem?

Gesendet:Freitag, 01. November 2013 um 16:53 Uhr
Von:William Pughe willpu...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Re: build failed due to bug in code

That was it, empty maven_home. All set now, thanks for the help.

On Fri, Nov 1, 2013 at 11:46 AM, Christoph Kutzinski ku...@gmx.de wrote:

What is your Jenkins and your maven-plugin versions?

From the error it looks like theres a problem with the configured maven installation to use for this job (Maven home seems to be empty).

Can you check that configuration?

Gesendet:Freitag, 01. November 2013 um 15:10 Uhr
Von:William Pughe willpu...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:build failed due to bug in code

A Jenkins build of code that builds from the command line and in other Jenkins instances produced:

Checking out Revision 3f7b2aebae0b87940b806423bb5d55e634e93a3b (origin/master)
First time build. Skipping changelog.
ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com

java.lang.NullPointerException at java.io.File.init(File.java:277) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) at hudson.FilePath.act(FilePath.java:1004) at hudson.maven.MavenModuleSetBuildMavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) at hudson.model.AbstractBuildAbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1665) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) project=hudson.maven.MavenModuleSet@66f11134[first] project.getModules()=[] project.getRootModule()=null FATAL: null java.lang.NullPointerException at java.io.File.init(File.java:277) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) at hudson.FilePath.act(FilePath.java:1004) at hudson.maven.MavenModuleSetBuildMavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) at hudson.model.AbstractBuildAbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1665) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230)

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/2711nDJxK6A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Aw: Re: Re: build failed due to bug in code

2013-11-01 Thread Christoph Kutzinski

maven2

Gesendet:Freitag, 01. November 2013 um 17:24 Uhr
Von:William Pughe willpu...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Re: Re: build failed due to bug in code

Sure, what component would this be for?

On Fri, Nov 1, 2013 at 12:08 PM, Christoph Kutzinski ku...@gmx.de wrote:

Nice :)

Could you create a JIRA issue for this, so we can produce a better error message the next time someone hits this problem?

Gesendet:Freitag, 01. November 2013 um 16:53 Uhr

Von:William Pughe willpu...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Re: build failed due to bug in code

That was it, empty maven_home. All set now, thanks for the help.

On Fri, Nov 1, 2013 at 11:46 AM, Christoph Kutzinski ku...@gmx.de wrote:

What is your Jenkins and your maven-plugin versions?

From the error it looks like theres a problem with the configured maven installation to use for this job (Maven home seems to be empty).

Can you check that configuration?

Gesendet:Freitag, 01. November 2013 um 15:10 Uhr
Von:William Pughe willpu...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:build failed due to bug in code

A Jenkins build of code that builds from the command line and in other Jenkins instances produced:

For more options, visit https://groups.google.com/groups/opt_out.

Re: Jenkins Maven NPE

2013-10-23 Thread Christoph Kutzinski


 JVM: Oracle Zero VM 21.0-b17
What kind of VM is that? I've never heard of it.

From the stacktrace it looks like you're trying to run the Maven build 
with a Java 5 VM (which is not supported). So you might want to try it 
with a Java 6 or 7 VM.


Anyway, the NullPointerException shouldn't happen. Could you please open 
a JIRA issue for that?


Am 23.10.2013 21:12, schrieb Christian Beikov:
It seems that jenkins is not able to parse my pom.xml or maybe it is 
something different?

Please Help!

My System:

OS: Darwin 9.8.0
JVM: Oracle Zero VM 21.0-b17
AS: JBoss EAP 6.1
Jenkins: 1.535
Maven: 3.1.1
Maven-Plugin: 2.0

Console Output:
Parsing POMs
[Booking] $ java -cp 
/Users/jboss/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.4.jar:/Users/jboss/.jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1/boot/plexus-classworlds-2.5.1.jar:/Users/jboss/.jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1/conf/logging
 jenkins.maven3.agent.Maven31Main 
/Users/jboss/.jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1 
/Library/JBossAS/current/standalone/tmp/vfs/tempad4550f3c74303/jenkins.war-9212d6c4d4b41483/WEB-INF/lib/remoting-2.32.jar
 
/Users/jboss/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.4.jar
 
/Users/jboss/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar
 49293
===[JENKINS REMOTING CAPACITY]===channel started
ERROR: Processing failed due to a bug in the code. Please report this 
tojenkinsci-us...@googlegroups.com
java.lang.NullPointerException
  http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException  
athudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:261)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.AbstractMavenProcessFactory.newProcessentity=method
athudson.maven.ProcessCache.get(ProcessCache.java:235)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.ProcessCache.getentity=method

athudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:739)
  
http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRunentity=method
athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method
athudson.model.Run.execute(Run.java:1665)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method
athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.runentity=method
athudson.model.ResourceController.execute(ResourceController.java:88)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=method
athudson.model.Executor.run(Executor.java:246)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method
project=hudson.maven.MavenModuleSet@156ffe7[Booking]
project.getModules()=[hudson.maven.MavenModule@1c92bb[Booking/at.ac.tuwien.sse:sse-agile-1][Booking/at.ac.tuwien.sse:sse-agile-1][relativePath:]]
project.getRootModule()=hudson.maven.MavenModule@1c92bb[Booking/at.ac.tuwien.sse:sse-agile-1][Booking/at.ac.tuwien.sse:sse-agile-1][relativePath:]
FATAL: null
java.lang.NullPointerException
  http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException  
athudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:261)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.AbstractMavenProcessFactory.newProcessentity=method
athudson.maven.ProcessCache.get(ProcessCache.java:235)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.ProcessCache.getentity=method

athudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:739)
  
http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRunentity=method
athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method
athudson.model.Run.execute(Run.java:1665)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method
athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.runentity=method
athudson.model.ResourceController.execute(ResourceController.java:88)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=method
athudson.model.Executor.run(Executor.java:246)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method

--

Aw: Console output in LTS 1.509.4

2013-10-15 Thread Christoph Kutzinski

Harald, seehttps://issues.jenkins-ci.org/browse/JENKINS-19396andhttps://issues.jenkins-ci.org/browse/JENKINS-19352



Gesendet:Dienstag, 15. Oktober 2013 um 11:22 Uhr
Von:Harald Wellmann hwellmann...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Console output in LTS 1.509.4


After upgrading from 1.509.3 to 1.509.4, my console output looks somewhat broken.

Mojo execution headlines are no longer emphasized in bold, and theres a lot of messages of the following kind:

Oct 15, 2013 11:11:59 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:


Looks like a regression to me, or is it just a configuration issue?

Best regards,
Harald




--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.






-- 
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Aw: Re: Console output in LTS 1.509.4

2013-10-15 Thread Christoph Kutzinski

Its fixed on trunk - at least for Java 7, but no release of the maven-plugin has been made, yet.

Gesendet:Dienstag, 15. Oktober 2013 um 11:45 Uhr
Von:Harald Wellmann hwellmann...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Re: Console output in LTS 1.509.4

Hmm, the impact on LTS is not clear to me. Does this mean the issue *is* a bug which is fixed (at least for Java 7) on trunk but still present in LTS?

Cheers,
Harald

2013/10/15 Christoph Kutzinski ku...@gmx.de

Harald, seehttps://issues.jenkins-ci.org/browse/JENKINS-19396andhttps://issues.jenkins-ci.org/browse/JENKINS-19352

Gesendet:Dienstag, 15. Oktober 2013 um 11:22 Uhr
Von:Harald Wellmann hwellmann...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Console output in LTS 1.509.4

After upgrading from 1.509.3 to 1.509.4, my console output looks somewhat broken.

Mojo execution headlines are no longer emphasized in bold, and theres a lot of messages of the following kind:

Oct 15, 2013 11:11:59 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO:

Looks like a regression to me, or is it just a configuration issue?

Best regards,
Harald

Aw: gradle sonar-runner fails on Jenkins

2013-09-02 Thread Christoph Kutzinski

For reference:

the problem turned out that the project name on Jenkins contained a whitespace while the directory on my developer machine didnt

Since Gradle automatically takes that as project.name and the sonarRunner obviously doesnt like white space in the project name, it failed on Jenkins.

Solution: change the Jenkins project name and/or explicitly set the project.name in Gradle (which sounds like a good idea, anyway)

Gesendet:Montag, 26. August 2013 um 14:05 Uhr
Von:Christoph Kutzinski ku...@gmx.de
An:Jenkins Users jenkinsci-users@googlegroups.com
Betreff:gradle sonar-runner fails on Jenkins

Hi,

Ive got the problem that the sonar task fails when running from Jenkins, but suceeds when running on a developer machine or even on the Jenkins build node when running from the shell.

Console output:

11:53:28 :sonarRunner
11:53:28 11:53:28.124 INFO .s.b.b.BatchSettings - Load batch settings
11:53:28 :sonarRunner FAILED
11:53:28
11:53:28 FAILURE: Build failed with an exception.
11:53:28
11:53:28 * What went wrong:
11:53:28 Execution failed for task :sonarRunner.
11:53:28 java.lang.IllegalArgumentException: Illegal character in query at index 95: http://xyz:9000/batch_bootstrap/properties?project=com.example:LIS sonar
11:53:28
11:53:28 * Try:
11:53:28 Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Relevant part of build.gradle:

sonarRunner {
sonarProperties {
property sonar.host.url, http://xyz:9000/
property sonar.jdbc.url, jdbc:postgresql://xyz/sonar
property sonar.jdbc.driverClassName, org.postgresql.Driver
property sonar.jdbc.username, sonar
property sonar.jdbc.password, sonar01
property suppressions-file-location, {projectDir}/config/checkstyle/suppressions.xml
}
}

The problem seems to me the whitespace between LIS and sonar, but Ive got no idea why the escaping works when running from the shell but not from within Jenkins.

Can anyone help?

Thanks

Christoph

gradle sonar-runner fails on Jenkins

2013-08-26 Thread Christoph Kutzinski

Hi,

Ive got the problem that the sonar task fails when running from Jenkins, but suceeds when running on a developer machine or even on the Jenkins build node when running from the shell.

Console output:

Relevant part of build.gradle:

The problem seems to me the whitespace between LIS and sonar, but Ive got no idea why the escaping works when running from the shell but not from within Jenkins.

Can anyone help?

Thanks

Christoph

Aw: Re: Jenkins isn't accessible due to several errors

2013-07-12 Thread Christoph Kutzinski

Which JVMs are you using for Master and Slave? The error is a serialisation incompatibility between these two.


Gesendet:Freitag, 12. Juli 2013 um 16:18 Uhr
Von:Mehdi Hayani hayani.mehdi...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Re: Jenkins isnt accessible due to several errors


Okk thanks, Ill check.


meanwhile, you have any idea why I Get this warning ??





WARNING: Failed to monitor ASLAVE-1 for Free Swap Space

java.io.InvalidClassException: hudson.node_monitors.SwapSpaceMonitorMonitorTask; local class incompatible: stream classdesc serialVersionUID = 1, local class serialVersionUID = 1184166703664094906

at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:617)

at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620)

at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515)

at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769)

at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348)

at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)

at hudson.remoting.UserRequest.deserialize(UserRequest.java:182)

at hudson.remoting.UserRequest.perform(UserRequest.java:98)

at hudson.remoting.UserRequest.perform(UserRequest.java:48)

at hudson.remoting.Request2.run(Request.java:326)

at hudson.remoting.InterceptingExecutorService1.call(InterceptingExecutorService.java:72)

at java.util.concurrent.FutureTaskSync.innerRun(FutureTask.java:334)

at java.util.concurrent.FutureTask.run(FutureTask.java:166)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at java.util.concurrent.ThreadPoolExecutorWorker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:724)

Jul 12, 2013 10:15:48 AM hudson.triggers.SCMTriggerRunner run







--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.








-- 
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Aw: Definitive Windows SVN notification guide?

2013-06-26 Thread Christoph Kutzinski

Theres no other documentation (Im aware of) than the one on the Wiki page and - if you like to stick your nose into it - in the GutHub sources (esp.https://github.com/jenkinsci/subversion-plugin/blob/master/src/main/java/hudson/scm/SubversionRepositoryStatus.java)

If you find that the documentation is missing something or is outright wrong, please feel free to change the Wiki page. If youre not comfortable with that, please at least open a JIRA issue describing whats wrong with it.

BTW: the rev query parameter is there to tell Jenkins to check out exactly this revision instead of the revision at the time when the build starts

Gesendet:Mittwoch, 26. Juni 2013 um 13:03 Uhr
Von:Yves Goergen yves.goer...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Definitive Windows SVN notification guide?

I would like to set up the Subversion commit notification for the Jenkins server. Were all Windows here, so the bash scripts are not usable in this case. I tried in several different ways but either nothing happened or I got an HTTP 500 response with no further details except a stack trace. The documentation (https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin) only shows some example scripts (which do not work) with sparse notes about exceptions and alternatives. But nowhere is explained what the URL consists of, what URL parameters are available, used for what, and required. Also the data to post is not explained anywhere. Ive seen the revision number and the commit message put in there, but neither should be necessary because Jenkins will fetch that revision from the repository anyway.

So is there a definitive guide how to get it working, all on the Windows platform? Preferable with a PowerShell script. Otherwise I must consider this broken undocumented and stick with the time schedule instead.

Aw: RE: Update to strange Jenkins version number?

2013-06-18 Thread Christoph Kutzinski

I guess Jesse has something to do with it ;-)


Gesendet:Dienstag, 18. Juni 2013 um 10:59 Uhr
Von:James Nord (jnord) jn...@cisco.com
An:jenkinsci-users@googlegroups.com jenkinsci-users@googlegroups.com
Cc:matthew.web...@diamond.ac.uk matthew.web...@diamond.ac.uk
Betreff:RE: Update to strange Jenkins version number?




It is 1.518 with a potential fix for Jenkins-14362[1] added for testing.



More info is in the bug  possibly shouldnt be in the update site but I will leave that for someone else to comment on.



/James



[1] https://issues.jenkins-ci.org/browse/JENKINS-14362






From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Louis Roch
Sent: 18 June 2013 08:48
To: jenkinsci-users@googlegroups.com
Cc: matthew.web...@diamond.ac.uk
Subject: Re: Update to strange Jenkins version number?





Same problem here.

On Tuesday, June 18, 2013 9:43:32 AM UTC+2,  matthew...@diamond.ac.uk wrote:

My Jenkins release, currently 1.518, is telling me:
-- New version of Jenkins (1.518.JENKINS-14362-jzlib) is available for download

Does anyone know what this is about?  http://jenkins-ci.org/changelog tells me that that is the latest release number, but I could find no other reference to it anywhere. Is this an official release?

Thanks
Matthew


--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom




--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.






--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.









-- 
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: javac compiler errors

2013-06-12 Thread Christoph Kutzinski

I think it would be very helpful to have this as part of Jenkins core.

Christoph



Ulli Hafner ullrich.haf...@gmail.com schrieb:

Wouldn't it be better if Jenkins would already provide a feature to
visualize compile errors? (And plug-ins can add new patterns for new
compiler types?) 

I can add such a feature in the warnings plug-in, however I think it
would make more sense to have that part in Jenkins core… Currently my
plug-in shows only warnings. 

What do others think? How could we improve compiler error
visualization?  

Ulli

Am 11.06.2013 um 22:44 schrieb Kevin Fleming (BLOOMBERG/ 731 LEXIN)
kpflem...@bloomberg.net:

 Ahh, well, it would take a bit of configuration. The Warnings plugin
allows you to define your own patterns to be used to capture content
from the job output, so you could take the existing patterns for javac
and extend them to capture errors as well.
 
 One note, though: it only captures one line of each warning, not the
whole thing (including any context the compiler may output, although
javac generally does a terrible job of that). The person reviewing the
problems will end up going back to the console output anyway to get the
remaining details.
 
 - Original Message -
 From: jenkinsci-users@googlegroups.com
 To: jenkinsci-users@googlegroups.com
 Cc: Kevin Fleming (BLOOMBERG/ 731 LEXIN)
 At: Jun 11 2013 16:39:53
 How? I've had a short email conversation with the warnings plugin
maintainer, Ulli Hafner, and he said it only does warnings: For javac,
only warnings are shown since errors are already flagged by Jenkins as
compile errors. Thank you,
 
 Alex
 
 
 On Tuesday, June 11, 2013 3:29:03 PM UTC-5, Kevin Fleming wrote:
 The Warnings plugin can be used to harvest compiler warning and error
messages and display them in a dedicated area of the build results
page.
 
 - Original Message -
 From: jenkins...@googlegroups.com
 To: jenkins...@googlegroups.com
 At: Jun 11 2013 16:27:56
 Is there anyway to have jenkins report javac compiler errors on the
project page or the build results page? It seems odd that one needs to
drill down into the Console Output to see what went wrong during the
build process.
 
 Alex
 
 -- 
 You received this message because you are subscribed to the Google
Groups Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-use...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  
 
 -- 
 You received this message because you are subscribed to the Google
Groups Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  
 
 -- 
 You received this message because you are subscribed to the Google
Groups Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  

-- 
You received this message because you are subscribed to the Google
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Aw: Wiki down ?

2013-05-31 Thread Christoph Kutzinski

Works for me


Gesendet:Freitag, 31. Mai 2013 um 16:28 Uhr
Von:mpapo - Michal Pailloncy mpapo@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Wiki down ?


Hi,



The wiki seems to be down : https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API=502 Bad Gateway





Michal


--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.








-- 
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Aw: RE: Maven-release-plugin pushing snapshots instead of releases

2013-05-29 Thread Christoph Kutzinski


Are you using git?

Theres a bug in the maven-release-plugin with localized git output:

http://www.shredzone.de/cilla/page/373/maven-release-plugin-and-git-fix.html



Gesendet:Mittwoch, 29. Mai 2013 um 13:09 Uhr
Von:James Nord (jnord) jn...@cisco.com
An:jenkinsci-users@googlegroups.com jenkinsci-users@googlegroups.com
Betreff:RE: Maven-release-plugin pushing snapshots instead of releases




Hi Brett,



There are several ways that Jenkins publishes things (post deploy, or as part of the build).

Can you be more exact about what is happening and what you think is wrong (also how are you triggering the release?)



Regards,



/James








From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Brett Delle Grazie
Sent: 29 May 2013 12:00
To: jenkinsci-users@googlegroups.com
Subject: Maven-release-plugin pushing snapshots instead of releases






Hi,






Weve got an odd situation with Jenkins 1.509.1 LTS and latest plugins including maven2 release.







When triggering a release build, Jenkins is publishing a SNAPSHOT build instead of the release build configured.







Has anyone come across this before?






Thanks,







Brett


--
Best Regards,

Brett Delle Grazie



--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.






--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.









-- 
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Aw: Mark Build Unstable if it takes to long

2013-05-02 Thread Christoph Kutzinski

Check the build timeout plugin


Gesendet:Donnerstag, 02. Mai 2013 um 17:20 Uhr
Von:Tom tpri...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Mark Build Unstable if it takes to long

Hello,

Does anyone know how to mark a build unstable if it takes to long?

Thanks
-Tom


--
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.








-- 
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Fingerprint system understanding

2013-04-11 Thread Christoph Kutzinski


I think you're referring to the changes I had done some time ago.
Previously (before my changes) the relationship was built up to a 
'non-predictable' job (means the assigment was stable, but not really 
deducable from parameters which are visible from the outside - i.e. only 
based on a hashcode)


Now it is based on the following rules:
- jobs who 'deploy' artifacts come 1st
- jobs who 'install' artifacts come 2nd
- all others come 3rd

if there is no clear winner based on that, the alphabetical 1st job wins

If think (hope) that I have documented that somewhere in the online 
help. If not, please kick me, so I do it.


cheers
Christoph

Am 11.04.2013 17:51, schrieb Jesse Farinacci:

Greetings,

I have experienced the same problem. Where the last job through the
system greedily becomes the parent for all jobs which utilize the same
Maven projects. This breaks otherwise correct parent/child fingerprint
linkage, where upstream projects being built will not trigger
downstreams because the downstreams parent is now the @nighly job which
only ever runs once. It's a big pain, and as far as I can remember, was
introduced a few LTS ago.

-Jesse


On Thu, Apr 11, 2013 at 11:43 AM, Jonathan Piron
jonathanpi...@gmail.com mailto:jonathanpi...@gmail.com wrote:

Hi,

I'm trying to understand how fingerprint system works. I understand
the purpose but not how it works.
I have 2 maven jobs for the same project (let's say TOP) : one daily
and one nightly.
The same goes for a BOTTOM project : one daily and one nightly job.

Currently the nightly BOTTOM and the daily TOP are linked with the
fingerprint system. Once a nightly BOTTOM build finished, it
triggers the daily TOP.

I'd like the daily BOTTOM to be linked to the daily TOP and the
nightly BOTTOM to be linked to the nightly TOP.

Is there a way to achieve this ?

Thanks for your help,


--
You received this message because you are subscribed to the Google
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-users+unsubscr...@googlegroups.com
mailto:jenkinsci-users%2bunsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.





--
There are 10 types of people in this world, those
that can read binary and those that can not.

--
You received this message because you are subscribed to the Google
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




--
You received this message because you are subscribed to the Google Groups Jenkins 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: JBOSS Management Plugin

2013-03-04 Thread Christoph Kutzinski


Hi,

sorry that you didn't get any response so far.
Unfortunately I'm not familiar with the JBoss management plugin, but 
usually you find the configuration for plugins either in the global 
management section (manage Jenkins) or in the jobs' configuration page. 
Have you looked there already?


hope that helps,
Christoph

Am 04.03.2013 12:50, schrieb Aswini Rajasekaran:

Hi friends,

I have posted many threads in this forum, but haven't got reply for 
any. Hoping to get a reply for this thread atleast.


I am trying to start JBOSS server for running the unit tests through 
Jenkins. Can anyone tell me how to use the JBOSS Management Plugin to 
start the JBOSS Server? How will I specify the jboss server instance 
and the port of the jboss instance?


Thanks a mil in advance.
Aswini
--
You received this message because you are subscribed to the Google 
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.




--
You received this message because you are subscribed to the Google Groups Jenkins 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Copy Existing Job throws stacktrace

2013-02-08 Thread Christoph Kutzinski

That's a bug in Jenkins core: 
https://issues.jenkins-ci.org/browse/JENKINS-16499


You'll have to wait for Jenkins 1.501 (I wonder why it's not released 
yet) or downgrade.


Am 08.02.2013 16:21, schrieb David Hoffman:

I have also gone ahead and upgraded the Mercurial plugin to 1.43 with no
joy -  Error still happens.

--
You received this message because you are subscribed to the Google
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




--
You received this message because you are subscribed to the Google Groups Jenkins 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Aw: Test results disappeared since upgrade to 1.500

2013-02-07 Thread Christoph Kutzinski

Could behttps://issues.jenkins-ci.org/browse/JENKINS-16573Do you see any error messages?

Gesendet:Donnerstag, 07. Februar 2013 um 15:34 Uhr
Von:Guillaume Bilodeau guillaume.bilod...@gmail.com
An:jenkinsci-users@googlegroups.com

Betreff:Test results disappeared since upgrade to 1.500

Hi all,Weve been running Jenkins happily since a year now. One of our jobs runs a Maven build that in turn executes a series of Selenium-based acceptance tests through its FailSafe plugin. Until version 1.500, test reports have been displayed on the individual build page, with the ability to drill down to individual test results. Somehow since upgrading to 1.500 these test reports have disappeared from the build page. Also, hovering over the job weather icon on the main dashboard used to show test stability; it doesnt anymore.I have verified that the tests are still executed and that the job workspace still contains the FailSafe reports. Something else is amiss.Any ideas?Thanks!GB

Checkstyle/FindBugs plugin: warning summary gone after update?

2013-01-29 Thread Christoph Kutzinski

Hi,weve recently updated our Checkstyle and FindBugs plugin (and also static analysis core) to the latest version and since then weve mentioned that the warning summary on the build overview page has gone.Im not sure, if this is a bug or were missing some configuration which we have to do to get it back.Note that we didnt update the compiler warnings plugin and we still can see the compiler warnings summary!cheersChristoph



-- 
You received this message because you are subscribed to the Google Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Aw: Re: Checkstyle/FindBugs plugin: warning summary gone after update?

2013-01-29 Thread Christoph Kutzinski

Hi Ulli,Im not sure if I can find out which version we did upgrade from, but Ill try. Our Warnings plugin is currently at3.26, so the FB and CS plugins were probably around the same age.I cannot see any errors in neither logfile nor console.BTW: the FB and CS links in the navigation are still and there and the warning details view also still works. Also the trend graphs on the projects page are still there.Its just the summary which is gone.cheersChristoph

Gesendet:Dienstag, 29. Januar 2013 um 10:38 Uhr
Von:Ulli Hafner ullrich.haf...@gmail.com
An:jenkinsci-users@googlegroups.com

Betreff:Re: Checkstyle/FindBugs plugin: warning summary gone after update?

Hi Christoph,I havent changed the plug-ins for quite a while now From which versions did you upgrade? What Jenkins version are you using? Are the missing summaries in maven or freestyle jobs? Are there any exceptions on the console? (Or messages that Jenkins cannot assign some values from XML to the actual objects?)UlliAm 29.01.2013 um 10:28 schrieb Christoph Kutzinski ku...@gmx.de:Hi,weve recently updated our Checkstyle and FindBugs plugin (and also static analysis core) to the latest version and since then weve mentioned that the warning summary on the build overview page has gone.Im not sure, if this is a bug or were missing some configuration which we have to do to get it back.Note that we didnt update the compiler warnings plugin and we still can see the compiler warnings summary!cheersChristoph

Aw: Re: Checkstyle/FindBugs plugin: warning summary gone after update?

2013-01-29 Thread Christoph Kutzinski

These are the version changes we did:analysis-core 1.37-1.48findbugs 4.33-4.45checkstyle 3.23 - 3.32Jenkins version is 1.480.2The affected jobs are Maven jobs.

Gesendet:Dienstag, 29. Januar 2013 um 10:51 Uhr
Von:Christoph Kutzinski ku...@gmx.de
An:jenkinsci-users@googlegroups.com

Betreff:Aw: Re: Checkstyle/FindBugs plugin: warning summary gone after update?

Gesendet:Dienstag, 29. Januar 2013 um 10:38 Uhr
Von:Ulli Hafner ullrich.haf...@gmail.com
An:jenkinsci-users@googlegroups.com

Betreff:Re: Checkstyle/FindBugs plugin: warning summary gone after update?

Aw: Re: Checkstyle/FindBugs plugin: warning summary gone after update?

2013-01-29 Thread Christoph Kutzinski

No, it neither shows for old nor for new builds.Christoph

Gesendet:Dienstag, 29. Januar 2013 um 11:26 Uhr
Von:Ulli Hafner ullrich.haf...@gmail.com
An:jenkinsci-users@googlegroups.com

Betreff:Re: Checkstyle/FindBugs plugin: warning summary gone after update?

I changed something in 4.34 of findbugs plug-in (show information of build result evaluation). Maybe that change was not backward compatible? Does the information show up for new builds?UlliAm 29.01.2013 um 11:17 schrieb Christoph Kutzinski ku...@gmx.de:These are the version changes we did:analysis-core 1.37-1.48findbugs 4.33-4.45checkstyle 3.23 - 3.32Jenkins version is 1.480.2The affected jobs are Maven jobs.

Gesendet:Dienstag, 29. Januar 2013 um 10:51 Uhr
Von:Christoph Kutzinski ku...@gmx.de
An:jenkinsci-users@googlegroups.com

Betreff:Aw: Re: Checkstyle/FindBugs plugin: warning summary gone after update?

Gesendet:Dienstag, 29. Januar 2013 um 10:38 Uhr
Von:Ulli Hafner ullrich.haf...@gmail.com
An:jenkinsci-users@googlegroups.com

Betreff:Re: Checkstyle/FindBugs plugin: warning summary gone after update?

Aw: Re: Checkstyle/FindBugs plugin: warning summary gone after update?

2013-01-29 Thread Christoph Kutzinski

Great that you can reproduce it.We updated Jenkins and shortly thereafter the plugins. I think the issue only appeared after the plugin update, but not 100% sure anymore.https://issues.jenkins-ci.org/browse/JENKINS-16518thanksChristoph

Gesendet:Dienstag, 29. Januar 2013 um 11:55 Uhr
Von:Ulli Hafner ullrich.haf...@gmail.com
An:jenkinsci-users@googlegroups.com

Betreff:Re: Checkstyle/FindBugs plugin: warning summary gone after update?

I can reproduce the problem now I dont know if something in my plug-ins or in the core maven support has been changed that causes this defect. Did you upgrade Jenkins in parallel? Or did the error appear only after the plug-in updates?The error is located in the maven part of the plug-in, so the warnings plug-in and the freestyle jobs should workCan you please file a bug report?UlliAm 29.01.2013 um 11:30 schrieb Christoph Kutzinski ku...@gmx.de:No, it neither shows for old nor for new builds.Christoph

Gesendet:Dienstag, 29. Januar 2013 um 11:26 Uhr
Von:Ulli Hafner ullrich.haf...@gmail.com
An:jenkinsci-users@googlegroups.com

Betreff:Re: Checkstyle/FindBugs plugin: warning summary gone after update?

Gesendet:Dienstag, 29. Januar 2013 um 10:51 Uhr
Von:Christoph Kutzinski ku...@gmx.de
An:jenkinsci-users@googlegroups.com

Betreff:Aw: Re: Checkstyle/FindBugs plugin: warning summary gone after update?

Gesendet:Dienstag, 29. Januar 2013 um 10:38 Uhr
Von:Ulli Hafner ullrich.haf...@gmail.com
An:jenkinsci-users@googlegroups.com

Betreff:Re: Checkstyle/FindBugs plugin: warning summary gone after update?

--
You received this message

Aw: Re: Checkstyle/FindBugs plugin: warning summary gone after update?

2013-01-29 Thread Christoph Kutzinski

1.424.x (1.424.3 or so)

Gesendet:Dienstag, 29. Januar 2013 um 12:18 Uhr
Von:Ulli Hafner ullrich.haf...@gmail.com
An:jenkinsci-users@googlegroups.com

Betreff:Re: Checkstyle/FindBugs plugin: warning summary gone after update?

Which Jenkins version did you upgrade from?UlliAm 29.01.2013 um 12:05 schrieb Christoph Kutzinski ku...@gmx.de:Great that you can reproduce it.We updated Jenkins and shortly thereafter the plugins. I think the issue only appeared after the plugin update, but not 100% sure anymore.https://issues.jenkins-ci.org/browse/JENKINS-16518thanksChristoph