[JIRA] [findbugs-plugin] (JENKINS-31633) Only first execution is tracked
Title: Message Title C. S. commented on JENKINS-31633 Re: Only first execution is tracked Alright in this case I have solved it like here JENKINS-28746 . I have changed the phases of the different exceutions to be sure that the non breaker execution is executed at first. What would be the advantage to support only freetype? There are some plugins which are limited to maven projects, which can't be used together without creating an own analysis job in jenkins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-31633) Only first execution is tracked
Title: Message Title C. S. commented on JENKINS-31633 Re: Only first execution is tracked It seems not as easy as thought to change the order of the excection caused by the check goal design. The check goal calls internally the findbugs/pmd report goal and detects if there is already a report file and takes it instead of reanalysis. Is there any possibility to skip check goals in your plugin? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-31633) Only first execution is tracked
Title: Message Title C. S. commented on JENKINS-31633 Re: Only first execution is tracked Yes you are right it should cover my goals. But the second time it isn't executed. Here the jenkins output: [INFO] --- findbugs-maven-plugin:3.0.3:findbugs (findbugs) @ business --- [INFO] Fork Value is true [INFO] Done FindBugs Analysis [FINDBUGS] Finding all files that match the pattern findbugsXml.xml [FINDBUGS] Parsing 1 file in TRUNK/business/target [FINDBUGS] Successfully parsed file TRUNK/business/target/findbugsXml.xml of module Heatsoak Business with 0 unique warnings and 0 duplicates. [FINDBUGS] Computing warning deltas based on reference build #1029 [INFO] [INFO] <<< findbugs-maven-plugin:3.0.3:check (findbugs-always) < :findbugs @ business <<< [INFO] [INFO] --- findbugs-maven-plugin:3.0.3:check (findbugs-always) @ business --- [INFO] BugInstance size is 0 [INFO] Error size is 0 [INFO] No errors/warnings found ... [INFO] --- findbugs-maven-plugin:3.0.3:findbugs (findbugs-normal) @ business --- [INFO] Fork Value is true [java] Warnings generated: 47 [INFO] Done FindBugs Analysis Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-31633) Only first execution is tracked
Title: Message Title C. S. commented on JENKINS-31633 Re: Only first execution is tracked I have copied too less output. Before the first findbugs there is the check goal. And yes internally findbugs is called by check. Is there no way to instruct the plugin to use more than one file for the result? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-31633) Only first execution is tracked
Title: Message Title C. S. created an issue Jenkins / JENKINS-31633 Only first execution is tracked Issue Type: Bug Assignee: Ulli Hafner Components: findbugs-plugin Created: 18/Nov/15 5:17 PM Priority: Minor Reporter: C. S. I have different findbugs goals in my pom file configured. One is executed as check to break the build instantly if some rules are violated. The second one is the normal findbugs goal. I have noticed that only the first one is tracked. Add Comment
[JIRA] [findbugs-plugin] (JENKINS-31633) Only first execution is tracked
Title: Message Title C. S. commented on JENKINS-31633 Re: Only first execution is tracked Yes I am using a maven job and we need the possibilities of it. Is there no way to fetch more than one goal or just take the result of a findbugs goal instead of check? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-31633) Only first execution is tracked
Title: Message Title C. S. edited a comment on JENKINS-31633 Re: Only first execution is tracked I don't see the difference, but my plan as workaround will be to change the execution order of the jenkins profile. It should execute the findbugs goal at first and after it the check goal. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-31633) Only first execution is tracked
Title: Message Title C. S. commented on JENKINS-31633 Re: Only first execution is tracked I don't see the difference, but my plan will be to change the execution order of the jenkins profile. It should execute the findbugs goal at first and after it the check goal. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title C. S. updated an issue Jenkins / JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Change By: C. S. Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title C. S. commented on JENKINS-15570 Re: Coverage report includes classes that have been excluded from Jacoco analysis We ran into the same issue. It is important for us to get it working, because we have a lot of generated classes, which should be excluded and it would be a mess to set up each Jenkins job according the new classes. So we decided to exclude the classes from the report via pom. But it seems that the jacoco plugin does its own match from classes to exec file. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-20263) Artifact Resolver does not retrieve the latest version from central Maven Repository
Title: Message Title C. S. commented on JENKINS-20263 Re: Artifact Resolver does not retrieve the latest version from central Maven Repository Can confirm this behaviour. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-28638) Order of version selection dropdown list should be configurable
Title: Message Title C. S. commented on JENKINS-28638 Re: Order of version selection dropdown list should be configurable The order is changed with https://github.com/jenkinsci/repository-connector-plugin/commit/f0035fd9acd1d3aeb20d1ee75e6e3a52ccdcc217 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-29031) Current Build Parameters doesn't pass custom job parameters
Title: Message Title C. S. created an issue Jenkins / JENKINS-29031 Current Build Parameters doesn't pass custom job parameters Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 23/Jun/15 8:46 AM Priority: Minor Reporter: C. S. I have recognized that using Current Build Parameters when triggering another job doesn't pass custom job parameters. Job A and B have both a parameter called DAILY_BUILD. Using Current Build Parameters doesn't pass DAILY_BUILD to job B. Add Comment
[JIRA] [checkstyle-plugin] (JENKINS-28746) Plugin doesn't publish result files but find them
Title: Message Title C. S. created an issue Jenkins / JENKINS-28746 Plugin doesn't publish result files but find them Issue Type: Bug Assignee: Ulli Hafner Components: checkstyle-plugin Created: 04/Jun/15 10:10 AM Environment: Jenkins ver. 1.615 checkstyle-plugin 3.42 checkstyle 6.1.1 Priority: Minor Reporter: C. S. I have recognized that suddenly the checkstyle plugin doesn't publish any checkstyle result anymore. It seems that it finds the files Checkstyle: 0 warnings from 3 analyses.. There is no entry in the build log for the checkstyle plugin. No configuration about the output file of checkstyle. Add Comment
[JIRA] [checkstyle-plugin] (JENKINS-28746) Plugin only publish first result file
Title: Message Title C. S. updated an issue Jenkins / JENKINS-28746 Plugin only publish first result file Change By: C. S. Summary: Plugin doesn't only publish first result filesbutfindthem file Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [checkstyle-plugin] (JENKINS-28746) Plugin doesn't publish result files but find them
Title: Message Title
C. S. updated an issue
Jenkins / JENKINS-28746
Plugin doesn't publish result files but find them
Change By:
C. S.
Ihaverecognizedthatsuddenlythecheckstyleplugindoesn'tpublishanycheckstyleresultanymore.ItseemsthatitfindsthefilesCheckstyle:0warningsfrom3analyses..Thereis no onlyone entryinthebuildlogforthecheckstyleplugin.Noconfigurationabouttheoutputfileofcheckstyle. {code}[INFO]---maven-checkstyle-plugin:2.15:check(default-cli)@warehouse-parent---log4j:WARNNoappenderscouldbefoundforlogger(org.apache.commons.digester3.Digester.sax).log4j:WARNPleaseinitializethelog4jsystemproperly.[CHECKSTYLE]Parsingfile/.../target/checkstyle-result.xml[CHECKSTYLE]Successfullyparsedfile/.../target/checkstyle-result.xmlofmoduleWarehouseParentPOMwith0uniquewarningsand0duplicates.[CHECKSTYLE]Computingwarningdeltasbasedonreferencebuild#497[PMD]Noreportfoundformojocheck[INFO][INFO]---maven-dependency-plugin:2.8:copy(default)@warehouse-parent---[INFO][INFO]---jacoco-maven-plugin:0.7.5.201505241946:prepare-agent(default-prepare-agent)@warehouse-parent---[INFO]argLinesetto-javaagent:/home/jenkins/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/.../target/jacoco.exec[INFO][INFO]---maven-checkstyle-plugin:2.15:checkstyle(compile)@warehouse-parent---[INFO][INFO]---maven-checkstyle-plugin:2.15:checkstyle(check-test)@warehouse-parent---{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues
[JIRA] [checkstyle-plugin] (JENKINS-28746) Plugin only publish first result file
Title: Message Title
C. S. updated an issue
Jenkins / JENKINS-28746
Plugin only publish first result file
Change By:
C. S.
Ihaverecognizedthatsuddenlythecheckstyleplugindoesn'tpublishanycheckstyleresultanymore.ItseemsthatitfindsthefilesCheckstyle:0warningsfrom3analyses.. Thereisonlyoneentryinthebuildlogforthecheckstyleplugin. Noconfigurationabouttheoutputfileofcheckstyle. {code}[INFO]---maven-checkstyle-plugin:2.15:check(default-cli)@warehouse-parent---log4j:WARNNoappenderscouldbefoundforlogger(org.apache.commons.digester3.Digester.sax).log4j:WARNPleaseinitializethelog4jsystemproperly.[CHECKSTYLE]Parsingfile/.../target/checkstyle-result.xml[CHECKSTYLE]Successfullyparsedfile/.../target/checkstyle-result.xmlofmoduleWarehouseParentPOMwith0uniquewarningsand0duplicates.[CHECKSTYLE]Computingwarningdeltasbasedonreferencebuild#497[PMD]Noreportfoundformojocheck[INFO][INFO]---maven-dependency-plugin:2.8:copy(default)@warehouse-parent---[INFO][INFO]---jacoco-maven-plugin:0.7.5.201505241946:prepare-agent(default-prepare-agent)@warehouse-parent---[INFO]argLinesetto-javaagent:/home/jenkins/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/.../target/jacoco.exec[INFO][INFO]---maven-checkstyle-plugin:2.15:checkstyle(compile)@warehouse-parent---[INFO][INFO]---maven-checkstyle-plugin:2.15:checkstyle(check-test)@warehouse-parent---{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To
[JIRA] [checkstyle-plugin] (JENKINS-28746) Plugin only publish first result file
Title: Message Title C. S. resolved as Fixed Thanks for your fast reponse. To be honest, I don't know what I can tell you to give more information. I am really confused. In my opinion checkstyle-result.xml contains all scanned files and the errors/warnings of the check. In my case the file checkstyle-result.xml contains only all scanned files and the console tells me there a X errors. Finally I found my mistake ... I did run first checkstyle:checkstyle on the tests resources and run checkstyle:check on main using in both cases the same outputFile. I was expecting that checkstyle:check just breaks and don't dump any file. That explains the checkstyle-result.xml on Jenkins containing only scanned files from main. The real background behind this issue was that Jenkins doesn't load any checkstyle-result.xml any more. I think it was overwritten by the two executions. Jenkins / JENKINS-28746 Plugin only publish first result file Change By: C. S. Status: Open Resolved Resolution: Fixed Add Comment
[JIRA] [checkstyle-plugin] (JENKINS-28746) Plugin only publish first result file
Title: Message Title C. S. resolved as Not A Defect Jenkins / JENKINS-28746 Plugin only publish first result file Change By: C. S. Status: Reopened Resolved Resolution: NotADefect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [checkstyle-plugin] (JENKINS-28746) Plugin only publish first result file
Title: Message Title C. S. reopened an issue Jenkins / JENKINS-28746 Plugin only publish first result file Change By: C. S. Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-18595) Uncaught TypeError when opening configuration of project (Jenkins 1.521)
C. S. created JENKINS-18595 Uncaught TypeError when opening configuration of project (Jenkins 1.521) Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 03/Jul/13 8:48 AM Description: Getting the error "Uncaught TypeError: Property 'on' of object #HTMLFormElement is not a function" in textarea.js on line 18. If I disable the plugin the problem is gone. Environment: Jenkins 1.521 on Debian 7 x64 Project: Jenkins Priority: Blocker Reporter: C. S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17639) Project disabled message not shown
C. S. created JENKINS-17639 Project disabled message not shown Issue Type: Bug Assignee: Unassigned Components: jenkins-multijob-plugin Created: 16/Apr/13 4:33 PM Project: Jenkins Priority: Minor Reporter: C. S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17285) Submultijob runs as Job on Slaves
C. S. created JENKINS-17285 Submultijob runs as Job on Slaves Issue Type: Bug Assignee: Unassigned Components: jenkins-multijob-plugin Created: 20/Mar/13 9:35 AM Description: I have a hierarchical multijob structure. I get in trouble if it is executed on my slave which has only one executor. The submultijob is running on it and waits for free executors to run the contained projects. Project: Jenkins Priority: Major Reporter: C. S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17131) Some weird exceptions while archiving with raspberry as slave
C. S. created JENKINS-17131 Some weird exceptions while archiving with raspberry as slave Issue Type: Bug Assignee: Unassigned Components: core Created: 08/Mar/13 4:59 PM Description: Executing the archive artifacts step you can find in the slave log following messages: Failed to load native POSIX impl; falling back on Java impl. Stacktrace follows. java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native at org.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96) at org.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65) at org.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24) at hudson.os.PosixAPI.clinit(PosixAPI.java:41) at hudson.util.IOUtils.mode(IOUtils.java:125) at hudson.util.io.TarArchiver.visit(TarArchiver.java:102) at hudson.util.DirScanner$Glob.scan(DirScanner.java:133) at hudson.FilePath.writeToTar(FilePath.java:1939) at hudson.FilePath.access$1000(FilePath.java:168) at hudson.FilePath$36.invoke(FilePath.java:1880) at hudson.FilePath$36.invoke(FilePath.java:1876) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) This error only occurs when trying to archive the artifcats. I have a full build process which works without any errors. Installing the package "libjna-posix-java" fix the above shown exception and result into another exception: Failed to load native POSIX impl; falling back on Java impl. Stacktrace follows. java.lang.UnsatisfiedLinkError: Unable to load library 'libc.so.6': com.sun.jna.Native.open(Ljava/lang/String;)J at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:166) at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:239) at com.sun.jna.Library$Handler.init(Library.java:140) at com.sun.jna.Native.loadLibrary(Native.java:366) at org.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96) at org.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65) at org.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24) at hudson.os.PosixAPI.clinit(PosixAPI.java:41) at hudson.util.IOUtils.mode(IOUtils.java:125) at hudson.util.io.TarArchiver.visit(TarArchiver.java:102) at hudson.util.DirScanner$Glob.scan(DirScanner.java:133) at hudson.FilePath.writeToTar(FilePath.java:1939) at hudson.FilePath.access$1000(FilePath.java:168) at hudson.FilePath$36.invoke(FilePath.java:1880) at hudson.FilePath$36.invoke(FilePath.java:1876) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) But in general it seems to work. There is only an information in the log: log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter). log4j:WARN Please initialize the log4j system properly. If there is a possibility to get more details from the slave client, please tell me. I couldn't find anything in the wiki.
[JIRA] (JENKINS-17131) Some weird exceptions while archiving with raspberry as slave
C. S.
updated JENKINS-17131
Some weird exceptions while archiving with raspberry as slave
Just formatted the text.
Change By:
C. S.
(08/Mar/13 5:01 PM)
Description:
Executingthearchiveartifactsstepyoucanfindintheslavelogfollowingmessages:
{quote}
FailedtoloadnativePOSIXimpl;fallingbackonJavaimpl.Stacktracefollows.java.lang.NoClassDefFoundError:Couldnotinitializeclasscom.sun.jna.Native atorg.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96) atorg.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65) atorg.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24) athudson.os.PosixAPI.clinit(PosixAPI.java:41) athudson.util.IOUtils.mode(IOUtils.java:125) athudson.util.io.TarArchiver.visit(TarArchiver.java:102) athudson.util.DirScanner$Glob.scan(DirScanner.java:133) athudson.FilePath.writeToTar(FilePath.java:1939) athudson.FilePath.access$1000(FilePath.java:168) athudson.FilePath$36.invoke(FilePath.java:1880) athudson.FilePath$36.invoke(FilePath.java:1876) athudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) atjava.lang.Thread.run(Thread.java:722)
{quote}
Thiserroronlyoccurswhentryingtoarchivetheartifcats.Ihaveafullbuildprocesswhichworkswithoutanyerrors.Installingthepackage
*
libjna-posix-java
*
fixtheaboveshownexceptionandresultintoanotherexception:
{quote}
FailedtoloadnativePOSIXimpl;fallingbackonJavaimpl.Stacktracefollows.java.lang.UnsatisfiedLinkError:Unabletoloadlibrarylibc.so.6:com.sun.jna.Native.open(Ljava/lang/String;)J atcom.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:166) atcom.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:239) atcom.sun.jna.Library$Handler.init(Library.java:140) atcom.sun.jna.Native.loadLibrary(Native.java:366) atorg.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96) atorg.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65) atorg.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24) athudson.os.PosixAPI.clinit(PosixAPI.java:41) athudson.util.IOUtils.mode(IOUtils.java:125) athudson.util.io.TarArchiver.visit(TarArchiver.java:102) athudson.util.DirScanner$Glob.scan(DirScanner.java:133) athudson.FilePath.writeToTar(FilePath.java:1939) athudson.FilePath.access$1000(FilePath.java:168) athudson.FilePath$36.invoke(FilePath.java:1880) athudson.FilePath$36.invoke(FilePath.java:1876) athudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) atjava.lang.Thread.run(Thread.java:722)
{quote}
Butingeneralitseemstowork.Thereisonlyaninformationinthelog:
{quote}
log4j:WARNNoappenderscouldbefoundforlogger(org.apache.commons.beanutils.converters.BooleanConverter).log4j:WARNPleaseinitializethelog4jsystemproperly.
{quote}
Ifthereisapossibilitytogetmoredetailsfromtheslaveclient,pleasetellme.Icouldntfindanythinginthewiki.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see:
[JIRA] (JENKINS-16974) Build Now link on MultiJob page doesn't work
C. S. commented on JENKINS-16974 Build Now link on MultiJob page doesnt work Same problem with stopping the job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17069) Can't reset job view
C. S. created JENKINS-17069 Cant reset job view Issue Type: Bug Assignee: Unassigned Attachments: sort.png, sortDefault.png Components: jenkins-multijob-plugin Created: 05/Mar/13 2:52 PM Description: After using the sort by job name, I can't reset the sort order/getting back to the default (see screenshots). Project: Jenkins Priority: Major Reporter: C. S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17069) Can't reset job view
C. S. resolved JENKINS-17069 as Duplicate Cant reset job view Change By: C. S. (05/Mar/13 2:55 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17070) Missing times with multiconfiguration projects
C. S. created JENKINS-17070 Missing times with multiconfiguration projects Issue Type: Bug Assignee: Unassigned Attachments: timesMissing.png Components: jenkins-multijob-plugin Created: 05/Mar/13 3:07 PM Project: Jenkins Priority: Major Reporter: C. S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17071) Support for multiconfiguration projects
C. S. created JENKINS-17071 Support for multiconfiguration projects Issue Type: New Feature Assignee: Unassigned Components: jenkins-multijob-plugin Created: 05/Mar/13 3:11 PM Description: It seems that the plugin doesn't really support multiconfiguration projects. I have some and want to archive artifacts over all instances. The only way at the moment is to have a checkout and archive job at the beginning and at the end. Project: Jenkins Priority: Major Reporter: C. S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17078) Different view of artifact in project overview
C. S. created JENKINS-17078 Different view of artifact in project overview Issue Type: Bug Assignee: Unassigned Attachments: artifacts.png Components: core Created: 05/Mar/13 5:18 PM Description: It seems there is a difference in showing artifacts in multi configuration projects. Project: Jenkins Labels: artifact view Priority: Minor Reporter: C. S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17052) Change to root directory of host configuration didn't work
C. S. created JENKINS-17052 Change to root directory of host configuration didnt work Issue Type: Bug Affects Versions: current Assignee: bap Components: publish-over-ssh Created: 04/Mar/13 3:18 PM Description: Host configuration has an absolute directory and the publisher step has a relative path. The creation of the folder structure works, but the commands are executed in the home directory of the user itself. Project: Jenkins Priority: Major Reporter: C. S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17052) Change to root directory of host configuration didn't work
C. S. commented on JENKINS-17052 Change to root directory of host configuration didnt work What do you think about changing the directory into the remote directory when opening the exec channel? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13061) Support for salted hashes
C. S. created JENKINS-13061: --- Summary: Support for salted hashes Key: JENKINS-13061 URL: https://issues.jenkins-ci.org/browse/JENKINS-13061 Project: Jenkins Issue Type: New Feature Components: mysql-auth Reporter: C. S. Assignee: darkhonor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12816) Support for matrix project
C. S. created JENKINS-12816: --- Summary: Support for matrix project Key: JENKINS-12816 URL: https://issues.jenkins-ci.org/browse/JENKINS-12816 Project: Jenkins Issue Type: New Feature Components: sloccount Reporter: C. S. Assignee: npiguet -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12632) Subversion plugin update fails
[ https://issues.jenkins-ci.org/browse/JENKINS-12632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] C. S. updated JENKINS-12632: Component/s: cvs Subversion plugin update fails -- Key: JENKINS-12632 URL: https://issues.jenkins-ci.org/browse/JENKINS-12632 Project: Jenkins Issue Type: Bug Components: cvs, plugin, subversion, update-center Environment: Jenkins 1.450 CentOS 6.2 (2.6.32-220.4.1.el6.centos.plus.x86_64) java version 1.6.0_29 Java(TM) SE Runtime Environment (build 1.6.0_29-b11) Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02, mixed mode) Reporter: Paul Milliken Labels: jenkins, plugin I'm encountering an issue similar to JENKINS-12514 with Jenkins 1.450. Update manager reports that I'm running subversion plugin 1.34 and 1.37 is available. In my plugins folder I can see: -rw-rw-r--. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.bak -rw-rw-r--. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.jpi I tell Jenkins to install 1.37. Once it's downloaded I can see: -rw-rw-r--. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.bak -rw-rw-r--. 1 jenkins jenkins 2103308 Feb 2 15:43 subversion.jpi Checking the manifests: [jenkins@ plugins]$ unzip -p subversion.bak META-INF/MANIFEST.MF | grep Plugin-Version Plugin-Version: 1.34 [jenkins@ plugins]$ unzip -p subversion.jpi META-INF/MANIFEST.MF | grep Plugin-Version Plugin-Version: 1.37 Restart jenkins to apply the changes. At this point, the present files are: -rw-rw-r--. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.bak -rw-rw-r--. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.jpi and the manifests: [jenkins@ plugins]$ unzip -p subversion.bak META-INF/MANIFEST.MF | grep Plugin-Version Plugin-Version: 1.34 [jenkins@ plugins]$ unzip -p subversion.jpi META-INF/MANIFEST.MF | grep Plugin-Version Plugin-Version: 1.34 And update manager still reports 1.34 with 1.37 available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12307) Stack Trace when going to main configuration page
[
https://issues.jenkins-ci.org/browse/JENKINS-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158958#comment-158958
]
C. S. commented on JENKINS-12307:
-
Are there any news?
Stack Trace when going to main configuration page
-
Key: JENKINS-12307
URL: https://issues.jenkins-ci.org/browse/JENKINS-12307
Project: Jenkins
Issue Type: Bug
Components: warnings
Reporter: mwebber
Assignee: Ulli Hafner
Priority: Minor
When I go (in the web interface) to the main Jenkins configuration page, a
stack trace is generated on the Jenkins console. No adverse results appear on
the web page itself. From the stack track, it looks like it is connected to
the warnings plugin.
This is Jenkins 1.446 and Warnings plugin 3.26 (the latest available at the
time of reporting). I have been noticing this stack track for some time now,
including under earlier releases (I'm not sure how recently it started).
The stack trace:
{noformat}
05-Jan-2012 11:35:26 hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating:
descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason:
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
at
org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
at
org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
at
org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
at
org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at
org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at
org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at
hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at
org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
(snip)
at
winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.AssertionError: null is missing its
