Re: PMD plugin doesn't use pmd.xml
The pmd.xml file exists. It's produced with the binding of check goal during verify phase: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId executions execution idcheck-pmd/id phaseverify/phase goals goalcheck/goal /goals Le jeudi 15 mai 2014 23:24:25 UTC+2, Ullrich Hafner a écrit : The PMD plug-in requires that your build creates the pmd.xml file. I.e., you need to run 'mvn pmd:pmd'. Or how did you produce the pmd.xml file in your build before? Am 15.05.2014 um 16:34 schrieb Jean Pierre Froud jpf...@gmail.comjavascript: : Hi, I'm having a similar issue to this one: PMD plugin doesn't use pmd.xmlhttps://issues.jenkins-ci.org/browse/JENKINS-10820 Unless I explicitly call pmd:pmd, the graph doesn't show. And if I add pmd:pmd, I see in log: Successfully parsed file... and the graph appears. Jenkins ver. 1.544 Static Code Analysis Plug-ins 1.41 -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: mvn release does not work, only publishes SNAPSHOT releases
Hehehe. So there is no hope for fixing this ever? At least, could you be so kind as to describe those neccessary changes that should fix the project layout? Like removing the extra depends/versions? Or separating the Jenkins pom from plugin pom? -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Summary Action on Project page
I got it to produce only one by having getProjectAction return the same instance whenever it is called. On Thursday, May 15, 2014 6:30:04 PM UTC+1, twr wrote: That works perfectly. Thanks. *However, *the only way I've managed to get it to actually add to the page is by overriding getProjectAction on my Notifier (Publisher) and returning a new instance of my action, but for some reason it *gets added twice*? (currently stuck on version 1.509.2 of Jenkins - if that makes a difference) On Thursday, May 15, 2014 6:16:40 PM UTC+1, ogondza wrote: On Thu, 15 May 2014 19:06:28 +0200, twr thomas.w...@gmail.com wrote: I make extensive use of summary actions on builds, but I would like to do something similar on the project page (for a summary of all builds)? Where would I start with this? (best I've managed is links to alternate page via ProminentProjectAction and associated index.jelly - but I would much prefer a summary that appears in the project page itself). Thanks Project actions optionally includes jobMain.jelly[1]. Quite similar to build's summary.jelly. [1] https://github.com/jenkinsci/jenkins/blob/0f7b144fd32544a872075d58300a53b9abcca5f4/core/src/main/resources/hudson/model/AbstractProject/main.jelly#L77-80 HTH -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: PMD plugin doesn't use pmd.xml
I see. This is currently not supported with the maven project type. You need to either switch to a freestyle project or invoke pmd:pmd. I think there is already a similar issue: https://issues.jenkins-ci.org/browse/JENKINS-8650 Am 16.05.2014 um 08:01 schrieb Jean Pierre Froud jpfr...@gmail.com: The pmd.xml file exists. It's produced with the binding of check goal during verify phase: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId executions execution idcheck-pmd/id phaseverify/phase goals goalcheck/goal /goals Le jeudi 15 mai 2014 23:24:25 UTC+2, Ullrich Hafner a écrit : The PMD plug-in requires that your build creates the pmd.xml file. I.e., you need to run 'mvn pmd:pmd'. Or how did you produce the pmd.xml file in your build before? Am 15.05.2014 um 16:34 schrieb Jean Pierre Froud jpf...@gmail.com: Hi, I'm having a similar issue to this one: PMD plugin doesn't use pmd.xml Unless I explicitly call pmd:pmd, the graph doesn't show. And if I add pmd:pmd, I see in log: Successfully parsed file... and the graph appears. Jenkins ver. 1.544 Static Code Analysis Plug-ins 1.41 -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@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 Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
jenkins-ci.org down
503 Service Unavailable No server is available to handle this request. :( -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RC testing for 1.554.2 started
Hi, Latest RC was made public. Join us testing what will become next LTS release! We have two weeks to make sure that all the fixes[1] are in place and no new regressions was introduced. 1.554.2 will be released 2014-05-28. Report your findings in this thread or in the test plan wiki. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war Check community maintained LTS test plan https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.544.x+RC+Testing [1] https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+10172+AND+labels+%3D+%221.554.2-fixed%22 Thank you -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Jenkins - run Maven build with 3rd Party Dependencies
I have a project to be run through jenkins-maven plug-in. Things look fine and I am using a 3rd party jar in the maven project that I have installed locally. When I run mvn clean install from command prompt, it seems to work fine but when i run the pom through the Jenkins - I get an error .. [ERROR] Failed to execute goal on project dnbiautomation: Could not resolve dependencies for project com.dnb.automation:dnbiautomation:jar:1.0: Could not find artifact com.excel2objects:excel2objects:jar:1.0 in central (http://repo.maven.apache.org/maven2) - [Help 1] How to resolve this? Please help -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
IRC Bot is still having issues creating repos
13:07 +stephenc jenkins-admin: create mapdb-api-plugin on github
13:08 @jenkins-admin Failed to create a repository: {
I solved the problem by forking...
13:13 +stephenc jenkins-admin: fork stephenc/mapdb-api-plugin
13:13 @jenkins-admin Forking mapdb-api-plugin
13:13 @jenkins-admin Created https://github.com/jenkinsci/mapdb-api-plugin
but it was annoying having to create the repo in my github first
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Leaked processes in Jenkins 1.563
I have just upgraded Jenkins from 1.556 to 1.563. I have a job, that stats JBoss application server on my Linux slave node. In 1.556, the java process with server was killed after the build was finished. ProcessTreeKiller managed to kill all processes, that i started during the build. But after the upgrade to version 1.563, the JBoss processes are not killed after the build is finished. It caused me a lot of troubles. I did not change any settings (disabling ProcessTree, asi is mention here: https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller) Do you know something about that? Is this a bug, or expected behaviour? Thaks for reactions. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: ValidateButton without descriptor
I'm trying to do a similar thing but with a hudson.model.ManagementLink.
Problem is that I can't extend ManagementLink AND AbstractDescribableImpl
(as in the example of ProxyConfiguration).
If I implement DescribableMyManagementLink and create the inline
DescriptorMyManagementLink, I can't do the normal getDescriptor()
override, which should be...
@Override
public DescriptorMyManagementLink getDescriptor() {
return (MyManagementLinkDescriptor) super.getDescriptor();
}
...since ManagementLink doesnt have a getDescriptor() since it isn't itself
describable.
Note also, the contents of the index.jelly for MyManagementLink is a series
of components within a f:form tag.
--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/ValidateButton-without-descriptor-tp4409633p4701169.html
Sent from the Jenkins dev mailing list archive at Nabble.com.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Backporting for 1.554.2 started
The daemon that does that was not receiving emails because Dyndns killing its free service severed the mail delivery route. I have that fixed a while back, but Google Groups never retries an email address once it starts bouncing, even after the bounce is fixed, and I didn't notice that that was happening until too late. The problem is corrected now, I'll investigate if I can rerun the daemon by manually feeding commit messages while the daemon was incapacitated. On 05/14/2014 04:09 PM, Christopher Orr wrote: Hmm.. are there still problems with the JIRA bot? I pushed several [FIXED JENKINS-xxx] commits today, and over 24 hours ago to android-emulator-plugin, but JIRA still hasn't updated at all. Thanks, Chris On 05/14/2014 02:51 PM, Stephen Connolly wrote: Only not resolved because the bot has been slow to pick up the [FIXED...] commit comment On 14 May 2014 13:31, ogondza ogon...@gmail.com mailto:ogon...@gmail.com wrote: On Wednesday, May 14, 2014 11:20:27 AM UTC+2, Stephen Connolly wrote: https://github.com/jenkinsci/jenkins/commit/7c620e9fd321029e05f7cc994d3da1dde48411f7 But I also understand if this is too late in the day and we need to wait for 1.554.3... Yes, we will. Note the issue is not resolved. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com mailto:jenkinsci-dev+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 Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com mailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Jenkins Enterprise, our professional version of Jenkins -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: IRC Bot is still having issues creating repos
My apologies. Fixed now.
(11:58:08 AM) kohsuke: jenkins-admin: create foo-plugin on github
(11:58:20 AM) jenkins-admin: New github repository created at
https://github.com/jenkinsci/foo-plugin
On 05/16/2014 05:14 AM, Stephen Connolly wrote:
13:07 +stephenc jenkins-admin: create mapdb-api-plugin on github
13:08 @jenkins-admin Failed to create a repository: {
I solved the problem by forking...
13:13 +stephenc jenkins-admin: fork stephenc/mapdb-api-plugin
13:13 @jenkins-admin Forking mapdb-api-plugin
13:13 @jenkins-admin Created https://github.com/jenkinsci/mapdb-api-plugin
but it was annoying having to create the repo in my github first
--
Kohsuke Kawaguchi http://kohsuke.org/
--
You received this message because you are subscribed to the Google Groups Jenkins
Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Use case for testing the triggerIfResult functionality (NodeLabelParameter plugin)
I'm currently working on further acceptance tests for the NodeLabelParameter plugin within the scope of U. Hafners student projects. At the moment I'm struggling to define a valid use case to test the triggerIfResult options (run next build only if build succeeds, etc.) of the plugin. I tried to set up a freestyle job parameterized with a node parameter (no default node, no node restriction, next build triggered only if build succeeds and node eligibility set to all nodes). To simulate failed or unstable builds I use the text-finder plugin as post build action. The particular slave the job shall be build on contains a text file in its workspace which causes the plugin to mark the build as failed or unstable. I built the job on multiple (dumb) slaves which were prepared to get a failed result. My expectation was that as the first build is failed the other builds won't start. But I always get builds on all slaves. It would be helpful to know in which case those triggerIfResult options are evaluated and whether I need to add further settings, parameters and / or post build actions to the job. Or may be the text-finder plugin is not the appropriate way to simulate failed builds. I'm open to alternative suggestions. -- Martin -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Leaked processes in Jenkins 1.563
There is a similar known issue that started to affect Jenkins in 1.553: https://issues.jenkins-ci.org/browse/JENKINS-22641 Are you absolutely sure it still worked on 1.556 for you? In your case, did you rely on process killing for successful builds only, but also for failed builds? On 16.05.2014, at 16:01, Jan Řezníček ing.jan.rezni...@gmail.com wrote: I have just upgraded Jenkins from 1.556 to 1.563. I have a job, that stats JBoss application server on my Linux slave node. In 1.556, the java process with server was killed after the build was finished. ProcessTreeKiller managed to kill all processes, that i started during the build. But after the upgrade to version 1.563, the JBoss processes are not killed after the build is finished. It caused me a lot of troubles. I did not change any settings (disabling ProcessTree, asi is mention here: https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller) Do you know something about that? Is this a bug, or expected behaviour? Thaks for reactions. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+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 Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
