[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin
Raphael CHAUMIER started work on JENKINS-18467 Unable to deploy the ear file using weblogic-deployer-plugin Change By: Raphael CHAUMIER (25/Jun/13 7:22 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] [build-flow] (JENKINS-17906) Executor dies because of AssertionError
julian tragé commented on JENKINS-17906 Executor dies because of AssertionError Same problem on Windows (Server 2008 R2 ServicePack 1) with Jenkins as a service. Jenkins version: 1.500 and 1.509.1. And on a linux node (Unix slave, version 2.23) SUSE Linux Enterprise Server 11 (x86_64). Stacktrace (from Windows server, Master node): 24.06.2013 12:19:40 hudson.ExpressionFactory2$JexlExpression evaluate WARNUNG: Caught exception evaluating: job.lastSuccessfulBuild in /. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor100.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:283) at org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92) at $Proxy36.projectView(Unknown Source) at lib.JenkinsTagLib$projectView.call(Unknown Source) at hudson.model.View.main.run(main.groovy:14) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:66) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:59) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at
[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin
Raphael CHAUMIER
commented on JENKINS-18467
Unable to deploy the ear file using weblogic-deployer-plugin
Hi,
Due to a problem with my laptop, I couldn't release a new version of the plugin with the bug fix. Here is some workaround.
First : You can checkout git project (git://github.com/jenkinsci/weblogic-deployer-plugin.git), build it then load it manually on your jenkins
Second : The simplest one. Find into the plugin dir (plugins) the task.jelly file (WEB-INF/classes/org/jenkinsci/plugins/deploy/weblogic/data/DeploymentTask\task.jelly). Then replace the following part :
f:entry title="${%wl.configuration}"
f:entry title="${%wl.configuration.stage.mode}" field="stageMode"
select class="setting-input" name="stageMode"
j:forEach var="inst" items="${descriptor.weblogicStageModes}"
f:option value="${inst.name()}" selected="${inst.name() == it.stageMode.name()}" ${inst.name()}/f:option
/j:forEach
/select
/f:entry
/f:entry
By this one
f:entry title="${%wl.configuration}"
f:entry title="${%wl.configuration.stage.mode}" field="stageMode"
f:textbox default="stage" value="stage"/
/f:entry
/f:entry
I hope It will resolve your job creation issue until the next release
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] [artifactdeployer] (JENKINS-18401) java.lang.NoClassDefFoundError: hudson/maven/MavenReporter
Nicolas Phung updated JENKINS-18401 java.lang.NoClassDefFoundError: hudson/maven/MavenReporter Change By: Nicolas Phung (25/Jun/13 7:56 AM) Environment: Debian6,Jenkins1.519 Component/s: artifactdeployer Component/s: artifactory Component/s: maven2 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] [email-ext] (JENKINS-18474) Should be able to use token-macro to provide the recipient list
Timor Raiman
commented on JENKINS-18474
Should be able to use token-macro to provide the recipient list
I guess this was related to environment variables with dots in them (JENKINS-7180 not supported by design). So I was getting:
11:06:10 Sending email for trigger: Success
11:06:11 Sending email to: ${ENV var=br_env.MailTo}
11:06:13 Error sending to the following INVALID addresses: ${ENV var=br_env.MailTo}
This does work with normal variable names. So I'm getting rid of those dots..
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-18425) Build with parameters returns empty web page after upgrading to 1.519
Vlad Aginsky assigned JENKINS-18425 to IRCbot Run by Kohsuke Build with parameters returns empty web page after upgrading to 1.519 Change By: Vlad Aginsky (25/Jun/13 8:46 AM) Assignee: IRCbotRunbyKohsuke 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-18425) Build with parameters returns empty web page after upgrading to 1.519
Vlad Aginsky commented on JENKINS-18425 Build with parameters returns empty web page after upgrading to 1.519 Hi all, who should be assigned to 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] [build-blocker] (JENKINS-18482) Jenkins ver. 1.519 when run job white space comes
soner sivri created JENKINS-18482 Jenkins ver. 1.519 when run job white space comes Issue Type: Bug Assignee: Unassigned Components: build-blocker Created: 25/Jun/13 8:48 AM Description: Jenkins ver. 1.519 when run job white space comes /build?delay=0sec comes and nothing shown Project: Jenkins Priority: Major Reporter: soner sivri 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-18425) Build with parameters returns empty web page after upgrading to 1.519
Vlad Aginsky started work on JENKINS-18425 Build with parameters returns empty web page after upgrading to 1.519 Change By: Vlad Aginsky (25/Jun/13 8:48 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] [core] (JENKINS-18425) Build with parameters returns empty web page after upgrading to 1.519
Vlad Aginsky stopped work on JENKINS-18425 Build with parameters returns empty web page after upgrading to 1.519 Change By: Vlad Aginsky (25/Jun/13 8:49 AM) Status: InProgress Open 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-18331) Project modifaction fails because of serialization error
Alexey Khmelevskikh commented on JENKINS-18331 Project modifaction fails because of serialization error Please help! The problem is reproduced on Jenkins v. 1.519 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-14213) Projects that Trigger/call builds on other projects with the Block until ... finish their builds enabled will hang if the other project is disabled
evernat resolved JENKINS-14213 as Fixed Projects that Trigger/call builds on other projects with the Block until ... finish their builds enabled will hang if the other project is disabled This seems fixed to me. Using Jenkins 1.519 and the case given, I have the following log at the end of the build: Skipping x. The project is either disabled or the configuration has not been saved yet. Finished: SUCCESS Change By: evernat (25/Jun/13 9:15 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] [ci-game] (JENKINS-18483) Support of all violation plugin
Guillaume Kulakowski created JENKINS-18483 Support of all violation plugin Issue Type: Improvement Assignee: redsolo Components: ci-game Created: 25/Jun/13 9:21 AM Description: Hi, Violation provide plugin for a lot of lint. But CI Game doesn't support all. Project: Jenkins Priority: Major Reporter: Guillaume Kulakowski 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-18467) Unable to deploy the ear file using weblogic-deployer-plugin
Srikanth Tirukovalluru commented on JENKINS-18467 Unable to deploy the ear file using weblogic-deployer-plugin Hi, Thanks for your quick response. By following your second approach i could able to proceed further.Let me check how the deployment process will be. Thanks for your help. Srikanth.T 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-18331) Project modifaction fails because of serialization error
vyacheslav artyukhov updated JENKINS-18331 Project modifaction fails because of serialization error Change By: vyacheslav artyukhov (25/Jun/13 9:25 AM) Affects Version/s: current 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-18484) Add Grape @Grab support to flow-dsl plugin
Timor Raiman
created JENKINS-18484
Add Grape @Grab support to flow-dsl plugin
Issue Type:
New Feature
Assignee:
Nicolas De Loof
Components:
build-flow
Created:
25/Jun/13 11:02 AM
Description:
I'm running jobs based on the content of an external CSV file.
I would like to import a CVS library:
@Grab('com.xlson.groovycsv:groovycsv:1.0')
import static com.xlson.groovycsv.CsvParser.parseCsv
It would appear that a solution is available in the job-dsl plugin:
JENKINS-16361
Project:
Jenkins
Priority:
Major
Reporter:
Timor Raiman
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 created JENKINS-18485 Use fine grained permissions for node manipulation via rest api Issue Type: Improvement Assignee: Oliver Gondža Components: cli, core Created: 25/Jun/13 12:06 PM Description: Reading and updating configuration via $JENKINS/computer/$NODE/config.xml requires Jenkins.ADMINISTER permission. Dedicated permissions should be used instead. Project: Jenkins Priority: Major Reporter: Oliver Gondža 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] [postbuildscript] (JENKINS-11219) Add the option to run the script after all the sub elements of a matrix project build have finished
SCM/JIRA link daemon commented on JENKINS-11219 Add the option to run the script after all the sub elements of a matrix project build have finished Code changed in jenkins User: Nicolas De Loof Path: src/main/java/org/jenkinsci/plugins/postbuildscript/PostBuildScript.java http://jenkins-ci.org/commit/postbuildscript-plugin/0dc60fb4cac4d40a6ca29a408d0ff1b17b613358 Log: JENKINS-11219 don't run on matrix head if configured to run on matrix axes nodes. 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] [parameterized-trigger] (JENKINS-18486) When providing multiple jobs to run, support running them one after another and not all together
Eldad Assis created JENKINS-18486 When providing multiple jobs to run, support running them one after another and not all together Issue Type: New Feature Affects Versions: current Assignee: huybrechts Components: parameterized-trigger Created: 25/Jun/13 1:22 PM Description: When I set the "Projects to build" to a multiple list of jobs, I'd like the option to run them serialized and not parallel. A use case: I set the "Projects to build" to jobs A,B,C. Job B needs the output of an action from job A and C needs from A and B. Chaining them hard coded in not acceptable as the "Projects to build" chain is dynamic and is a parameter itself. Environment: All Project: Jenkins Priority: Minor Reporter: Eldad Assis 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] [dry] (JENKINS-18487) unable to parse Simian.xml
pernes olivier created JENKINS-18487 unable to parse Simian.xml Issue Type: Patch Affects Versions: current Assignee: Ulli Hafner Attachments: simian.xml Components: dry, pmd Created: 25/Jun/13 1:40 PM Description: trying to parse a simian xml log report with latest jenkins/DRY copy paste detector. the output is the following : DRY Parsing of file C:\JenkinsTFS\simian.xml failed due to an exception: java.io.IOException: No parser found for duplicated code results file C:\JenkinsTFS\simian.xml at hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:102) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:306) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:264) at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:215) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:184) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath.act(FilePath.java:905) at hudson.FilePath.act(FilePath.java:878) at hudson.plugins.dry.DryPublisher.perform(DryPublisher.java:175) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:146) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:331) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1618) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:242) Environment: trying to parse a simian xml log report with latest jenkins/DRY copy paste detector. Simian version: 2.3.34 Project: Jenkins Priority: Major Reporter: pernes olivier 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-18425) Build with parameters returns empty web page after upgrading to 1.519
sogabe commented on JENKINS-18425 Build with parameters returns empty web page after upgrading to 1.519 1 seems to cause this issue. 1 https://github.com/jenkinsci/jenkins/commit/84a259388c0a1a0d7e70b3d870c10f52e1205c8b 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-18488) TestSwarm plugin causing other plugins not to load in Manage Plugins screen(and elsewhere in the app)
Leo Laskin created JENKINS-18488 TestSwarm plugin causing other plugins not to load in Manage Plugins screen(and elsewhere in the app) Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Attachments: plugins_installed.txt Components: plugin, swarm Created: 25/Jun/13 1:53 PM Description: When having the TestSwarm plugin installed (jenkins-testswarm-plugin v 1.2), other plugins start throwing errors on the Manage Plugins page. When I delete the jenkins-testswarm-plugin folder and jenkins-testswarm-plugin.jpi, the errors disappear. Here is a list of plugins I normally have installed/configured: specifically the errors below: Exception: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.519.jar!/hudson/PluginManager/installed.jelly:70:56: j:include could not include jelly script: jar:file:/var/lib/jenkins/plugins/jenkins-testswarm-plugin/WEB-INF/lib/classes.jar!/index.jelly. Reason: org.apache.commons.jelly.JellyException: Could not parse Jelly script : jar:file:/var/lib/jenkins/plugins/jenkins-testswarm-plugin/WEB-INF/lib/classes.jar!/index.jelly Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.519.jar!/hudson/PluginManager/installed.jelly:70:56: j:include could not include jelly script: jar:file:/var/lib/jenkins/plugins/jenkins-testswarm-plugin/WEB-INF/lib/classes.jar!/index.jelly. Reason: org.apache.commons.jelly.JellyException: Could not parse Jelly script : jar:file:/var/lib/jenkins/plugins/jenkins-testswarm-plugin/WEB-INF/lib/classes.jar!/index.jelly at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:175) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at
[JIRA] [pmd] (JENKINS-18489) CPD parsing issue
pernes olivier created JENKINS-18489 CPD parsing issue Issue Type: Patch Affects Versions: current Assignee: Ulli Hafner Components: pmd Created: 25/Jun/13 1:54 PM Description: Issue while parsing a cpd log : (cannot join the file for privacy reason) CCM Parsing of file C:\JenkinsTFS\ccm2.xml failed due to an exception: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Octet 2 de la séquence UTF-8 à 3 octets non valide. at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.invalidByte(Unknown Source) at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1916) at hudson.plugins.ccm.parser.CcmParser.parse(CcmParser.java:93) at hudson.plugins.analysis.core.AbstractAnnotationParser.parse(AbstractAnnotationParser.java:53) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:306) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:264) at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:215) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:184) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath.act(FilePath.java:905) at hudson.FilePath.act(FilePath.java:878) at hudson.plugins.ccm.CcmPublisher.perform(CcmPublisher.java:101) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:146) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:331) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1618) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:242) Environment: latest Jenkins/CPD PMD plugin (23/06) Latest CPD/Pmd binary (23/06) Project: Jenkins Priority: Major Reporter: pernes olivier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see:
[JIRA] [scp] (JENKINS-18477) use a unique name to display for scp connections
sogabe commented on JENKINS-18477 use a unique name to display for scp connections "Display Name" has been implemented in https://github.com/jenkinsci/scp-plugin/commit/4162acc0c88ec7adf606aa7725e8db460c4c93b9. But not released yet. 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-18488) TestSwarm plugin causing other plugins not to load in Manage Plugins screen(and elsewhere in the app)
Leo Laskin updated JENKINS-18488 TestSwarm plugin causing other plugins not to load in Manage Plugins screen(and elsewhere in the app) Change By: Leo Laskin (25/Jun/13 1:57 PM) Description: Jenkinsinstalledbycopingthedownloadedwarovertheoldwarinthejenkinsfolder WhenhavingtheTestSwarmplugininstalled(jenkins-testswarm-pluginv1.2),otherpluginsstartthrowingerrorsontheManagePluginspage.WhenIdeletethejenkins-testswarm-pluginfolderandjenkins-testswarm-plugin.jpi,theerrorsdisappear.HereisalistofpluginsInormallyhaveinstalled/configured:specificallytheerrorsbelow:Exception:org.apache.commons.jelly.JellyTagException:jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.519.jar!/hudson/PluginManager/installed.jelly:70:56:lt;j:includegt;couldnotincludejellyscript:jar:file:/var/lib/jenkins/plugins/jenkins-testswarm-plugin/WEB-INF/lib/classes.jar!/index.jelly.Reason:org.apache.commons.jelly.JellyException:CouldnotparseJellyscript:jar:file:/var/lib/jenkins/plugins/jenkins-testswarm-plugin/WEB-INF/lib/classes.jar!/index.jellyStacktrace:javax.servlet.ServletException:org.apache.commons.jelly.JellyTagException:jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.519.jar!/hudson/PluginManager/installed.jelly:70:56:lt;j:includegt;couldnotincludejellyscript:jar:file:/var/lib/jenkins/plugins/jenkins-testswarm-plugin/WEB-INF/lib/classes.jar!/index.jelly.Reason:org.apache.commons.jelly.JellyException:CouldnotparseJellyscript:jar:file:/var/lib/jenkins/plugins/jenkins-testswarm-plugin/WEB-INF/lib/classes.jar!/index.jelly atorg.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:770) atorg.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:175) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:770) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:583) atorg.kohsuke.stapler.Stapler.service(Stapler.java:214) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:45) atwinstone.ServletConfiguration.execute(ServletConfiguration.java:248) atwinstone.RequestDispatcher.forward(RequestDispatcher.java:333) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) atwinstone.RequestDispatcher.forward(RequestDispatcher.java:331) atwinstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) atwinstone.RequestHandlerThread.run(RequestHandlerThread.java:150) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166)
[JIRA] [maven2] (JENKINS-18403) Jenkins 1.518 causes Java 5 Maven builds to fail
mirumpf commented on JENKINS-18403 Jenkins 1.518 causes Java 5 Maven builds to fail Our current workaround is to set the Maven compiler via command line: -Dmaven.compiler.executable=JDK5-javac 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-pipeline] (JENKINS-18490) Run button not work
Jorge Rodríguez Pedrianes created JENKINS-18490 Run button not work Issue Type: Bug Assignee: Unassigned Components: build-pipeline Created: 25/Jun/13 2:18 PM Description: Build Pipeline Plugin throw the next exception when I click in the run button: WARNING: Untrapped Error in Servlet org.kohsuke.stapler.ForwardToView at org.kohsuke.stapler.HttpResponses.forwardToView(HttpResponses.java:213) at hudson.model.BuildAuthorizationToken.checkPermission(BuildAuthorizationToken.java:87) at hudson.model.AbstractProject.doBuild(AbstractProject.java:1791) at au.com.centrumsystems.hudson.plugin.buildpipeline.DownstreamProjectGridBuilder$1.generateResponse(DownstreamProjectGridBuilder.java:172) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:105) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:63) at org.kohsuke.stapler.Function.renderResponse(Function.java:103) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:92) Thanks in advance, Environment: Jenkins: 1.519 Build Pipeline Plugini: 1.3.4.1 Project: Jenkins Priority: Major Reporter: Jorge Rodríguez Pedrianes 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-dsl-plugin] (JENKINS-18491) Add support for advanced project configuration and timeouts to DSL
Jens Hausherr created JENKINS-18491 Add support for advanced project configuration and timeouts to DSL Issue Type: New Feature Assignee: Jens Hausherr Components: job-dsl-plugin Created: 25/Jun/13 2:36 PM Description: The support for configuring advanced project options (like quiet time,...) and for timeouts is quite limited at the moment. The DSL should support all yet missing advanced project options that are available by default in Jenkins: Quiet period Retry Count (SCM) using custom workspaces Setting a display name for a Job Likewise the timeout configuration is limited to configuring absolute timeouts. It also should permit configuration of the "elastic" and "likelyStuck" mode. Project: Jenkins Priority: Minor Reporter: Jens Hausherr 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-dsl-plugin] (JENKINS-18491) Add support for advanced project configuration and timeouts to DSL
Jens Hausherr commented on JENKINS-18491 Add support for advanced project configuration and timeouts to DSL Also implemented a method for linking a project to a github project 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] [artifactdeployer] (JENKINS-18422) hudson/maven/MavenReporter Class Not Found exception when running a build
kepa uriarte reopened JENKINS-18422 hudson/maven/MavenReporter Class Not Found exception when running a build I'm having the same problem as described. It only happens at 1.519 version. Artifactory plugin makes jenkins crash. I need to use artifactory plugin. Change By: kepa uriarte (25/Jun/13 2:43 PM) Resolution: Duplicate Status: Resolved 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] [job-dsl-plugin] (JENKINS-18492) Inception: Create DSL build step to add DSL Job execution as step
Jens Hausherr created JENKINS-18492 Inception: Create DSL build step to add DSL Job execution as step Issue Type: New Feature Assignee: Justin Ryan Components: job-dsl-plugin Created: 25/Jun/13 2:55 PM Description: The DSL should be able to create Jobs that in turn execute DSL scripts. It would be useful to shorten the ramp-up time for setting up new projects when the DSL job used for initializing a projects jobs could also install a DSL job that in turn takes care of featur branch builds (or any similar use case) Project: Jenkins Priority: Minor Reporter: Jens Hausherr 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] [artifactdeployer] (JENKINS-18422) hudson/maven/MavenReporter Class Not Found exception when running a build
Sam Bernet edited a comment on JENKINS-18422 hudson/maven/MavenReporter Class Not Found exception when running a build Confirmed to occur on: Windows 7 Prof SP1 x64 VM JDK7 1.7.0_10-b18, 64-bit Server VM 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
Andrew Gallant commented on JENKINS-17876 MSBuild Command Line Arguments quotes being stripped...not 5552 Any idea when this will be available as an update? Thanks, AJ 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
Jonathan Zimmerman commented on JENKINS-17876 MSBuild Command Line Arguments quotes being stripped...not 5552 I'm not sure. I'll reach out to the maintainers to see if we can get this pulled in and released. 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
sogabe assigned JENKINS-17876 to Gregory Boissinot MSBuild Command Line Arguments quotes being stripped...not 5552 @gboissinot Would you merge pull/7 and release this plugin? Change By: sogabe (25/Jun/13 3:25 PM) Assignee: kdsweeney GregoryBoissinot 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] [svnmerge] (JENKINS-16723) NPE when performing integration.
Oscar Andreasson commented on JENKINS-16723 NPE when performing integration. I've had the same issue and investigated a little bit. Seems that ubuntu 12.04 and 11.10 uses svnkit 1.3.5 while 12.10 and 13.04 uses svnkit 1.7.5. Looking at the SVNException code in old svnkit, it does not check for null errorMessages, so it will throw an NPE exception. In newer svnkit, they actually check for null and handle it. Adding handling for null in this plugin is one way to go, or update your server software as a workaround 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] [warnings] (JENKINS-17794) Replace StyleCop parser with native parser
SCM/JIRA link daemon commented on JENKINS-17794 Replace StyleCop parser with native parser Code changed in jenkins User: Sebastian Seidl Path: src/main/java/hudson/plugins/warnings/parser/stylecop/StyleCopParser.java src/main/java/hudson/plugins/warnings/parser/stylecop/XmlElementUtil.java src/test/java/hudson/plugins/warnings/parser/StyleCopParserTest.java src/test/resources/hudson/plugins/warnings/parser/stylecop.xml http://jenkins-ci.org/commit/warnings-plugin/1d9c7c02915064974a5c06ce5e14b4b7066c65d8 Log: Resolved Issue: JENKINS-17794 Implementet Violations-StyleCopParser as Native-Parser. Implementet Test-File for StyleCopParser. 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] [warnings] (JENKINS-17075) Warnings Plugin Wind River Diab Compiler (C/C++)-parser is missing support for fatal errors
SCM/JIRA link daemon commented on JENKINS-17075 Warnings Plugin Wind River Diab Compiler (C/C++)-parser is missing support for fatal errors Code changed in jenkins User: Sebastian Seidl Path: .classpath src/main/java/hudson/plugins/warnings/parser/DiabCParser.java src/test/java/hudson/plugins/warnings/parser/DiabCParserTest.java src/test/resources/hudson/plugins/warnings/parser/diabc.txt http://jenkins-ci.org/commit/warnings-plugin/6a9c77bbafa05ed3e921b2884e9e34bd7b86449c Log: Fixed Issue JENKINS-17075: DiabCParser recognizes now a "fatal error". 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] [warnings] (JENKINS-17794) Replace StyleCop parser with native parser
SCM/JIRA link daemon commented on JENKINS-17794 Replace StyleCop parser with native parser Code changed in jenkins User: Sebastian Seidl Path: src/main/java/hudson/plugins/warnings/parser/stylecop/StyleCopParser.java src/main/java/hudson/plugins/warnings/parser/stylecop/XmlElementUtil.java src/test/java/hudson/plugins/warnings/parser/StyleCopParserTest.java src/test/resources/hudson/plugins/warnings/parser/stylecop.xml http://jenkins-ci.org/commit/warnings-plugin/6f36bc4e8af081503a9fe063698c0e7bce826059 Log: Resolved Issue: JENKINS-17794 Implementet Violations-StyleCopParser as Native-Parser. Implementet Test-File for StyleCopParser. 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] [warnings] (JENKINS-17075) Warnings Plugin Wind River Diab Compiler (C/C++)-parser is missing support for fatal errors
SCM/JIRA link daemon commented on JENKINS-17075 Warnings Plugin Wind River Diab Compiler (C/C++)-parser is missing support for fatal errors Code changed in jenkins User: Sebastian Seidl Path: .classpath src/main/java/hudson/plugins/warnings/parser/DiabCParser.java src/test/java/hudson/plugins/warnings/parser/DiabCParserTest.java src/test/resources/hudson/plugins/warnings/parser/diabc.txt http://jenkins-ci.org/commit/warnings-plugin/411af186120b2e4d5b04167121518e4c68ae5739 Log: Fixed Issue JENKINS-17075: DiabCParser recognizes now a "fatal error". 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] [mercurial] (JENKINS-10558) Jenkins mercurial plugin - add support for bookmarks
Igor Kostenko commented on JENKINS-10558 Jenkins mercurial plugin - add support for bookmarks When you are using repository caching bookmarks are lost because bundle doesn't support them 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] [dashboard-view] (JENKINS-15858) Jenkinks UI blocking on some calls / DEADLOCK
Vincent Massol updated JENKINS-15858 Jenkinks UI blocking on some calls / DEADLOCK FTR I still have a lot of performance issues with 1.519. I don't use the dashboard plugin anymore since I thought it was causing the issue but apparently it's not since I have hangs on almost all UI views. Very very frequently a view will take as much as 5 minutes before displying making our jenkins UI almost unusable (http://ci.xwiki.org). I've just taken a thread dump of jenkins when I tried to access http://ci.xwiki.org/job/xwiki-platform%20Quality%20Checks/569/ which took about 3 minutes to display, see attached jstack-vmassol-20130625.txt Change By: Vincent Massol (25/Jun/13 4:09 PM) Attachment: jstack-vmassol-20130625.txt 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-18425) Build with parameters returns empty web page after upgrading to 1.519
Kohsuke Kawaguchi assigned JENKINS-18425 to Kohsuke Kawaguchi Build with parameters returns empty web page after upgrading to 1.519 Change By: Kohsuke Kawaguchi (25/Jun/13 4:36 PM) Assignee: IRCbotRunby Kohsuke Kawaguchi 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-18493) Users unable to copy jobs without global read permissions
Timothy Forbes created JENKINS-18493 Users unable to copy jobs without global read permissions Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Jenkins System Properties.doc, jenkins_copy_job_screen1.png, jenkins_copy_job_screen2.png Components: core, security Created: 25/Jun/13 4:40 PM Description: While using the Project-based Matrix Authorization Strategy users are unable to create a new job unless global read is enabled. The global read permission is too liberal, allowing any authenticated user to see any job. The Create Job Advanced Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Create+Job+Advanced+Plugin) seems to fix this by granting users full permissions to jobs they create, however, it does not apply to duplicated jobs. When an authenticated user attempts to copy an existing job without global read permissions the resulting job fails to copy the existing values from the copied job. The user is then forwarded to a page that requests the user log in to see the newly created job. Expected behavior: A user is only able to copy jobs they have the ability to read and the resultant job should have the same permissions as the copied job. Environment: CentOS release 6.4, OpenJDK 1.6.0_24, x86_64, Project: Jenkins Labels: permissions job authentication Priority: Minor Reporter: Timothy Forbes 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-18425) Build with parameters returns empty web page after upgrading to 1.519
SCM/JIRA link daemon commented on JENKINS-18425 Build with parameters returns empty web page after upgrading to 1.519 Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/model/ParametersDefinitionProperty.java core/src/main/resources/hudson/model/ParametersDefinitionProperty/index.jelly http://jenkins-ci.org/commit/jenkins/56969828cd9814e1063c8a203349541b9f0c0f29 Log: FIXED JENKINS-18425 "201 Created" response doesn't work well with a browser as the user agent. 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-18425) Build with parameters returns empty web page after upgrading to 1.519
SCM/JIRA link daemon resolved JENKINS-18425 as Fixed Build with parameters returns empty web page after upgrading to 1.519 Change By: SCM/JIRA link daemon (25/Jun/13 5:04 PM) 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] [core] (JENKINS-18407) Starting a job with params using REST Api doesn't return 201 http status code as stated in the documentation
Kohsuke Kawaguchi assigned JENKINS-18407 to Kohsuke Kawaguchi Starting a job with params using REST Api doesnt return 201 http status code as stated in the documentation Change By: Kohsuke Kawaguchi (25/Jun/13 5:07 PM) Assignee: KohsukeKawaguchi 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-18407) Starting a job with params using REST Api doesn't return 201 http status code as stated in the documentation
Kohsuke Kawaguchi commented on JENKINS-18407 Starting a job with params using REST Api doesnt return 201 http status code as stated in the documentation To explain what's going on, 201 gets returned when the item gets submitted in the queue, and 302 if the item was already in the queue. I realize that in both cases it probably makes sense to return 201, even though in the latter case, technically we haven't created any resources. Most often, the caller doesn't really care if the submission resulted in a new item in the queue or if it was already in the queue. 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] [dashboard-view] (JENKINS-15858) Jenkinks UI blocking on some calls / DEADLOCK
Vincent Massol updated JENKINS-15858 Jenkinks UI blocking on some calls / DEADLOCK And 2 more thread dumps when UI views are slow to load: jstack-vmassol-20130625-2.txt jstack-vmassol-20130625-3.txt Change By: Vincent Massol (25/Jun/13 6:12 PM) Attachment: jstack-vmassol-20130625-2.txt Attachment: jstack-vmassol-20130625-3.txt 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] [avatar] (JENKINS-18494) Switch source code to GIT
Łukasz Jąder created JENKINS-18494 Switch source code to GIT Issue Type: Task Affects Versions: current Assignee: Unassigned Components: avatar Created: 25/Jun/13 6:25 PM Description: Project should switch to git and preferably github. It would made easier providing patches in form of Pull Requests. Project: Jenkins Labels: git, github scm, Priority: Major Reporter: Łukasz Jąder 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-18407) Starting a job with params using REST Api doesn't return 201 http status code as stated in the documentation
SCM/JIRA link daemon commented on JENKINS-18407 Starting a job with params using REST Api doesnt return 201 http status code as stated in the documentation Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/matrix/MatrixConfiguration.java core/src/main/java/hudson/matrix/listeners/MatrixBuildListener.java core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/model/Queue.java core/src/main/java/hudson/model/queue/ScheduleResult.java test/src/test/groovy/hudson/model/AbstractProjectTest.groovy http://jenkins-ci.org/commit/jenkins/f719bd06a46b0c8f8249f5d4848db61947b920be Log: FIXED JENKINS-18407 Added Queue.schedule2 to allow the caller to retrieve the existing item in the queue. AbstractProject.doBuild() changed the behavior a bit to reply 201 if the item was already found in the queue (instead of a new one created.) Compare: https://github.com/jenkinsci/jenkins/compare/bdfc3f715630...f719bd06a46b 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-18407) Starting a job with params using REST Api doesn't return 201 http status code as stated in the documentation
SCM/JIRA link daemon resolved JENKINS-18407 as Fixed Starting a job with params using REST Api doesnt return 201 http status code as stated in the documentation Change By: SCM/JIRA link daemon (25/Jun/13 6:28 PM) 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] [core] (JENKINS-18425) Build with parameters returns empty web page after upgrading to 1.519
dogfood commented on JENKINS-18425 Build with parameters returns empty web page after upgrading to 1.519 Integrated in jenkins_main_trunk #2658 FIXED JENKINS-18425 (Revision 56969828cd9814e1063c8a203349541b9f0c0f29) Result = SUCCESS kohsuke : 56969828cd9814e1063c8a203349541b9f0c0f29 Files : core/src/main/java/hudson/model/ParametersDefinitionProperty.java changelog.html core/src/main/resources/hudson/model/ParametersDefinitionProperty/index.jelly 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] [artifactdeployer] (JENKINS-18422) hudson/maven/MavenReporter Class Not Found exception when running a build
Kohsuke Kawaguchi resolved JENKINS-18422 as Duplicate hudson/maven/MavenReporter Class Not Found exception when running a build Closing this as a duplicate of JENKINS-18401 Change By: Kohsuke Kawaguchi (25/Jun/13 6:35 PM) Status: Reopened Resolved Assignee: KohsukeKawaguchi Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-16758) Cannot stop a build from custom plugin using interrupt
Eddie M
commented on JENKINS-16758
Cannot stop a build from custom plugin using interrupt
Here is an update on this issue. The issue ultimately is that the result gets set correctly but the build does not stop. To get around this issue I first had to override the setUpEnvironment method. Here I was able to check to see if the result was a failure and if so throw an IOException(Not InterruptException because it will set the result to aborted and I specifically want failure). Dirty but it is an improvement on what I originally had to force kill the build. So with that said I also changed my logic in the onStarted method to only set the result and use setUpEnvironment to only stop the build.
@Override
public Environment setUpEnvironment(AbstractBuild build, Launcher launcher,
BuildListener listener) throws IOException, InterruptedException {
if (build.getResult() != null build.getResult().isWorseOrEqualTo(Result.FAILURE)) {
build.getExecutor().interrupt(Result.FAILURE);
throw new IOException("Build failed");
}
return super.setUpEnvironment(build, launcher, listener);
}
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] [artifactdeployer] (JENKINS-18401) java.lang.NoClassDefFoundError: hudson/maven/MavenReporter
Kohsuke Kawaguchi
commented on JENKINS-18401
java.lang.NoClassDefFoundError: hudson/maven/MavenReporter
I looked into this and here's why this problem is happening.
In order to interact with Maven at some pretty deep level, Artifactory plugin puts a lot of jars into Maven's "plexus.core" classpath. It does this by putting every jar that the artifactory plugin bundles in its WEB-INF/lib folder. This can be seen in the following classworlds.conf file it uses, and the actual value of m3plugin.lib that it passes when it launches JVM, such as -Dm3plugin.lib=/var/lib/jenkins/plugins/artifactory/WEB-INF/lib:
main is org.apache.maven.cli.MavenCli from plexus.core
set maven.home default ${user.home}/m2
[plexus.core]
load ${maven.home}/lib/*.jar
load ${m3plugin.lib}/*.jar
Aside from dependency jars, Jenkins plugins have its own set of code. Historically, they were packaged in the WEB-INF/classes folder of the plugin, and therefore they were not added to the above classpath before.
However, as a part of JENKINS-15120, we changed this, and now the plugin source code gets compiled into WEB-INF/lib/classes.jar and {{WEB-INF/classes} is kept empty.While somewhat dubious, this by itself wasn't a fatal problem.
As a result, now the classes.jar from artifactory plugin gets added to plexus core classpath, and when Artifactory plugin's MavenReporter implementation gets loaded into Maven JVM via remoting, it ends up resolving to the one loaded in plexus.core, instead of the dynamic classloader created by Jenkins remoting. This fails to resolve the dependencies (MavenReporter) properly, and it chokes.
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-18495) f:entry with f:repeatable breaks java-script on root-action index.jelly
Magnus Sandberg
created JENKINS-18495
f:entry with f:repeatable breaks java-script on root-action index.jelly
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
25/Jun/13 7:17 PM
Description:
Using f:entry with f:repeatable on index.jelly for root-action creates _javascript_ Error:
This works:
j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form" xmlns:l="/lib/layout"
l:layout
l:main-panel
f:form method="post" name="submit" action="" class="code-quote">"submit"
f:repeatable var="pattern" items="${it.patterns}"
f:textbox /
/f:repeatable
f:submit /
/f:form
/l:main-panel
/l:layout
/j:jelly
but this:
j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form" xmlns:l="/lib/layout"
l:layout
l:main-panel
f:form method="post" name="submit" action="" class="code-quote">"submit"
f:repeatable var="pattern" items="${it.patterns}"
f:entry
f:textbox /
/f:entry
/f:repeatable
f:entry
f:submit /
/f:entry
/f:form
/l:main-panel
/l:layout
/j:jelly
Creates _javascript_ Error that breaks the page with:
"Uncaught TypeError: Cannot call method 'hasClassName' of undefined" in repeatable.js line 112.
Project:
Jenkins
Priority:
Blocker
Reporter:
Magnus Sandberg
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] [grails] (JENKINS-13252) Grails build step not finding grails
Gary Pinkham commented on JENKINS-13252 Grails build step not finding grails an old issue but I see it's unresolved and it's biting me today..I clicked install automatically as well but it doesn't do anything other than try to run grails.. also not sure how one sets home and path if Jenkins is doing the install.. but regardless I also tried to manually install grails and set the home and path in the server's bash profile.. of course tomcat doesn't run a shell so again not sure that helps.. 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] [grails] (JENKINS-13252) Grails build step not finding grails
Gary Pinkham edited a comment on JENKINS-13252 Grails build step not finding grails an old issue but I see it's unresolved and it's biting me today..I clicked install automatically as well but it doesn't do anything other than try to run grails.. also not sure how one sets home and path if Jenkins is doing the install.. but regardless I also tried to manually install grails and set the home and path in the server's bash profile.. of course tomcat doesn't run a shell so again not sure that helps.. edit I also tried setting the tools locations in the configuration (and the grails home env variable).. none of this helped.. 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] [svnmerge] (JENKINS-16723) NPE when performing integration.
chirag Patel commented on JENKINS-16723 NPE when performing integration. Hi Oscar I am using windows and try to use these plug in can you please let me know what software i need updatd. does these need to be updated on build server or subversion server. Thank you so much for your help Thx C 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
SCM/JIRA link daemon commented on JENKINS-17876 MSBuild Command Line Arguments quotes being stripped...not 5552 Code changed in jenkins User: Jonathan Zimmerman Path: src/main/java/hudson/plugins/msbuild/MsBuildBuilder.java src/test/java/hudson/plugins/msbuild/MsBuildBuilderTest.java http://jenkins-ci.org/commit/msbuild-plugin/11525049ed173f941d6ec6e87694269ef40d9920 Log: JENKINS-17876 Directly invoke QuotedStringTokenizer so quotes can be preserved in both the installation default args and the instance args. 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
SCM/JIRA link daemon commented on JENKINS-17876 MSBuild Command Line Arguments quotes being stripped...not 5552 Code changed in jenkins User: Gregory Boissinot Path: pom.xml src/main/java/hudson/plugins/msbuild/MsBuildBuilder.java src/test/java/hudson/plugins/msbuild/MsBuildBuilderTest.java http://jenkins-ci.org/commit/msbuild-plugin/0ae0e878b29ff22072286e65fc198f32a0cdb46c Log: Merge pull request #7 from tyrius02/master FIXED JENKINS-17876 Use QuotedStringTokenizer when constructing msbuild command-line arguments Compare: https://github.com/jenkinsci/msbuild-plugin/compare/dbf9ee71a1a5...0ae0e878b29f 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
SCM/JIRA link daemon resolved JENKINS-17876 as Fixed MSBuild Command Line Arguments quotes being stripped...not 5552 Change By: SCM/JIRA link daemon (25/Jun/13 8:20 PM) 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] [core] (JENKINS-18332) Builds disappear from the history of slave builds (both from the HDD and GUI)
Julia Kreger commented on JENKINS-18332 Builds disappear from the history of slave builds (both from the HDD and GUI) I'm seeing something very similar on 1.517 where all of the history and status for some, but not all jobs will just disappear. I have an identical server that has no build slaves where this issue has not been reported, however on a server that has multiple build slaves, and this is being encountered at least once a week, possibly twice a week much to my developer's frustrations. All slaves are JNLP launched. All hosts are Linux. OpenJDK 1.6. Build history files can be found on disk on the master, but are not listed in the gui. Jobs are configured to retain artifacts for 5 builds, and history for 20 builds. Matrix permissions are in use. ant credentials 1.4 cvs 2.8 email-ext 2.28 external monitor job 1.1 git 1.3.0 git-client 1.0.5 javadoc 1.1 jira 1.35 mailer 1.4 maven-plugin 1.512 pam-auth 1.0 ssh-credentials 0.3 ssh-slaves 0.25 jenkins translation 1.10 token-macro 1.6 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] [artifactdeployer] (JENKINS-18401) java.lang.NoClassDefFoundError: hudson/maven/MavenReporter
Kohsuke Kawaguchi commented on JENKINS-18401 java.lang.NoClassDefFoundError: hudson/maven/MavenReporter The artifactory plugin really shouldn't put such a large number of dependencies into the plexus.core classloader. If you look at the list, it includes such things like commons http, Jackson, Guava, XPP, JDOM, commons-logging, and etc. These jar files would be visible throughout Maven, and when a plugin attempts to load a conflicting version of one of the dependencies, they will end up picking up the version the artifactory plugin inserts. This can cause strange compatibility issues. To minimize the classpath contamination, it should insert minimal possible, which is just one class that implements org.apache.maven.AbstractMavenLifecycleParticipant, into the plexus.core realm. It should then create another realm as a child of the plexus.core realm, then load everything in there. The bridge class you insert into plexus.core should then delegate to the logic in the child realm. For the time being, I'm putting a quick fix to get us back on track, but I encourage the plugin maintainers to conside r these changes. 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] [artifactdeployer] (JENKINS-18401) java.lang.NoClassDefFoundError: hudson/maven/MavenReporter
SCM/JIRA link daemon commented on JENKINS-18401 java.lang.NoClassDefFoundError: hudson/maven/MavenReporter Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml http://jenkins-ci.org/commit/artifactory-plugin/5f49381b7088d0a7be72f98a739951454e9f09a3 Log: JENKINS-18401 jzlib that artifactory plugin inserts into plexus.core breaks the use of jzlib-1.1.2 in Jenkins 1.519. hudson.util.IOException2: java.lang.reflect.InvocationTargetException at hudson.maven.Maven3Builder.call(Maven3Builder.java:162) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.lang.Exception: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:177) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) ... 10 more Caused by: java.lang.reflect.InvocationTargetException 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:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:174) ... 11 more Caused by: java.lang.VerifyError: Cannot inherit from final class at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at java.lang.ClassLoader.defineClass(ClassLoader.java:480) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:289) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:229) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at com.jcraft.jzlib.GZIPOutputStream.init(GZIPOutputStream.java:46) at com.jcraft.jzlib.GZIPOutputStream.init(GZIPOutputStream.java:40) at com.jcraft.jzlib.GZIPOutputStream.init(GZIPOutputStream.java:36) at hudson.console.ConsoleNote.encodeToBytes(ConsoleNote.java:174) at hudson.console.ConsoleNote.encode(ConsoleNote.java:193) at hudson.maven.util.ExecutionEventLogger.mojoStarted(ExecutionEventLogger.java:277) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoStarted(Maven3Builder.java:409) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:84) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) ... 18 more Compare: https://github.com/jenkinsci/artifactory-plugin/compare/b6c0173531f4...5f49381b7088 This message is automatically
[JIRA] [artifactdeployer] (JENKINS-18401) java.lang.NoClassDefFoundError: hudson/maven/MavenReporter
SCM/JIRA link daemon commented on JENKINS-18401 java.lang.NoClassDefFoundError: hudson/maven/MavenReporter Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/org/jfrog/hudson/util/PluginDependencyHelper.java http://jenkins-ci.org/commit/artifactory-plugin/f7fa8d30bbf2bb79109538582821e1559e637c7a Log: FIXED JENKINS-18401 Don't load the plugin classes into plexus.core. This is a quick fix. See my comment in JENKINS-18401 for the proper fix 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] [artifactdeployer] (JENKINS-18401) java.lang.NoClassDefFoundError: hudson/maven/MavenReporter
SCM/JIRA link daemon resolved JENKINS-18401 as Fixed java.lang.NoClassDefFoundError: hudson/maven/MavenReporter Change By: SCM/JIRA link daemon (25/Jun/13 9:14 PM) 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] [pmd] (JENKINS-18489) CPD parsing issue
Ulli Hafner updated JENKINS-18489 CPD parsing issue Change By: Ulli Hafner (25/Jun/13 9:23 PM) Issue Type: Patch Bug 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] [dry] (JENKINS-18487) unable to parse Simian.xml
Ulli Hafner commented on JENKINS-18487 unable to parse Simian.xml Seems that you file does not contain valid UTF-8 characters: Caused by: org.apache.xerces.impl.io.MalformedByteSequenceException: Invalid byte 2 of 3-byte UTF-8 sequence. at org.apache.xerces.impl.io.UTF8Reader.invalidByte(Unknown Source) at org.apache.xerces.impl.io.UTF8Reader.read(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.scanLiteral(Unknown Source) at org.apache.xerces.impl.XMLScanner.scanAttributeValue(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanAttribute(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source) Can you please check if Simian is able to produce valid UTF-8 sequences? The directory names seem to conain some accents. 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] [warnings] (JENKINS-18290) cpplint.py outputs not handled by Warnings plugin
Ulli Hafner commented on JENKINS-18290 cpplint.py outputs not handled by Warnings plugin Thanks, that is sufficient. The regualar _expression_ needs to be improved to capture both formats... 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] [pmd] (JENKINS-18489) CPD parsing issue
Ulli Hafner resolved JENKINS-18489 as Not A Defect CPD parsing issue The stacktrace indicates a Ccm Parser as reason? This stacktrace is not from PMD. Change By: Ulli Hafner (25/Jun/13 9:25 PM) Status: Open Resolved Resolution: NotADefect 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-18467) Unable to deploy the ear file using weblogic-deployer-plugin
Raphael CHAUMIER resolved JENKINS-18467 as Fixed Unable to deploy the ear file using weblogic-deployer-plugin Fixed in 2.3 version Change By: Raphael CHAUMIER (25/Jun/13 10:26 PM) 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] [weblogic-deployer] (JENKINS-17879) Needs the ability to use Weblogic created keystore user and key files instead of having a plain-text administration password out in a config file
Raphael CHAUMIER resolved JENKINS-17879 as Fixed Needs the ability to use Weblogic created keystore user and key files instead of having a plain-text administration password out in a config file Added in 2.3 version Change By: Raphael CHAUMIER (25/Jun/13 10:25 PM) 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] [managed-scripts] (JENKINS-18496) Exception caused by quotes in the shebang line of shell scripts
Michael Vincent created JENKINS-18496 Exception caused by quotes in the shebang line of shell scripts Issue Type: Bug Assignee: domi Components: managed-scripts Created: 25/Jun/13 10:30 PM Description: Exception: executing script 'Post-SCM-git-submodule-update-and-clean' [Job] $ "C:\Program Files (x86)\Git\bin\bash.exe" -e C:\Users\HANDSE~1\AppData\Local\Temp\build_step_template2413741568138346591.sh FATAL: Caught exception while loading script 'Post-SCM-git-submodule-update-and-clean' java.lang.IllegalArgumentException: Executable name has embedded quote, split the arguments at java.lang.ProcessImpl.isQuoted(Unknown Source) at java.lang.ProcessImpl.getExecutablePath(Unknown Source) at java.lang.ProcessImpl.init(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:763) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:988) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:955) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) Build step 'Execute managed script' marked build as failure Contents of the managed script: #!"C:\Program Files (x86)\Git\bin\bash.exe" -e git fetch origin git submodule update --recursive --init git clean -ffdx git submodule foreach --recursive 'git clean -ffdx; git reset --hard' Java 7u21 has changed the way quotes are handled by Runtime.exec() on Windows: http://www.oracle.com/technetwork/java/javase/7u21-relnotes-1932873.html#jruntime Downgrading the slaves to Java 7u17 fixed the problem. I suppose I could have used PROGRA~2 instead of the quotes, but that's pretty ugly. I've placed this issue in the managed-scripts component because I haven't experienced the same issue with regular "Execute Shell" build steps. Environment: Jenkins LTS 1.509.1 Master on Linux, slaves on Windows 7 Slaves running JRE 7u21 Managed script plugin 1.1 Using bash from msysgit 1.8.0 Project: Jenkins Labels: exception windows Priority: Minor Reporter: Michael Vincent 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] [testng] (JENKINS-18498) TestNG reports not working on specific build.
Jose Ignacio Gonzalez De La Fuente created JENKINS-18498 TestNG reports not working on specific build. Issue Type: Bug Affects Versions: current Assignee: nalin_makar Components: testng Created: 25/Jun/13 10:56 PM Description: The TestNG Results button works fine if we use it on the job screen (where we can see all the different jobs) but if you open a job and click on the TestNG Results button it will end up on a webpage not available. On both places it appends this to the URL /testngreports/? This is the stack trace: WARNING: Untrapped Error in Servlet java.lang.RuntimeException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.518.jar!/lib/layout/layout.jelly:231:26: d:invokeBody org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.518.jar!/lib/layout/main-panel.jelly:36:21: d:invokeBody org.apache.commons.jelly.JellyTagException: hudson.tasks.test.AggregatedTestResultAction$1 cannot be cast to hudson.tasks.test.TestResult at org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:280) at org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92) at $Proxy61.layout(Unknown Source) at lib.LayoutTagLib$layout.call(Unknown Source) at hudson.plugins.testng.TestNGTestResultBuildAction.index.run(index.groovy:8) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:69) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:62) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55) at org.kohsuke.stapler.jelly.groovy.GroovyFacet.handleIndexRequest(GroovyFacet.java:117) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at
[JIRA] [scm-sync-configuration] (JENKINS-18500) SCM-Sync stops synchronising after deleting a job
Gavin Kingsley created JENKINS-18500 SCM-Sync stops synchronising after deleting a job Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 25/Jun/13 11:03 PM Description: Whenever a job is deleted, SCM sync can not synchronise the change. Trying to iron out the issues led me to JENKINS-18499. Environment: SCM Sync Plug in 0.0.7.1 Jenkins ver. 1.509.1 SVN Project: Jenkins Labels: plugin Priority: Major Reporter: Gavin Kingsley 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-18407) Starting a job with params using REST Api doesn't return 201 http status code as stated in the documentation
dogfood commented on JENKINS-18407 Starting a job with params using REST Api doesnt return 201 http status code as stated in the documentation Integrated in jenkins_main_trunk #2661 Result = UNSTABLE 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-18405) Findbugs plugin unable to run on slaves with 1.519
SCM/JIRA link daemon commented on JENKINS-18405 Findbugs plugin unable to run on slaves with 1.519 Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/RemoteClassLoader.java http://jenkins-ci.org/commit/remoting/b2836fc11916ef05e2513e74cefdefd225eff534 Log: JENKINS-18405 added diagnosis We'd like to know which class is failng to load. 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-18500) SCM-Sync stops synchronising after deleting a job
Frédéric Camblor closed JENKINS-18500 as Duplicate SCM-Sync stops synchronising after deleting a job Change By: Frédéric Camblor (26/Jun/13 12:16 AM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18394) IncompatibleClassChangeError after upgrade to 1.519
SCM/JIRA link daemon commented on JENKINS-18394 IncompatibleClassChangeError after upgrade to 1.519 Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/RemoteClassLoader.java http://jenkins-ci.org/commit/remoting/bb5aa9498d0461d9d59e785be52704be5f2ac179 Log: FIXED JENKINS-18394 As a part of the prefetching, Jenkins 1.519 parses classes and tries to discover other classes that the current class relies on. "IncompatibleClassChangeError: Implementing class" was encountered during such analysis phase. This is a real problem in FindBugs source tree, but the code in question is never getting exercised, which is why it was working OK. In this change, I made the prefetching analysis such that it will ignore the failures encounted during the reference analysis. I need to start testing plugins with cutting-edge Jenkins version to detect errors like this before it hits the users. Compare: https://github.com/jenkinsci/remoting/compare/b2836fc11916...bb5aa9498d04 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-15120) Minimize round trips for slave class loading
SCM/JIRA link daemon commented on JENKINS-15120 Minimize round trips for slave class loading Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/ResourceImageDirect.java http://jenkins-ci.org/commit/remoting/781ccaec2e26797bc8fa9e6c982a031988d381e0 Log: JENKINS-18405 This fixes the 'Unknown url shema' error in the FindBugs plugin. Before JENKINS-15120, we used to faithfully recreate the expected resource path in a temporary resource file. For some reasons, we lost that. This change brings it back by recreting the directory structure. Note that this change doesn't address "java.lang.IncompatibleClassChangeError: Implementing class" error reported also in JENKINS-18405. That is still under investigation. 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-18405) Findbugs plugin unable to run on slaves with 1.519
SCM/JIRA link daemon commented on JENKINS-18405 Findbugs plugin unable to run on slaves with 1.519 Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/ResourceImageDirect.java http://jenkins-ci.org/commit/remoting/781ccaec2e26797bc8fa9e6c982a031988d381e0 Log: JENKINS-18405 This fixes the 'Unknown url shema' error in the FindBugs plugin. Before JENKINS-15120, we used to faithfully recreate the expected resource path in a temporary resource file. For some reasons, we lost that. This change brings it back by recreting the directory structure. Note that this change doesn't address "java.lang.IncompatibleClassChangeError: Implementing class" error reported also in JENKINS-18405. That is still under investigation. 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-18394) IncompatibleClassChangeError after upgrade to 1.519
SCM/JIRA link daemon resolved JENKINS-18394 as Fixed IncompatibleClassChangeError after upgrade to 1.519 Change By: SCM/JIRA link daemon (26/Jun/13 1:24 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] [core] (JENKINS-18405) Findbugs plugin unable to run on slaves with 1.519
Kohsuke Kawaguchi resolved JENKINS-18405 as Fixed Findbugs plugin unable to run on slaves with 1.519 "java.lang.IncompatibleClassChangeError: Implementing class" is tracked in JENKINS-18394. Therefore commit 781ccaec resolves this issue. Change By: Kohsuke Kawaguchi (26/Jun/13 1:25 AM) Status: Open Resolved Assignee: UlliHafner KohsukeKawaguchi 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] [core] (JENKINS-18405) Findbugs plugin unable to run on slaves with 1.519
Kohsuke Kawaguchi commented on JENKINS-18405 Findbugs plugin unable to run on slaves with 1.519 The fix is targeted to 1.521. 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] [groovy] (JENKINS-18349) Allow to use @Grab in a Script Console
SCM/JIRA link daemon commented on JENKINS-18349 Allow to use @Grab in a Script Console Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html pom.xml http://jenkins-ci.org/commit/jenkins/2ad427f6c3d187c5b330151b85e1a578e340cf2a Log: FIXED JENKINS-18349 JENKINS-18405 Integrated the fix toward 1.521. Compare: https://github.com/jenkinsci/jenkins/compare/0b8917b34479...2ad427f6c3d1 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-18405) Findbugs plugin unable to run on slaves with 1.519
SCM/JIRA link daemon commented on JENKINS-18405 Findbugs plugin unable to run on slaves with 1.519 Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html pom.xml http://jenkins-ci.org/commit/jenkins/2ad427f6c3d187c5b330151b85e1a578e340cf2a Log: FIXED JENKINS-18349 JENKINS-18405 Integrated the fix toward 1.521. Compare: https://github.com/jenkinsci/jenkins/compare/0b8917b34479...2ad427f6c3d1 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-18405) Findbugs plugin unable to run on slaves with 1.519
dogfood commented on JENKINS-18405 Findbugs plugin unable to run on slaves with 1.519 Integrated in jenkins_main_trunk #2663 FIXED JENKINS-18349 JENKINS-18405 (Revision 2ad427f6c3d187c5b330151b85e1a578e340cf2a) Result = SUCCESS kohsuke : 2ad427f6c3d187c5b330151b85e1a578e340cf2a Files : pom.xml changelog.html 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] [fitnesse] (JENKINS-18501) Fitnesse Plugin - java.net.SocketTimeoutException: Read timed out
Sam Jessop
created JENKINS-18501
Fitnesse Plugin - java.net.SocketTimeoutException: Read timed out
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
fitnesse
Created:
26/Jun/13 3:02 AM
Description:
We get this socket timeout the odd occasion, as you can see we have tried setting the HttpTimeout to a big number but it doesn't seem to help.
12:59:36 hudson.plugins.fitnesse.FitnesseBuilder: {fitnesseTargetPage=PayrollTeam.ModulePayroll.AaTaxArea.NewZealandTax, fitnesseTargetIsSuite=true, fitnesseHost=Private, fitnesseHttpTimeout=270, fitnessePortRemote=8886, fitnesseStart=False, fitnessePathToXmlResultsOut=C:\PayGlobal\FitNesse\Results\XESuiteNZTax_Results.xml}
12:59:36 Connnecting to http://PAYFIT003:8886/PayrollTeam.ModulePayroll.AaTaxArea.NewZealandTax?suiteformat=xmlincludehtml
12:59:36 Connected: 200/OK
13:44:46 java.net.SocketTimeoutException: Read timed out
13:44:46 at java.net.SocketInputStream.socketRead0(Native Method)
13:44:46 at java.net.SocketInputStream.read(Unknown Source)
13:44:46 at java.net.SocketInputStream.read(Unknown Source)
13:44:46 at java.io.BufferedInputStream.fill(Unknown Source)
13:44:46 at java.io.BufferedInputStream.read1(Unknown Source)
13:44:46 at java.io.BufferedInputStream.read(Unknown Source)
13:44:46 at sun.net.www.http.ChunkedInputStream.readAheadBlocking(Unknown Source)
13:44:46 at sun.net.www.http.ChunkedInputStream.readAhead(Unknown Source)
13:44:46 at sun.net.www.http.ChunkedInputStream.read(Unknown Source)
13:44:46 at java.io.FilterInputStream.read(Unknown Source)
13:44:46 at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(Unknown Source)
13:44:46 at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(Unknown Source)
13:44:46 at hudson.plugins.fitnesse.FitnesseExecutor.getHttpBytes(FitnesseExecutor.java:230)
13:44:46 at hudson.plugins.fitnesse.FitnesseExecutor$1.run(FitnesseExecutor.java:201)
13:44:46 at java.lang.Thread.run(Unknown Source)
I've had a quick look at the code and I'm pretty sure this is where it is crashing:
try {
log.println("Connnecting to " + pageCmdTarget);
HttpURLConnection connection = (HttpURLConnection) pageCmdTarget.openConnection();
connection.setReadTimeout(httpTimeout);
log.println("Connected: " + connection.getResponseCode() + "/" + connection.getResponseMessage());
inputStream = connection.getInputStream();
long recvd = 0, lastLogged = 0;
byte[] buf = new byte4096;
int lastRead;
while ((lastRead = inputStream.read(buf)) 0) {
bucket.write(buf, 0, lastRead);
timeout.reset();
recvd += lastRead;
if (recvd - lastLogged 1024) {
log.println(recvd/1024 + "k...");
lastLogged = recvd;
}
}
} catch (IOException e) {
// this may be a "premature EOF" caused by e.g. incorrect content-length HTTP header
// so it may be non-fatal -- try to recover
e.printStackTrace(log);
} finally {
if (inputStream != null) {
try {
inputStream.close();
} catch (Exception e) {
// swallow
}
}
}
I'm not very good with networking code so would someone please be able to look at this for me and see if there is an issue or suggest something environmentally we could do to avoid these timeouts?
Cheers,
Sam
Project:
Jenkins
Priority:
Major
Reporter:
Sam Jessop
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see:
[JIRA] [fitnesse] (JENKINS-18501) Fitnesse Plugin - java.net.SocketTimeoutException: Read timed out
Sam Jessop commented on JENKINS-18501 Fitnesse Plugin - java.net.SocketTimeoutException: Read timed out Hey all, me and another developer here have been looking into this further and we see that there is only 1 variable used for the httpTimeout and the tests timeout. This is not good in our case as it may take 45 minutes to run a test (big reports) but it also means it will take 45 minutes for the test to fail if the http fails to connect and timeout. Also it doesn't seem to retry to connect if it fails to connect the first time? 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.
