Sonar build is failing : Non-resolvable parent POM: Could not find artifact. a.b.c.pom:1.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 5, column 11 - [Help 2]
plugin a.b.c pom has one error Non-resolvable parent POM: Could not find artifact. a.b.c.pom:1.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 5, column 11 - [Help 2] the plugin a.b.c has a pom where parent poms relative path is given nightly build runs without any problem but sonar buidl fails with error that parnt.relative path points at wrong pom how shall i resolve this problem -- 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: shell execution produces couldn't flush stdout error
Hello, thank you for the suggestion - but I already tried that but it didn't change the behaviour. On Thursday, September 5, 2013 8:52:54 PM UTC+2, John Russell wrote: I find I have much better luck in Execute shell build steps if I put #!/bin/bash at the top. It tends to make the behavior much more consistent. YMMV On Wednesday, September 4, 2013 4:30:04 AM UTC-4, Matthias wrote: Hello, when using pipes in shell scripts I often get the error mentioned in the subject line. To reproduce the issue add an execute shell build step to a new job and run the following: echo replace e by a | sed 's_e_a_g' | echo done This might not make much sense - but it generates the error couldn't flush stdout while this does not happen when executing the same in a terminal. The jenkins console output produces: [EnvInject] - Loading node environment variables. Building on master in workspace /home/jenkins/build-server/jobs/test.sed/workspace [workspace] $ /bin/sh -xe /tmp/hudson7236481234921041257.sh + echo replace e by a + echo done done + sed s_e_a_g sed: couldn't flush stdout: Broken pipe Finished: SUCCESS best regards, Matthias -- 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: How do I stop Jenkins?
+1. kill -9 as a first step is a very very very bad idea. 2013/9/4 Richard Bywater rich...@byh2o.com Personally I wouldn't kill -9 the process straight away as then the process has no chance to clean up after itself... On Thu, Sep 5, 2013 at 12:57 AM, david.doug...@barclays.com wrote: How did you start Jenkins? . . . . Assuming you did something like Java –jar Jenkins.war ** ** From the command line ** ** ps –aef | grep Jenkins.war ** ** identify the process and ** ** Kill -9 process ** ** dD ** ** *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of *Ed Keith *Sent:* 04 September 2013 13:52 *To:* jenkinsci-users@googlegroups.com *Subject:* Re: How do I stop Jenkins? ** ** I do not see jenkins listed in the Activity Monitor, so I can not kill it there. ** ** -EdK On Wednesday, 4 September 2013 08:49:48 UTC-4, Ed Keith wrote: I running on Mac OS X 10.6.8. On Wednesday, 4 September 2013 08:31:02 UTC-4, Ed Keith wrote: I can't figure out how to shut down Jenkins. ** ** Any help would be appreciated. ** ** -EdK -- 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. This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments. Internet communications are not guaranteed to be secure or virus-free. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group. Barclays Bank PLC.Registered in England and Wales (registered no. 1026167). Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom. Barclays Bank PLC is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority (Financial Services Register No. 122702). -- 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. -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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: How to find out WHY a job was executed on a specific slave?
From my experience, and from what I think I've read somewhere (didn't check the code), Jenkins will indeed try to launch the build on the last slave if it's available for obvious reasons. So, I suppose your slave was unavailable or busy (did you double-check the builds that ran on it?) (see in the UI, you can see builds by slave). As for potential unavailability, I don't remember but I suppose something might be logged either in the server logs or in the audit trail (through the UI). My 2 cents. 2013/9/6 Dirk Heinrichs d...@recommind.com Hi, yesterday Jenkins executed two subsequent builds of the same job on different slaves, although the slave which ran the first build was idle when the second build started. Doesn't Jenkins try to execute the next build on the same slave if possible? If yes: How do I find out why this happend? Does Jenkins log this somewhere? Thanks... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Infrastructure *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 1149 *Email*: d...@recommind.com mailto:d...@recommind.com *Skype*: dirk.heinrichs.recommind www.recommind.com http://www.recommind.com http://www.recommind.com -- 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. -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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: Redirect stdout to surefire reports
Not totally sure what you want, but seems more like a maven question than a jenkins one. 2013/9/6 Gaurang shah gaurangns...@gmail.com Hi Guys, In the surefire reports on jenkins when a test case fails it shows both stacktrace and stdout. Is there any way it shows stdout even when test case passes. Gaurang Shah -- 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. -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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: Jenkins Log4j warning
Maven question. Please better post on Maven users mailing list next time.
As for your issue, move your log4j.properties file to src/test/resources.
Cheers
2013/9/6 Gaurang shah gaurangns...@gmail.com
Hi Guy,
I have configured log4j in my project, however the problem is when i run
that in jenkins i get following log4j jenkins. have i missed something in
log4j.properties file or have i misplaced it ??
I am using maven project.
*Error Messages*
log4j:WARN No appenders could be found for logger
(org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
*Location of the log4j.properties - *src\test\java
*log4j.properties:*
# Root logger option
log4j.rootLogger=INFO, stdout
# Direct log messages to stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.Target=System.out
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{-MM-dd HH:mm:ss}
%-5p %c{1}:%L - %m%n
--
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.
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor ! nbsp;!
--
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: Plugin require for BTS
On Friday, September 6, 2013 12:39:54 AM UTC-4, Gaurang shah wrote: Hi Guys, I have my automation project configured on the Jenkins, Now everytime a test case fails management is interested in knowing the reason. Is it a bug in automation ? is it a product bug ? is it a timing or network issue ? In all the above case if necessary bug Id. is there any plugin avaible which serves this puprose I want something like below If this were possible, there'd already be software that could write itself. I'm not sure what your goal is, but mine is to eliminate all test failures which do not indicate a bug in the software being tested. Therefore, when I see a failure which indicates a bug in the test, I attempt to fix the test. I have spent many hours on this, but there are still occasional invalid failures. Unfortunately, I don't think this problem is any more solvable than the problem of bugs in software in general. -- 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: How to find out WHY a job was executed on a specific slave?
Am 08.09.2013 22:02, schrieb Baptiste Mathus: So, I suppose your slave was unavailable or busy (did you double-check the builds that ran on it?) Yes, I did. It was available, but idle for about 2 hours while the second build was started on another slave. Neither the master, nor the slave log have any indication as to why this happened. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Infrastructure *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 1149 *Email*: d...@recommind.com mailto:d...@recommind.com *Skype*: dirk.heinrichs.recommind www.recommind.com http://www.recommind.com http://www.recommind.com -- 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.
