[JIRA] [testlink] (JENKINS-17802) TAP files with platform information and recursive result seeking strategy
Paul Zimmerman commented on JENKINS-17802 TAP files with platform information and recursive result seeking strategy Hello Bruno, I've corrected my description - the phrase /.tap looked very stange (had to mask ist) Also updated the attachment. Please use tapplattest.zip. I wasn't able to remove the other one. Regards Paul 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] [testlink] (JENKINS-17802) TAP files with platform information and recursive result seeking strategy
Bruno P. Kinoshita commented on JENKINS-17802 TAP files with platform information and recursive result seeking strategy Hi Paul! Thanks for updating the issue. I've released tap-plugin 1.11 last Saturday, and am working to release a new version next Friday. I'll either start a cycle on testlink-plugin this week, or after I've finished tap 1.12. 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] [testlink] (JENKINS-17802) TAP files with platform information and recursive result seeking strategy
Paul Zimmerman updated JENKINS-17802 TAP files with platform information and recursive result seeking strategy Change By: Paul Zimmerman (22/Jul/13 6:09 AM) Attachment: tapplattest.zip Description: Hithere,Ihavesometroublewithresultseekingstrategies,tapfilesandplatforms.Indetail:-mytap-filesareinsubfolderstestresults/platform1/tf1.tapandtestresults/platform2/tf1.tap-theresultseekingstrategytestresults/ \ * \ */*.tapbringsonlytheplatform2resultstotestlink-ifIremoveoneplatform(andthecorrespondingtap-file)everythingworks find fine .Theproblemis,thatIhavetestcasesassignedtotwoplatformsandIhave2tapfileswithseparateresultsforeachplatform.TheTestLinkPluginonlytakesthesecondtapfile(samefilenameasthefirstone)andoverwritesthevaluesofthefirstone.SoinTestLinkthetreeentryisgray(showstheresultoverallassignedplatforms).SohowcanIcollectseparateresultsfortwoplatforms? One CurrentlyImakeuseof2Jenkins-Jobstodothis(aworkaround).Also:one tap-Filewithtwoplatforminformationdontseemtowork...Hopethathelpsinanyway.Thanks!Paul 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] [deploy] (JENKINS-16007) Weblogic Deploy periodically not working
Raphael CHAUMIER assigned JENKINS-16007 to Raphael CHAUMIER Weblogic Deploy periodically not working Change By: Raphael CHAUMIER (22/Jul/13 7:27 AM) Assignee: RaphaelCHAUMIER 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] [deploy] (JENKINS-16007) Weblogic Deploy periodically not working
Raphael CHAUMIER updated JENKINS-16007 Weblogic Deploy periodically not working Change By: Raphael CHAUMIER (22/Jul/13 7:27 AM) Component/s: weblogic-deployer 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] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
sanga commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel We just hit this in 1.509.2 i.e. the current jenkins stable release. And it's causing about half our builds to fail at the moment. So our CI system is at the moment pretty much screwed. Raising to critical 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] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Marc Seeger commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel A small note: this happened for us when the master was heavily overloaded (swapping). I reduced the number of executors on the master and just started a slave with more CPU/RAM to take care of the jobs. 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] [ivy] (JENKINS-18848) Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Ronald Müller
commented on JENKINS-18848
Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Hi, Johno
thank you for investigating this issue. My remote settings.xml (referenced in build.xml via: ivy:settings url="" /) is accessible and quite simple:
ivysettings
settings defaultResolver="default" /
resolvers
ibiblio name="public-rep" m2compatible="true" /
ivyrep name="unicomp-ivy-rep" ivyroot="http://jenkins/ivy/repository/"/
url name="unicomp-ivy-rep" checkmodified="true" changingPattern=".*" latest="latest-time"
ivy pattern="http://jenkins/ivy/repository/[organisation]/[module]/[revision]/ivys/[artifact].[ext]" /
artifact pattern="http://jenkins/ivy/repository/[organisation]/[module]/[revision]/jars/[artifact].[ext]" /
/url
filesystem name="local"
ivy pattern="${ivy.default.ivy.user.dir}/local/[organisation]/[module]/[revision]/ivys/[artifact].[ext]" /
artifact pattern="${ivy.default.ivy.user.dir}/local/[organisation]/[module]/[revision]/jars/[artifact].[ext]" /
/filesystem
chain name="default"
resolver ref="public-rep"/
resolver ref="unicomp-ivy-rep"/
/chain
/resolvers
/ivysettings
I've tested the build process from command-line @ /var/lib/jenkins/jobs/project-name/workspace# and everything is fine there. Only jenkins can not build!?
regards
Ronald
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] [role-strategy] (JENKINS-16415) Unable to add project roles using Role stratedy plugin
Oleg Nenashev edited a comment on JENKINS-16415 Unable to add project roles using Role stratedy plugin Can't reproduce issue via Firefox 22.0 and IE 10. In case of IE, config's page layout is awful, but works well. What browser/version do you use? 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] [build-flow] (JENKINS-16980) build flow need sandboxing
SCM/JIRA link daemon commented on JENKINS-16980 build flow need sandboxing Code changed in jenkins User: Daniel Beck Path: src/main/java/com/cloudbees/plugins/flow/BuildFlow.java src/main/resources/com/cloudbees/plugins/flow/BuildFlow/configure-entries.jelly http://jenkins-ci.org/commit/build-flow-plugin/12ef23ec8fd8df235cd7fd6e2ed8bd981a19 Log: Temporary fix for JENKINS-16980, prevent users without RUN_SCRIPTS permission from editing Groovy DSL 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] [robot-plugin] (JENKINS-18230) Parsing output xml: Failed!
Jussi Malinen commented on JENKINS-18230 Parsing output xml: Failed! I am not able to reproduce your problem. The output you have sent works fine when I try it. Is this still an issue for you? 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] [role-strategy] (JENKINS-16415) Unable to add project roles using Role stratedy plugin
Lukas Goormann commented on JENKINS-16415 Unable to add project roles using Role stratedy plugin With me problem occurs with IE 9. (Usage mandatory in our organization) 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] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
sanga commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel I don't see our master swapping. And our master doesn't do much except for serve web pages and farm jobs out to the slaves. We do have many slaves though (on the order of 30 or so I guess). 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] [port-allocator] (JENKINS-18786) Port allocation blocks jobs from executing concurrently
Jyrki Puttonen commented on JENKINS-18786 Port allocation blocks jobs from executing concurrently Seems to be working properly, thanks a lot! 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] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config
Mischa Soujon commented on JENKINS-18667 NullPointerException when saving job config I tried to add a BuildTrigger to the job and got this NPE: ... at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:1822) 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) Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger.getLogFile(BuildResultTrigger.java:46) at org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger.getProjectActions(BuildResultTrigger.java:51) at hudson.model.Project.createTransientActions(Project.java:222) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:724) at hudson.model.AbstractProject.save(AbstractProject.java:279) at hudson.util.PersistedList.onModified(PersistedList.java:173) at hudson.util.PersistedList.replaceBy(PersistedList.java:85) at hudson.model.AbstractProject.submit(AbstractProject.java:1983) at hudson.model.Project.submit(Project.java:202) at hudson.model.Job.doConfigSubmit(Job.java:1084) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:765) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:297) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:160) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:95) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) ... 65 more It is jenkins 1.523 on a windows box. Changing the config.xml by hand shows the change in the job config view but does not work. 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] [weblogic-deployer] (JENKINS-18812) Redeployment feature
Raphael CHAUMIER started work on JENKINS-18812 Redeployment feature Change By: Raphael CHAUMIER (22/Jul/13 8:54 AM) Status: Open InProgress 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] [cli] (JENKINS-18485) Use fine grained permissions for node manipulation via rest api
Oliver Gondža commented on JENKINS-18485 Use fine grained permissions for node manipulation via rest api Pull request: https://github.com/jenkinsci/jenkins/pull/855 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Jan Krotký
commented on JENKINS-17885
Publish over SSH lost main configuration data after jenkins server reboot
Confirming same XLM load error as in CiFS issue. Strange is, that the publish over FTP plugin (which on the quick overlook uses similar configuration) is not affected.
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
22.7.2013 10:22:28 jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
22.7.2013 10:22:28 jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh
INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@5f8d0141: display name [Root WebApplicationContext]; startup date [Mon Jul 22 10:22:28 CEST 2013]; root of context hierarchy
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@5f8d0141]: org.springframework.beans.factory.support.DefaultListableBeanFactory@146ae3ad
22.7.2013 10:22:28 org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@146ae3ad: defining beans [authenticationManager]; root of factory hierarchy
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh
INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@4fabb0ca: display name [Root WebApplicationContext]; startup date [Mon Jul 22 10:22:28 CEST 2013]; root of context hierarchy
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@4fabb0ca]: org.springframework.beans.factory.support.DefaultListableBeanFactory@281edacc
22.7.2013 10:22:28 org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@281edacc: defining beans [filter,legacy]; root of factory hierarchy
22.7.2013 10:22:42 org.apache.commons.jexl.util.Introspector clearCache
INFO: Introspector : detected classloader change. Dumping cache.
22.7.2013 10:22:42 org.apache.commons.jexl.util.Introspector clearCache
INFO: Introspector : detected classloader change. Dumping cache.
couldn't setup local SOCKS5 proxy on port : Address already in use
Running from: /usr/lib/jenkins/jenkins.war
22.7.2013 10:27:50 winstone.Logger logInternal
INFO: Beginning extraction from war file
Jenkins home directory: /var/lib/jenkins found at: System.getProperty("JENKINS_HOME")
22.7.2013 10:27:54 winstone.Logger logInternal
INFO: HTTP Listener started: port=8080
22.7.2013 10:27:54 winstone.Logger logInternal
INFO: AJP13 Listener started: port=8009
22.7.2013 10:27:54 winstone.Logger logInternal
INFO: Winstone Servlet Engine v0.9.10 running: controlPort=disabled
22.7.2013 10:27:55 jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
22.7.2013 10:27:56 jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
22.7.2013 10:27:57 hudson.plugins.im.IMConnectionProvider$ConnectorRunnable run
INFO: Trying to connect
22.7.2013 10:27:57 hudson.plugins.im.HudsonIsBusyListener init
INFO: Executor busy listener created
22.7.2013 10:27:58 org.jenkinsci.plugins.scriptler.ScritplerPluginImpl synchronizeConfig
INFO: initialize scriptler
22.7.2013 10:28:01 hudson.plugins.greenballs.PluginImpl start
INFO: Green Balls!
22.7.2013 10:28:05 jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
22.7.2013 10:28:14 hudson.model.Descriptor load
WARNING: Failed to load /var/lib/jenkins/jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin.xml
hudson.util.IOException2: Unable to read /var/lib/jenkins/jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin.xml
at
[JIRA] [weblogic-deployer] (JENKINS-18685) Support customization of deployment target/environment
Raphael CHAUMIER commented on JENKINS-18685 Support customization of deployment target/environment In the next version, it will be possible for the user to set a set of custom command line . All non specific token values set in this command line will be look for global variables (probably also defined as job parameter). 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] [config-file-provider] (JENKINS-18864) Add an integration to the config-file-provider plugin in the sonar plugin
Arnaud Héritier created JENKINS-18864 Add an integration to the config-file-provider plugin in the sonar plugin Issue Type: Bug Assignee: Sonar Team Components: config-file-provider, sonar Created: 22/Jul/13 9:07 AM Description: Hi, I'm using the config-file-provider plugin (https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin) to share maven settings.xml between all my jobs. I sadly discovered that the sonar plugin didn't take care of it and used the settings files from the node account. If you could add an integration to this plugin it may help a lot. Thx Project: Jenkins Priority: Major Reporter: Arnaud Héritier 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] [weblogic-deployer] (JENKINS-18685) Support customization of deployment target/environment
Raphael CHAUMIER started work on JENKINS-18685 Support customization of deployment target/environment Change By: Raphael CHAUMIER (22/Jul/13 9:01 AM) Status: Open InProgress 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] [config-file-provider] (JENKINS-18864) Add an integration to the config-file-provider plugin in the sonar plugin
sbrandhof commented on JENKINS-18864 Add an integration to the config-file-provider plugin in the sonar plugin Hi Arnaud, could you please move this JIRA ticket to http://jira.codehaus.org/browse/SONARJNKNS ? Thanks 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] [core] (JENKINS-18865) CCTray (cc.xml) file is generated as an empty list of projects (since upgrade to 1.509)
Aaron Searle created JENKINS-18865 CCTray (cc.xml) file is generated as an empty list of projects (since upgrade to 1.509) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 22/Jul/13 9:26 AM Description: Since the upgrade from the previous LTS release 1.480, the cctray integration file has been generated blank. The entire contents is below: Projects/ Project: Jenkins Labels: cctray Priority: Major Reporter: Aaron Searle 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] [role-strategy] (JENKINS-18700) Add support of macro-roles and macro-users
cforce commented on JENKINS-18700 Add support of macro-roles and macro-users How does this work? The documentation is missing. 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Jan Krotký
edited a comment on JENKINS-17885
Publish over SSH lost main configuration data after jenkins server reboot
Confirming same XML load error as in CiFS issue. Strange is, that the publish over FTP plugin (which on the quick overlook uses similar configuration) is not affected.
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
22.7.2013 10:22:28 jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
22.7.2013 10:22:28 jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh
INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@5f8d0141: display name [Root WebApplicationContext]; startup date [Mon Jul 22 10:22:28 CEST 2013]; root of context hierarchy
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@5f8d0141]: org.springframework.beans.factory.support.DefaultListableBeanFactory@146ae3ad
22.7.2013 10:22:28 org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@146ae3ad: defining beans [authenticationManager]; root of factory hierarchy
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh
INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@4fabb0ca: display name [Root WebApplicationContext]; startup date [Mon Jul 22 10:22:28 CEST 2013]; root of context hierarchy
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@4fabb0ca]: org.springframework.beans.factory.support.DefaultListableBeanFactory@281edacc
22.7.2013 10:22:28 org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@281edacc: defining beans [filter,legacy]; root of factory hierarchy
22.7.2013 10:22:42 org.apache.commons.jexl.util.Introspector clearCache
INFO: Introspector : detected classloader change. Dumping cache.
22.7.2013 10:22:42 org.apache.commons.jexl.util.Introspector clearCache
INFO: Introspector : detected classloader change. Dumping cache.
couldn't setup local SOCKS5 proxy on port : Address already in use
Running from: /usr/lib/jenkins/jenkins.war
22.7.2013 10:27:50 winstone.Logger logInternal
INFO: Beginning extraction from war file
Jenkins home directory: /var/lib/jenkins found at: System.getProperty("JENKINS_HOME")
22.7.2013 10:27:54 winstone.Logger logInternal
INFO: HTTP Listener started: port=8080
22.7.2013 10:27:54 winstone.Logger logInternal
INFO: AJP13 Listener started: port=8009
22.7.2013 10:27:54 winstone.Logger logInternal
INFO: Winstone Servlet Engine v0.9.10 running: controlPort=disabled
22.7.2013 10:27:55 jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
22.7.2013 10:27:56 jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
22.7.2013 10:27:57 hudson.plugins.im.IMConnectionProvider$ConnectorRunnable run
INFO: Trying to connect
22.7.2013 10:27:57 hudson.plugins.im.HudsonIsBusyListener init
INFO: Executor busy listener created
22.7.2013 10:27:58 org.jenkinsci.plugins.scriptler.ScritplerPluginImpl synchronizeConfig
INFO: initialize scriptler
22.7.2013 10:28:01 hudson.plugins.greenballs.PluginImpl start
INFO: Green Balls!
22.7.2013 10:28:05 jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
22.7.2013 10:28:14 hudson.model.Descriptor load
WARNING: Failed to load /var/lib/jenkins/jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin.xml
hudson.util.IOException2: Unable to read /var/lib/jenkins/jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin.xml
at
[JIRA] [disk-usage] (JENKINS-13247) disk usage should not follow symlinks
Ben Golding commented on JENKINS-13247 disk usage should not follow symlinks My suggestion is to make this part of the next plugin release, but controlled by a global option (and keep the default behaviour unchanged - follow all symlinks). The global option could also control different behaviour for file/directory symlink, as 'centic' suggested. I would be happy to help with testing. 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] [ec2] (JENKINS-18450) EC2 Plugin Configure Screen Status Code: 500 error
Liam Friel commented on JENKINS-18450 EC2 Plugin Configure Screen Status Code: 500 error Have seen the same issue here This happens with a Jenkins server running on Fedora. It doesn't happen with Jenkins on Ubuntu. had a brief look around and the plugin file structure is completely different for Jenkins on Fedora vs Ubuntu: probably this is the issue, somehow. 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] [role-strategy] (JENKINS-16415) Unable to add project roles using Role stratedy plugin
Oleg Nenashev updated JENKINS-16415 Unable to add project roles using Role stratedy plugin Change By: Oleg Nenashev (22/Jul/13 7:58 AM) Environment: Linux Windows,IE9.0 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] [role-strategy] (JENKINS-18700) Add support of macro-roles and macro-users
Oleg Nenashev resolved JENKINS-18700 as Fixed Add support of macro-roles and macro-users Implemented in 2.1.0 Change By: Oleg Nenashev (22/Jul/13 10:41 AM) Status: InProgress Resolved Resolution: Fixed 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] [svn-tag] (JENKINS-3034) Pegging the externals when tagging.
Ricardo Ruiz commented on JENKINS-3034 Pegging the externals when tagging. I agree this is essential. 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] [rebuild] (JENKINS-15882) rebuild plugin should not store non-stored password parameter
SCM/JIRA link daemon commented on JENKINS-15882 rebuild plugin should not store non-stored password parameter Code changed in jenkins User: Rino Path: src/main/java/com/sonyericsson/rebuild/RebuildAction.java src/main/java/com/sonyericsson/rebuild/RebuildConfiguration.java src/main/resources/com/sonyericsson/rebuild/RebuildAction/PasswordParameterValue.jelly src/main/resources/com/sonyericsson/rebuild/RebuildAction/global.jelly src/main/resources/com/sonyericsson/rebuild/RebuildAction/help-rememberPassword.html src/main/resources/com/sonyericsson/rebuild/RebuildAction/parameterized.jelly http://jenkins-ci.org/commit/rebuild-plugin/17cfac781eae06934a25498c1f6372f6676435a0 Log: Fixed JENKINS-15882 - rebuild plugin should not store non-stored password parameter Added global configuration option to (not) remember password 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] [rebuild] (JENKINS-15882) rebuild plugin should not store non-stored password parameter
SCM/JIRA link daemon commented on JENKINS-15882 rebuild plugin should not store non-stored password parameter Code changed in jenkins User: Rino Path: .gitignore src/main/java/com/sonyericsson/rebuild/RebuildAction.java src/main/java/com/sonyericsson/rebuild/RebuildConfiguration.java src/main/java/com/sonyericsson/rebuild/RebuildDescriptor.java src/main/resources/com/sonyericsson/rebuild/RebuildAction/PasswordParameterValue.jelly src/main/resources/com/sonyericsson/rebuild/RebuildAction/global.jelly src/main/resources/com/sonyericsson/rebuild/RebuildAction/help-rememberPassword.html src/main/resources/com/sonyericsson/rebuild/RebuildAction/parameterized.jelly src/main/resources/com/sonyericsson/rebuild/RebuildDescriptor/config.jelly src/main/resources/com/sonyericsson/rebuild/RebuildDescriptor/help-rememberPasswordEnabled.html http://jenkins-ci.org/commit/rebuild-plugin/6678b8e297661bdbb83649280546d927ea06c617 Log: JENKINS-15882 - rebuild plugin should not store non-stored password parameter fixed review comment 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] [rebuild] (JENKINS-15882) rebuild plugin should not store non-stored password parameter
SCM/JIRA link daemon commented on JENKINS-15882 rebuild plugin should not store non-stored password parameter Code changed in jenkins User: Rino Path: src/main/resources/com/sonyericsson/rebuild/RebuildAction/global.jelly http://jenkins-ci.org/commit/rebuild-plugin/690ac040b745e95de347e429d9ed23c2312374b5 Log: JENKINS-15882 - rebuild plugin should not store non-stored password parameter -added default true 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] [extended-choice-parameter] (JENKINS-14828) Rebuild plugin crashes when used in conjuction with Extended Choice Parameter
SCM/JIRA link daemon commented on JENKINS-14828 Rebuild plugin crashes when used in conjuction with Extended Choice Parameter Code changed in jenkins User: Rino Path: src/main/resources/com/sonyericsson/rebuild/RebuildAction/ExtendedChoiceParameterValue.jelly http://jenkins-ci.org/commit/rebuild-plugin/2102137b5b988d46283368c1fb61dd216183b7be Log: Fixed: JENKINS-14828 - Rebuild plugin crashes when used in conjuction with Extended Choice Parameter Added the Jelly file that makes it possible to change the value of the parameter when rebuilding (simple string input box). Unfortunately the type of parameter is not serialized in the job, so it's hard to present a nice gui when rebuilding based on the type of extended choice parameter. We could use the current job configuration, however this might conflict with builds that ran in the past with a different configuration. 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] [rebuild] (JENKINS-15882) rebuild plugin should not store non-stored password parameter
SCM/JIRA link daemon commented on JENKINS-15882 rebuild plugin should not store non-stored password parameter Code changed in jenkins User: Rino Path: src/main/java/com/sonyericsson/rebuild/RebuildAction.java src/main/java/com/sonyericsson/rebuild/RebuildConfiguration.java src/main/resources/com/sonyericsson/rebuild/RebuildAction/PasswordParameterValue.jelly src/main/resources/com/sonyericsson/rebuild/RebuildAction/global.jelly src/main/resources/com/sonyericsson/rebuild/RebuildAction/help-rememberPassword.html http://jenkins-ci.org/commit/rebuild-plugin/0eb0c0005525327e3818c4b961ab65da28fcd75d Log: JENKINS-15882 - rebuild plugin should not store non-stored password parameter -Replaced if jelly tag by choose -fixed global jelly to show documentation -imrpoved documentation -added license -added javadoc 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] [role-strategy] (JENKINS-18700) Add support of macro-roles and macro-users
Oleg Nenashev commented on JENKINS-18700 Add support of macro-roles and macro-users Feature is available since 2.1.0. In this version, you're able to see brief description in the "list-macros" page. BTW, I should update Wiki page. Do you want to implement your own macros? 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] [core] (JENKINS-18169) Deadlock when running multiple delete
Antoine Musso commented on JENKINS-18169 Deadlock when running multiple delete I am hit by the same issue with Jenkins 1.509.2. 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] [plugin] (JENKINS-18866) Symlink prevens backup from ThinBackup
Frank Roghair created JENKINS-18866 Symlink prevens backup from ThinBackup Issue Type: Bug Assignee: Unassigned Components: plugin Created: 22/Jul/13 11:31 AM Description: Removal of the symlinks lastFailedBuild,lastUnstableBuild and lastUnsuccessfulBuild does result in a correct backup. Error message: Jul 22, 2013 1:13:27 PM org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork backupNow SEVERE: Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path 'c:\work\backup'. java.io.FileNotFoundException: Source 'C:\Program Files (x86)\Jenkins\jobs\Build Job 1\builds\lastFailedBuild' does not exist at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:866) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:814) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildFiles(HudsonBackup.java:302) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildsFor(HudsonBackup.java:270) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJob(HudsonBackup.java:208) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobsDirectory(HudsonBackup.java:196) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobs(HudsonBackup.java:175) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backup(HudsonBackup.java:142) at org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork.backupNow(ThinBackupPeriodicWork.java:87) at org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink$1.execute(ThinBackupMgmtLink.java:76) at org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:54) at java.lang.Thread.run(Unknown Source) Environment: windows7 8 Project: Jenkins Priority: Major Reporter: Frank Roghair 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] [locale] (JENKINS-10388) Wrong french translation
SCM/JIRA link daemon commented on JENKINS-10388 Wrong french translation Code changed in jenkins User: Harald Albers Path: core/src/main/resources/hudson/model/Messages_fr.properties http://jenkins-ci.org/commit/jenkins/793682e3f0bfc49feea080e581c9cb9ba02b80b6 Log: FIXED JENKINS-10388 Wrong french translation 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] [locale] (JENKINS-10388) Wrong french translation
SCM/JIRA link daemon resolved JENKINS-10388 as Fixed Wrong french translation Change By: SCM/JIRA link daemon (22/Jul/13 11:34 AM) Status: Open Resolved Resolution: Fixed 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] [plugin] (JENKINS-18866) Symlink prevens backup from ThinBackup
Frank Roghair commented on JENKINS-18866 Symlink prevens backup from ThinBackup version is 1.523 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] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
sanga updated JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Change By: sanga (22/Jul/13 7:37 AM) Priority: Major Critical 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] [fstrigger] (JENKINS-18658) NPE in FSTrigger upon configuration save
Zoltan Szeverenyi commented on JENKINS-18658 NPE in FSTrigger upon configuration save Also occurs when running Jenkins 1.522 on RHEL release 6.2 (Santiago) 2.6.32-220.el6.x86_64 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] [subversion] (JENKINS-18847) FishEye No Longer Recognized (or Shown) for Subversion Repository Browser
John Werner commented on JENKINS-18847 FishEye No Longer Recognized (or Shown) for Subversion Repository Browser Here's the version information for the install the trace is from: Jenkins: 1.520 Subversion: 1.50 I am also seeing the same inability to select FishEye on another install: Jenkins: 1.523 Subversion: 1.50 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] [maven] (JENKINS-18459) IOException: No Such File
Igor Kostenko commented on JENKINS-18459 IOException: No Such File I'm so happy that I found that bug. I couldn't upgrade to jenkins 1.519-1.523, no linux slaves were running (windows slaves were fine) and I couldn't figure out what the issue was. Now I see that it was because of my .jenkins script in home directory of build user (and we have mounted home directories - so it is the same directory on all hosts). After renaming the script and changing all jobs which using it upgraded jenkins is working ok. Hopefully this cache directory wouldn't be messed up because many hosts are using it. 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] [jacoco] (JENKINS-16788) Coverage trend's legend is only partially translated
centic resolved JENKINS-16788 as Fixed Coverage trends legend is only partially translated This should be fixed now and will be included in the next release of the JaCoCo plugin. A few more translations were adjusted as well. Change By: centic (22/Jul/13 8:37 AM) Status: InProgress Resolved Resolution: Fixed 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] [custom-tools] (JENKINS-18774) Add setup of additional variables after installation
Oleg Nenashev commented on JENKINS-18774 Add setup of additional variables after installation TODO: fix multiple modification of one variable (ex, LD_LIBRARY_PATH) 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] [locale] (JENKINS-10388) Wrong french translation
dogfood commented on JENKINS-10388 Wrong french translation Integrated in jenkins_main_trunk #2737 FIXED JENKINS-10388 Wrong french translation (Revision 793682e3f0bfc49feea080e581c9cb9ba02b80b6) Result = SUCCESS github : 793682e3f0bfc49feea080e581c9cb9ba02b80b6 Files : core/src/main/resources/hudson/model/Messages_fr.properties 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] [disk-usage] (JENKINS-13247) disk usage should not follow symlinks
Greg Moncreaff commented on JENKINS-13247 disk usage should not follow symlinks When I wrote this ticket, the original environment was linux clearcase dynamic views. For those that haven't had suffered with clearcase in a unix environment, it creates a virtual file system /vobs (vobs/subdirs based on how you divide your typically monolithic repository) creates a sorta workspace /view/workspace_name inside the sorta workspace has /view/workspace_name/vobs/whatever also in the sorta workspace is /view/workspace_name/links_to_all_root_filesystem_elements so, if you follow smylinks you have infinite recursion. 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] [msbuild] (JENKINS-17876) MSBuild Command Line Arguments quotes being stripped...not 5552
François Le Rolland
commented on JENKINS-17876
MSBuild Command Line Arguments quotes being stripped...not 5552
I have the same issue as Damian.
I think the problem come from spaces in parameter values. Like for Damian, one of my parameters contains spaces and it's surrounded by quotes (') in the command line.
I have the same error message: Only one project can be specified.
To solve the issue, I have to roll back to previous version of the plugin (1.15).
Regards,
François
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] [core] (JENKINS-18870) debian init script is missing access_log support
Antoine Musso created JENKINS-18870 debian init script is missing access_log support Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Jul/13 2:43 PM Description: The rpm provide JENKINS_ENABLE_ACCESS_LOG which enable Jenkins to write down some access log. It is missing from the debian package. One would have to: 1) add JENKINS_ENABLE_ACCESS_LOG support in debian/debian/jenkins.init 2) update the logrotate script 3) update debian/debian/jenkins.default Project: Jenkins Priority: Major Reporter: Antoine Musso 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] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Björn Pedersen commented on JENKINS-18867 Wrong binding for the remove logs button Firefox 22 Jenkins 1.523 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] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor commented on JENKINS-18867 Wrong binding for the remove logs button Could your please provide : Your jenkins version Your browser version 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] [git] (JENKINS-10385) FATAL: Could not checkout null with start point after a reset --hard to remove a commit
Justin Hammond edited a comment on JENKINS-10385 FATAL: Could not checkout null with start point after a reset --hard to remove a commit Just ran into this error. I will attempt restarting the server, but otherwise it's locked up. Edit: Alright I restarted my server and it didn't make a difference. I noticed that git was checking out origin/master but when it was building it was referencing origin1/master. I believe this was caused because I added a second git repo and removed it. The work around was to copy the job to a new one. Edit 2: I've been able to recreate this issue by creating a project that checks out from some repo, then in a bash script during the build process, performing a git clone on some other repo (it's crazy, yeah..). 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] [testlink] (JENKINS-18871) After reloading configuration from disk, Jenkins doesn't read the changes of system configuration
Valery Vindover created JENKINS-18871 After reloading configuration from disk, Jenkins doesnt read the changes of system configuration Issue Type: Bug Assignee: Bruno P. Kinoshita Components: testlink Created: 22/Jul/13 2:53 PM Description: I've got installed Testlink plugin. If I create or change file /var/lib/jenkins/hudson.plugins.testlink.TestLinkBuilder.xml and then run reload-configuration, the changes are not applied. If I restart Jenkins, they are. Due Date: 22/Jul/13 12:00 AM Environment: Ubuntu 12.04 amd64 Project: Jenkins Priority: Major Reporter: Valery Vindover 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] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Shannon Kerr commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Is the fix going to change? 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] [core] (JENKINS-18875) st:bind seems to include json2.js, but not everytime
Frédéric Camblor
created JENKINS-18875
st:bind seems to include json2.js, but not everytime
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
22/Jul/13 4:33 PM
Description:
When installing SCM-Sync-Configuration plugin v0.0.7.2 on 1.523, it seems like this line of code :
var plugin = st:bind value="${it}"/;
is sometimes (depending on Jenkins installations) generating a strange output in the HTML :
var plugin = script src='' type='text/_javascript_'/scriptmakeStaplerProxy('/jenkins/$stapler/bound/47f87312-880f-40fc-9a12-0a75149deedc','xx',['purgeScmSyncConfigLogs']);
Whereas in 1.509.2, I have this generated output :
var plugin = makeStaplerProxy('/$stapler/bound/some-token','another token',['purgeScmSyncConfigLogs']);
I personnally don't reproduce it on a fresh 1.523 install, but Björn Pedersen is reproducing it on its instance.
Is there something bad :
In my code (I shouldn't affect the call to st:bind to a js variable because it could potentially has to include necessary third party js files like json2.js)
= if this is the case, is there a workaround to proxify my plugin instance on the JS clientside world ? (other than having to do stuff by hand by sending manual Ajax calls to the server side)
In Björn Pedersen's installation, or Jenkins core ?
Environment:
Jenkins 1.523
Project:
Jenkins
Priority:
Major
Reporter:
Frédéric Camblor
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] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor commented on JENKINS-18867 Wrong binding for the remove logs button I just raised JENKINS-18875 because it doesn't seem to be related to the plugin You can track this issue to have feedback about your problem 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] [disk-usage] (JENKINS-18872) Disk usage plugin doesn't show usage by promotions
recampbell created JENKINS-18872 Disk usage plugin doesnt show usage by promotions Issue Type: Bug Assignee: vjuranek Components: disk-usage, promoted-builds Created: 22/Jul/13 3:33 PM Description: The disk used by a job's promotions is not included in disk usage calculated for a promotion. I have a job which disk-usage reports 200MB of builds, but du -hs hudson/home/job name reports as 3.6GB. The 'promotions' folder in this plugin consumes 3GB thereof (mostly in the workspace folder). Environment: 1.509.2 Project: Jenkins Priority: Major Reporter: recampbell 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] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor
commented on JENKINS-18867
Wrong binding for the remove logs button
I just download 1.523 and cannot reproduce your issue
In the html page, I have :
function removeLog() {
var plugin = makeStaplerProxy('/$stapler/bound/445063c5-e7f0-4900-bf56-666d02720240','bc2fe9c2-6963-46ba-bf58-6dbcd40eb78d',['purgeScmSyncConfigLogs']);
plugin.purgeScmSyncConfigLogs();
alert("SCM Sync Config errors purged ! You can refresh the page.");
}
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] [core] (JENKINS-18875) st:bind seems to include json2.js, but not everytime
Frédéric Camblor
updated JENKINS-18875
st:bind seems to include json2.js, but not everytime
Change By:
Frédéric Camblor
(22/Jul/13 4:39 PM)
Description:
WheninstallingSCM-Sync-Configurationpluginv0.0.7.2on1.523,itseemslike[thislineofcode|https://github.com/jenkinsci/scm-sync-configuration-plugin/blob/master/src/main/resources/hudson/plugins/scm_sync_configuration/extensions/ScmSyncConfigurationPageDecorator/footer.jelly#L64]:{code}varplugin=st:bindvalue=${it}/;{code}issometimes(dependingonJenkinsinstallations)generatingastrangeoutputintheHTML:{code}varplugin=scriptsrc="">{code}Whereasin1.509.2,Ihavethisgeneratedoutput:{code}varplugin=makeStaplerProxy(/$stapler/bound/some-token,anothertoken,[purgeScmSyncConfigLogs]);{code}Ipersonnallydontreproduceitonafresh1.523install,butBjörnPedersenisreproducingitonitsinstance.Istheresomethingbad:-Inmycode(Ishouldntaffectthecalltost:bindtoajsvariablebecauseitcould_potentially_hastoincludenecessarythirdpartyjsfileslikejson2.js)=ifthisisthecase,isthereaworkaroundtoproxifymyplugininstanceontheJSclientsideworld?(otherthanhavingtodostuffbyhandbysending_manual_Ajaxcallstotheserverside)-InBjörnPedersensinstallation,orJenkinscore?
Sidenote:Seemslikethesourceoftheproblemislocatedin[thiscommit|https://github.com/stapler/stapler/commit/48cdf0f3242c6a79bb398e9115c0db7526c42a50#L4R74]whichloadsjson2.jsifitisntalreadyloaded.
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] [port-allocator] (JENKINS-18786) Port allocation blocks jobs from executing concurrently
Richard Mortimer assigned JENKINS-18786 to Peter Wilcsinszky Port allocation blocks jobs from executing concurrently Assign to Peter (who fixed JENKINS-11255) to check that he has no objections to the proposed fix for this issue. I don't think the fix will break pooled ports but you never know! Change By: Richard Mortimer (22/Jul/13 4:58 PM) Assignee: RichardMortimer PeterWilcsinszky 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] [scm-sync-configuration] (JENKINS-16024) SCM Sync fails to check in any files
A.J. Brown commented on JENKINS-16024 SCM Sync fails to check in any files I've also verified that restarting Jenkins fixes the problem. 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] [port-allocator] (JENKINS-18786) Port allocation blocks jobs from executing concurrently
Richard Mortimer commented on JENKINS-18786 Port allocation blocks jobs from executing concurrently Thanks for testing. 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] [ssh-slaves] (JENKINS-2293) ssh slave doesn't detect correctly java installation
Waldek M commented on JENKINS-2293 ssh slave doesnt detect correctly java installation I've raised the ticket: https://issues.jenkins-ci.org/browse/JENKINS-18767 If some more details are needed, please let me know. 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] [core] (JENKINS-18869) list-view with lots of tabs renders a very wide job table
Marc Günther created JENKINS-18869 list-view with lots of tabs renders a very wide job table Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Jul/13 2:16 PM Description: If you have a list view with lots of tabs (so you have to scroll horizontally), the table with the jobs becomes as wide as the tabs. This leaves very much space between the columns, and makes the table very much unusable. Expected: make the table es wide as necessary to display it's contents, and not wider. Project: Jenkins Priority: Trivial Reporter: Marc Günther 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] [promoted-builds] (JENKINS-18873) No way to delete promoted-builds from GUI
recampbell created JENKINS-18873 No way to delete promoted-builds from GUI Issue Type: Bug Assignee: Unassigned Components: promoted-builds Created: 22/Jul/13 3:41 PM Description: The promoted-builds plugin creates a directory called 'promotions' in the job's root directory. There is no way to browse the list of 'builds' for a given promotion, so as to delete them. This, confounded by the inability to see disk-usage of a promotion (JENKINS-18872), makes disk management almost impossible, except from the command line. Project: Jenkins Priority: Major Reporter: recampbell 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] [promoted-builds] (JENKINS-18873) No way to delete promoted-builds from GUI
Jesse Glick commented on JENKINS-18873 No way to delete promoted-builds from GUI https://github.com/jenkinsci/promoted-builds-plugin/commit/3b979f90ffe49487252842c8002ab9936489207c made it easier to navigate to promotion processes (the “job” corresponding to promotions which are the “builds”), which may have addressed this. 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] [maven] (JENKINS-18592) JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520
Tony Sweeney commented on JENKINS-18592 JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520 We see the same problem. None of our Java5 Maven builds work any longer. Some of the classes in the maven-plugin.hpi are Java6 format: [sweeney@hudson0 plugins]$ unzip -l -p maven-plugin.hpi 'WEB-INF/classes/hudson/maven/ProcessCache$GetSystemProperties.class' xxx [sweeney@hudson0 plugins]$ file xxx xxx: compiled Java class data, version 50.0 [sweeney@hudson0 plugins]$ rm xxx [sweeney@hudson0 plugins]$ We have to have Java5 artefacts because the target J2EE container runs atop Java5. We can work round this by using the Java6 compiler and modifying the build to explicitly request Java5-compatible artefacts, but that means changing several dozen jobs. If Java5 is deprecated in this release I would have expected to see something in the changelog. 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] [android-emulator] (JENKINS-18584) Install Android package task doesn't find aapt with newer SDK
Steve Moyer commented on JENKINS-18584 Install Android package task doesnt find aapt with newer SDK Pull request submitted. 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] [git] (JENKINS-10385) FATAL: Could not checkout null with start point after a reset --hard to remove a commit
Justin Hammond commented on JENKINS-10385 FATAL: Could not checkout null with start point after a reset --hard to remove a commit Just ran into this error. I will attempt restarting the server, but otherwise it's locked up. 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] [core] (JENKINS-18868) [xstream] ConcurrentModificationException from PrioritizedList$PrioritizedItemIterator.next
Jesse Glick created JENKINS-18868 [xstream] ConcurrentModificationException from PrioritizedList$PrioritizedItemIterator.next Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Jul/13 1:35 PM Description: Observed to break startup. java.util.ConcurrentModificationException at java.util.TreeMap$PrivateEntryIterator.nextEntry(Unknown Source) at java.util.TreeMap$KeyIterator.next(Unknown Source) at com.thoughtworks.xstream.core.util.PrioritizedList$PrioritizedItemIterator.next(PrioritizedList.java:91) at com.thoughtworks.xstream.core.DefaultConverterLookup.lookupConverterForType(DefaultConverterLookup.java:55) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:56) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061) at hudson.util.XStream2.unmarshal(XStream2.java:109) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:925) at hudson.XmlFile.read(XmlFile.java:143) at hudson.model.Items.load(Items.java:220) ... Environment: 1.509.x Project: Jenkins Labels: xstream threads Priority: Major Reporter: Jesse Glick 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] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor
edited a comment on JENKINS-18867
Wrong binding for the remove logs button
I just downloaded 1.523 and cannot reproduce your issue
In the html page, I have :
function removeLog() {
var plugin = makeStaplerProxy('/$stapler/bound/445063c5-e7f0-4900-bf56-666d02720240','bc2fe9c2-6963-46ba-bf58-6dbcd40eb78d',['purgeScmSyncConfigLogs']);
plugin.purgeScmSyncConfigLogs();
alert("SCM Sync Config errors purged ! You can refresh the page.");
}
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] [promoted-builds] (JENKINS-18873) No way to delete promoted-builds from GUI
recampbell edited a comment on JENKINS-18873 No way to delete promoted-builds from GUI (removed) 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] [active-directory] (JENKINS-3761) When login j_acegi_security_check return a 404 error
twizzle twizzle commented on JENKINS-3761 When login j_acegi_security_check return a 404 error Kohsuke Kawaguchi, This plugin does not work properly; with matrix-based authentication enabled the workarounds simply do not work. Can you either fix it or disable the matrix authentication option in the Jenkins config page when Active Directory has been selected. It would save people being misled by Jenkins' capabilities and spending time reaching this conclusion. 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] [core] (JENKINS-18874) logrotate script kills Jenkins (SIGALRM)
Antoine Musso created JENKINS-18874 logrotate script kills Jenkins (SIGALRM) Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Jul/13 4:11 PM Description: The logrotate script provided in the rpm and opensuse packages send an ALRM script to java after the log have been rotated. The result is that it entirely kills the java process which is not very nice. Way to reproduce: /bin/kill -s ALRM pid of java process there You could react on SIGUSR1 / SIGUSR2 maybe. Environment: 1.590.2 Project: Jenkins Priority: Major Reporter: Antoine Musso 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] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Björn Pedersen created JENKINS-18867 Wrong binding for the remove logs button Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 22/Jul/13 1:12 PM Description: Wrong binding for the 'remove logs' footer button. The result is a JS-Error: Timestamp: 22.07.2013 15:11:09 Error: SyntaxError: syntax error Source File: http://./jenkins/ Line: 355, Column: 25 Source Code: var plugin = script src=''margin-top:0;margin-bottom:10px;'>and the output of the script as plain text. Project: Jenkins Priority: Minor Reporter: Björn Pedersen 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] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor updated JENKINS-18867 Wrong binding for the remove logs button Change By: Frédéric Camblor (22/Jul/13 2:49 PM) Environment: scm-sync-configurationv0.0.7.2 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] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor edited a comment on JENKINS-18867 Wrong binding for the remove logs button I don't reproduce your issue on 1.509.2 (latest LTS) either. I just raised JENKINS-18875 because it doesn't seem to be related to the plugin You can track this issue to have feedback about your problem 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] [port-allocator] (JENKINS-18786) Port allocation blocks jobs from executing concurrently
Peter Wilcsinszky commented on JENKINS-18786 Port allocation blocks jobs from executing concurrently It's my fault and I think port pools do not need ResourceActivity either. I've only added it because I thought it is better to block in the queue, than start the build and blocking there without any messages. Just did not tested it with slaves. I've removed it completely here: https://github.com/jenkinsci/port-allocator-plugin/pull/4 Here's the build: https://buildhive.cloudbees.com/job/jenkinsci/job/port-allocator-plugin/13/org.jenkins-ci.plugins$port-allocator/artifact/org.jenkins-ci.plugins/port-allocator/1.7-SNAPSHOT/port-allocator-1.7-SNAPSHOT.hpi We will test it within this week. 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] [core] (JENKINS-18537) java.lang.ArrayIndexOutOfBoundsException when trying to save data
Joseph Wilkicki commented on JENKINS-18537 java.lang.ArrayIndexOutOfBoundsException when trying to save data I'm seeing this issue on a fresh install of Jenkins 1.523 on RHEL4 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] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Björn Pedersen
commented on JENKINS-18867
Wrong binding for the remove logs button
Here I have (this time with google-chrome):
{{
script type="text/_javascript_"
function removeLog() {
alert("Only administrators can purge logs !");
return;
var plugin = script src='' type='text/_javascript_'/scriptmakeStaplerProxy('/jenkins/$stapler/bound/47f87312-880f-40fc-9a12-0a75149deedc','xx',['purgeScmSyncConfigLogs']);
plugin.purgeScmSyncConfigLogs();
alert("SCM Sync Config errors purged ! You can refresh the page.");
}
/script
}}
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] [jacoco] (JENKINS-18863) JaCoCo plugin does not handle JaCoCo modules for the coverage trend charts correctly
centic commented on JENKINS-18863 JaCoCo plugin does not handle JaCoCo modules for the coverage trend charts correctly Hmm, the build is from yesterday, i.e. 2013-07-21, somehow Jenkins or the JaCoCo plugin try to access an outdated build directory. I have now removed those old builds and restarted Jenkins, but the error message still appears, any clue where it gets this outdated build-date from? 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] [tap] (JENKINS-17504) TAP Plugin generates bad detail links on tapTestReport page
Ken Raffenetti commented on JENKINS-17504 TAP Plugin generates bad detail links on tapTestReport page Updating to 1.11 brought back the bad behavior Dave described in my installation. 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] [jacoco] (JENKINS-18863) JaCoCo plugin does not handle JaCoCo modules for the coverage trend charts correctly
centic resolved JENKINS-18863 as Cannot Reproduce JaCoCo plugin does not handle JaCoCo modules for the coverage trend charts correctly After removing all build information the issue disappeared, strange that I could not find the build 2012-10-04 being mentioned in any config-file or build-file, I wonder where Jenkins did store/cache this information... Change By: centic (22/Jul/13 8:28 PM) Status: Open Resolved Resolution: CannotReproduce 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] [tap] (JENKINS-17504) TAP Plugin generates bad detail links on tapTestReport page
Bruno P. Kinoshita commented on JENKINS-17504 TAP Plugin generates bad detail links on tapTestReport page @Ken, weird. I'll take a look tomorrow Ken. Sorry for that :-/ 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] [tap] (JENKINS-17504) TAP Plugin generates bad detail links on tapTestReport page
Bruno P. Kinoshita reopened JENKINS-17504 TAP Plugin generates bad detail links on tapTestReport page Reopening due to regression Change By: Bruno P. Kinoshita (22/Jul/13 8:29 PM) Resolution: Fixed Status: Closed Reopened 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] [role-strategy] (JENKINS-18700) Add support of macro-roles and macro-users
cforce commented on JENKINS-18700 Add support of macro-roles and macro-users Its difficult Tod say anything as long i can't und erstand how Theiß macros work and what possibilities they habe. Would be helpful indeed Tod habe some developer doc 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] [core] (JENKINS-17183) Exception: java.lang.NullPointerException
C. Alex Reober commented on JENKINS-17183 Exception: java.lang.NullPointerException Update: This is not working still in Jenkins ver. 1.522 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] [job-import] (JENKINS-18816) Jobs disappear when upgrading from Jenkins 1.514 to 1.523
xylo man edited a comment on JENKINS-18816 Jobs disappear when upgrading from Jenkins 1.514 to 1.523 I attempted to upgrade an instance today as well and was met with the same issues. New jobs had a configuration similar to the visible attached to this issue most of these jobs were created on 1.518 version of jenkins if my memory serves me right. However, config_hidden.xml is similar to jobs that were created on the older version of jenkins prior to the 1.518 version. 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] [job-import] (JENKINS-18816) Jobs disappear when upgrading from Jenkins 1.514 to 1.523
xylo man edited a comment on JENKINS-18816 Jobs disappear when upgrading from Jenkins 1.514 to 1.523 I attempted to upgrade an instance today as well and was met with the same issues. New jobs had a configuration similar to the visible attached to this issue. Most of those jobs were created on 1.518 version of jenkins if my memory serves me right. However, config_hidden is similar to jobs that were created on the older version of jenkins prior to the 1.518 upgrade. 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] [job-import] (JENKINS-18816) Jobs disappear when upgrading from Jenkins 1.514 to 1.523
xylo man commented on JENKINS-18816 Jobs disappear when upgrading from Jenkins 1.514 to 1.523 I attempted to upgrade an instance today as well and was met with the same issues. New jobs had a configuration similar to the visible attached to this issue. Most of those jobs were created on 1.514 version of jenkins if my memory serves me right. However, config_hidden is similar to jobs that were created on the older version of jenkins prior to the 1.514 upgrade. 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] [jacoco] (JENKINS-16786) Please make the N/A white, not black. :-)
SCM/JIRA link daemon commented on JENKINS-16786 Please make the N/A white, not black. :-) Code changed in jenkins User: ognjenb Path: src/main/java/hudson/plugins/jacococoveragecolumn/JaCoCoColumn.java src/main/resources/hudson/plugins/jacococoveragecolumn/JaCoCoColumn/column.jelly src/test/java/hudson/plugins/jacococoveragecolumn/CoverageRangeTest.java src/test/java/hudson/plugins/jacococoveragecolumn/JaCoCoColumnTest.java http://jenkins-ci.org/commit/jacoco-plugin/a730ff0c1315f562bb026b5799450317d73a9bb0 Log: Merge pull request #22 from centic9/JENKINS-16786 JENKINS-16786: make coverage column show N/A as white, not black Compare: https://github.com/jenkinsci/jacoco-plugin/compare/b2fbab739fcc...a730ff0c1315 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] [jacoco] (JENKINS-16786) Please make the N/A white, not black. :-)
Matthew Harrah commented on JENKINS-16786 Please make the N/A white, not black. :-) +1 for option to enable/disable the column on the dashboard. 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] [jacoco] (JENKINS-16786) Please make the N/A white, not black. :-)
SCM/JIRA link daemon commented on JENKINS-16786 Please make the N/A white, not black. :-) Code changed in jenkins User: Dominik Stadler Path: src/main/java/hudson/plugins/jacococoveragecolumn/JaCoCoColumn.java src/main/resources/hudson/plugins/jacococoveragecolumn/JaCoCoColumn/column.jelly src/test/java/hudson/plugins/jacococoveragecolumn/CoverageRangeTest.java src/test/java/hudson/plugins/jacococoveragecolumn/JaCoCoColumnTest.java http://jenkins-ci.org/commit/jacoco-plugin/131a83673b8091d2c2575ddd60cf06982ee457d7 Log: JENKINS-16786: make N/A white, not black. Also enhance unit tests for coverage column classes 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] [promoted-builds] (JENKINS-18873) No way to delete promoted-builds from GUI
recampbell commented on JENKINS-18873 No way to delete promoted-builds from GUI Likewise, you can't see how much disk a promotion's 'workspace' is using. 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] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Justin Harringa edited a comment on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Is there any chance that this might get backported besides just providing the WAR? I noticed that you already marked it as an lts-candidate but it didn't make it into 1.509.2 and wasn't rejected either. 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] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Justin Harringa edited a comment on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Is there any chance that this might get backported besides just providing the WAR? I noticed that you already marked it as an lts-candidate but it didn't make it into 1.509.2 and wasn't rejected either. Our infra guys prefer installing via RPM. 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] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Justin Harringa commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Is there any chance that this might get back-ported besides just providing the WAR? I noticed that you already marked it as an lts-candidate but it didn't make it into 1.509.2 and wasn't rejected either. 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] [disk-usage] (JENKINS-13247) disk usage should not follow symlinks
evernat commented on JENKINS-13247 disk usage should not follow symlinks @Ben Golding I am not against a configuration option. Of course, it seems better if it "just works" without configuration (in all environments), but otherwise configuration is supposed to be better than a "bug". Most important is that you may need to submit a github pull request with working code in order to make it accepted by the plugin maintainer. 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.
