[JIRA] [ldap] (JENKINS-24704) LDAP restrict requested User attributes
Marco Jacob updated JENKINS-24704 LDAP restrict requested User attributes As far as I can see from my point of view, the LdapTemplate has a list of of attributes for the request. It could be modified before a request is done. Now it is set to NULL which indicates to request all attributes. LdapTemplate is bound to the AppContext, so it is used for each request. Therefore it should be explizitly set before a request is done. That would be an easy solution. The list of attributes could be given in settings with a default (e.g. uid). I'm affraid I can't do the change on my own at work ... some resources missing and no chance to create a PR. This could be done for user and usergroup requests. 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/d/optout.
[JIRA] [ldap] (JENKINS-24704) LDAP restrict requested User attributes
Marco Jacob edited a comment on JENKINS-24704 LDAP restrict requested User attributes As far as I can see from my point of view, the LdapTemplate has a list of of attributes for the request. It could be modified before a request is done. Now it is set to NULL which indicates to request all attributes. LdapTemplate is bound to the AppContext, so it is used for each request. Therefore it should be explicitly set before a request is done. That would be an easy solution. The list of attributes could be given in settings with a default (e.g. uid). I'm affraid I can't do the change on my own at work ... some resources missing and no chance to create a PR. This could be done for user and usergroup requests. 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/d/optout.
[JIRA] [ldap] (JENKINS-24704) LDAP restrict requested attributes
Marco Jacob updated JENKINS-24704 LDAP restrict requested attributes Changed title because also group attribute requests could be restricted. Change By: Marco Jacob (18/Sep/14 6:44 AM) Summary: LDAPrestrictrequested User attributes 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/d/optout.
[JIRA] [pretested-integration] (JENKINS-24754) Add Support for named repositories, required for multiple scm selections
Mads Nielsen created JENKINS-24754 Add Support for named repositories, required for multiple scm selections Issue Type: New Feature Assignee: Praqma Support Components: pretested-integration Created: 18/Sep/14 7:01 AM Project: Jenkins Priority: Major Reporter: Mads Nielsen 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/d/optout.
[JIRA] [accelerated-build-now] (JENKINS-24755) Caught exception evaluating: it.killerBuildUrl
herve_colliaux created JENKINS-24755 Caught exception evaluating: it.killerBuildUrl Issue Type: Bug Assignee: Anthony Dahanne Components: accelerated-build-now Created: 18/Sep/14 7:08 AM Description: sept. 18, 2014 8:52:47 AM AVERTISSEMENT hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: it.killerBuildUrl in /job/AMR-meter/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.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._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsString(ExpressionSupport.java:46) at org.apache.commons.jelly._expression_.CompositeExpression.evaluateAsString(CompositeExpression.java:256) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.buildAttributes(ReallyStaticTagLibrary.java:111) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) 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.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.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.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) 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.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) 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$2.run(CoreTagLibrary.java:105) at
[JIRA] [core] (JENKINS-24215) Viewing Workspace or Last Successful Artifacts links throws an exception
Dennis Wagelaar commented on JENKINS-24215 Viewing Workspace or Last Successful Artifacts links throws an exception Happened to us as well on Jenkins 1.577, Oracle JDK 1.7.0_67. Jenkins restart did not resolve the problem. N.B. We cannot see slave workspaces, only master workspaces! Slave runs via JNLP (slave.jar), which is updated to the version that ships with the Jenkins master. Only happens for accessing workspace; last artifacts display fine. Also, I manually deleted a workspace from the slave. After running the job again, the workspace could still not be displayed (workspace did exist on filesystem). 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/d/optout.
[JIRA] [core] (JENKINS-24458) SomeAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
herve_colliaux edited a comment on JENKINS-24458 SomeAction doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions I had also this issue on Windows 7 with Jenkins 1.580. resolved by deactivating EzWall plugin. In fact, deactivating it seems not necessary. Just stopping displaying this wall ... 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/d/optout.
[JIRA] [security] (JENKINS-14313) login page redirects to login page
christoph Forster commented on JENKINS-14313 login page redirects to login page Another workaround without touching the Keyboard: I click on the Jenkins Logo which also replaces http://localhost:8080/jenkins/login?from=%2Fjenkins with http://localhost:8080/jenkins/login?from=%2Fjenkins%2F Then the Login works. 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/d/optout.
[JIRA] [core] (JENKINS-24458) SomeAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Craig Phillips commented on JENKINS-24458 SomeAction doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions Do you know what release the logging change is scheduled for? 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/d/optout.
[JIRA] [ldap] (JENKINS-24756) LDAP No unbind after request
Marco Jacob created JENKINS-24756 LDAP No unbind after request Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ldap Created: 18/Sep/14 8:15 AM Description: LDAP Plugin does BIND requests but is missing UNBIND. So there are several bound connections not released until timeout. Environment: LDAP-Plugin 1.10.2, Jenkins 1.532.1 Project: Jenkins Labels: plugin ldap unbind Priority: Minor Reporter: Marco Jacob 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/d/optout.
[JIRA] [core] (JENKINS-24215) Viewing Workspace or Last Successful Artifacts links throws an exception
Dennis Wagelaar edited a comment on JENKINS-24215 Viewing Workspace or Last Successful Artifacts links throws an exception Happened to us as well on Jenkins 1.577, Oracle JDK 1.7.0_67. Jenkins restart did not resolve the problem. N.B. We cannot see slave workspaces, only master workspaces! Slave runs via JNLP (slave.jar), which is updated to the version that ships with the Jenkins master. Only happens for accessing workspace; last artifacts display fine. Also, I manually deleted a workspace from the slave. After running the job again, the workspace could still not be displayed (workspace did exist on filesystem). EDIT: after a slave server reboot, and a rebuild, we could view the workspaces again. 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/d/optout.
[JIRA] [core] (JENKINS-24215) Viewing Workspace or Last Successful Artifacts links throws an exception
Dennis Wagelaar edited a comment on JENKINS-24215 Viewing Workspace or Last Successful Artifacts links throws an exception Happened to us as well on Jenkins 1.577, Oracle JDK 1.7.0_67. Jenkins restart did not resolve the problem. N.B. We cannot see slave workspaces, only master workspaces! Slave runs via JNLP (slave.jar), which is updated to the version that ships with the Jenkins master. Only happens for accessing workspace; last artifacts display fine. Also, I manually deleted a workspace from the slave. After running the job again, the workspace could still not be displayed (workspace did exist on filesystem). EDIT: after a slaver server reboot, and a rebuild, we could view the workspaces again. 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/d/optout.
[JIRA] [core] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
Adam commented on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave hey Trevor, any chance you have the update to 3.4.x kernel steps handy. I didn't see the kernel in the main repo. Anyone from the Jenkins team able to comment if they could help resolve this issue? I leave ssh sessions open overnight with no issues or drops, so I really can't understand why jenkins keeps having these ping timeouts.Could we get a patch which would disable the ping check entirely? I added "-Dhudson.remoting.Launcher.pingIntervalSec=0 -Dhudson.remoting.Launcher.pingTimeoutSec=0" to my startup on the master but it didn't seem to help. Would appreciate any suggestion to avoid rolling back the kernel. Trevor, It would be interesting to see the output before/after the rollback of "sysctl -a", wonder if there's a kernel param that changed which might have an impact. 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/d/optout.
[JIRA] [build-pipeline] (JENKINS-15957) All build executors permanently Dead!
mgy tdxmgy commented on JENKINS-15957 All build executors permanently Dead! Sep 18, 2014 4:06:19 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: item.isStuck() in /view/Z2_SISLEY/ajaxBuildQueue. Reason: java.lang.ArrayIndexOutOfBoundsException: Assertion error: fa iling to load #123 DESC: lo=18,hi=16,size=18,size2=18 java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #123 DESC: lo=18,hi=16,size=18,size2=18 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:442) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:220) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:103) at hudson.model.Job.getLastBuildsOverThreshold(Job.java:887) at hudson.model.Job.getEstimatedDuration(Job.java:894) at hudson.model.Queue$BuildableItem.isStuck(Queue.java:1654) at sun.reflect.GeneratedMethodAccessor734.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) 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.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.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.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) 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.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java: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.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.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) 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] [build-pipeline] (JENKINS-15957) All build executors permanently Dead!
mgy tdxmgy commented on JENKINS-15957 All build executors permanently Dead! My version is Jenkins ver. 1.509.1,I met master and many slaves dead,except slaves which ar running jobs.Do you know how to resloved this for ever? It's OK when I restart jenkins . 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/d/optout.
[JIRA] [promoted-builds] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Chris Engel commented on JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. Is it possible to set the Priority up? Would be nice, if it is fixed in the near future. 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/d/optout.
[JIRA] [core] (JENKINS-24458) SomeAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Daniel Beck commented on JENKINS-24458 SomeAction doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions 1.582 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/d/optout.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Craig Phillips commented on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) I am looking at this issue and trying to build the plugin. I am seeing the following maven errors, can you help? WARNING The POM for org.apache.maven:maven-plugin-api:jar:3.0.3 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details ... INFO maven-hpi-plugin:1.74:test-hpl (default-test-hpl) @ cppcheck INFO Generating /var/lib/jenkins/jobs/jenkinsci-cppcheck-plugin/workspace/target/test-classes/the.hpl INFO INFO BUILD FAILURE INFO INFO Total time: 5.706s INFO Finished at: Thu Sep 18 10:06:49 BST 2014 INFO Final Memory: 24M/347M INFO Waiting for Jenkins to finish collecting data ERROR Failed to execute goal org.jenkins-ci.tools:maven-hpi-plugin:1.74:test-hpl (default-test-hpl) on project cppcheck: Error preparing the manifest: Failed to open artifact org.apache.maven:maven-plugin-api:jar:3.0.3:test at /var/lib/jenkins/.m2/repository/org/apache/maven/maven-plugin-api/3.0.3/maven-plugin-api-3.0.3.jar: 1 problem was encountered while building the effective model ERROR FATAL Non-parseable POM /var/lib/jenkins/.m2/repository/org/apache/maven/maven-plugin-api/3.0.3/maven-plugin-api-3.0.3.pom: only whitespace content allowed before start tag and not 0 (position: START_DOCUMENT seen 0... @1:1) @ line 1, column 1 ERROR for project for project ERROR - Help 1 ERROR ERROR To see the full stack trace of the errors, re-run Maven with the -e switch. ERROR Re-run Maven using the -X switch to enable full debug logging. ERROR ERROR For more information about the errors and possible solutions, please read the following articles: ERROR Help 1 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException 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/d/optout.
[JIRA] [groovy] (JENKINS-23617) Cannot use spaces in groovy script parameters
Daniel Beck commented on JENKINS-23617 Cannot use spaces in groovy script parameters Jira is not a support site. Please ask in #jenkins on Freenode, or on the jenkinsci-users mailing list. 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/d/optout.
[JIRA] [customtools-plugin] (JENKINS-14515) Malformed PATH environment variable on Windows slave (unix syntax used)
Oleg Nenashev commented on JENKINS-14515 Malformed PATH environment variable on Windows slave (unix syntax used) The functionality has been broken in https://github.com/jenkinsci/customtools-plugin/commit/1ed68b4a65642113f4a61da08aa5f2e4da5d5b4b (0.4.1). I'll fix the regression 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/d/optout.
[JIRA] [groovy] (JENKINS-24757) Allow spaces in script parameters
vjuranek created JENKINS-24757 Allow spaces in script parameters Issue Type: New Feature Assignee: vjuranek Components: groovy Created: 18/Sep/14 9:25 AM Description: Similar to JENKINS-23617, allow parameters also in Script parameters option Project: Jenkins Priority: Major Reporter: vjuranek 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/d/optout.
[JIRA] [groovy] (JENKINS-23617) Cannot use spaces in groovy script parameters
vjuranek commented on JENKINS-23617 Cannot use spaces in groovy script parameters @nigel_charman: there are two parameters options, Groovy parameters - parameter for groovy executable and Script parameters - parameters for script. It was implemented only for the first one, Groovy parameters. I've created JENKINS-24757 for allowing spaces also in Script parameters. 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/d/optout.
[JIRA] [github-oauth] (JENKINS-23324) GitHub OAuth 0.17 requires private access to all repositories
Matthew Mead-Briggs commented on JENKINS-23324 GitHub OAuth 0.17 requires private access to all repositories This is a real problem for us too. I've forked the repo, and made this change for now: https://github.com/mattmb/github-oauth-plugin/compare/jenkinsci:master...master But this should really be fixed properly. For those that don't need the repo functionality they shouldn't have to give that permission. 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/d/optout.
[JIRA] [core] (JENKINS-11078) NullPointerException in hudson.maven.Maven3Builder$MavenExecutionListener.recordProjectStarted
SCM/JIRA link daemon commented on JENKINS-11078 NullPointerException in hudson.maven.Maven3Builder$MavenExecutionListener.recordProjectStarted Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/maven/Maven3Builder.java http://jenkins-ci.org/commit/maven-plugin/6e44d072bd5048ecae2b9ad9f99d90c5844ce913 Log: JENKINS-11078 prevent NPE 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/d/optout.
[JIRA] [ircbot] (JENKINS-24685) When a build fails, and IRC Notification is set up as a Post-build Action, the build is marked SUCCESS instead of FAILED
kutzi resolved JENKINS-24685 as Not A Defect When a build fails, and IRC Notification is set up as a Post-build Action, the build is marked SUCCESS instead of FAILED No feedback from reporter. Probably a misconfiguration in the previous buildstep, so not related to ircbot at all. Change By: kutzi (18/Sep/14 9:50 AM) 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/d/optout.
[JIRA] [jclouds] (JENKINS-15820) JClouds plugin deadlock
SCM/JIRA link daemon commented on JENKINS-15820 JClouds plugin deadlock Code changed in jenkins User: Kei YAMAZAKI Path: jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsRetentionStrategy.java http://jenkins-ci.org/commit/jclouds-plugin/34820cebf612d0975acd91e2fc44c1cdc385c8d0 Log: JENKINS-15820 Fix NPE 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/d/optout.
[JIRA] [jclouds] (JENKINS-15820) JClouds plugin deadlock
SCM/JIRA link daemon commented on JENKINS-15820 JClouds plugin deadlock Code changed in jenkins User: Marat Mavlyutov Path: jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsRetentionStrategy.java http://jenkins-ci.org/commit/jclouds-plugin/700644c1bd6d99953042d1a78791b180b1e816d8 Log: Merge pull request #73 from kei-yamazaki/avoid-deadlock JENKINS-15820 Fix NPE Compare: https://github.com/jenkinsci/jclouds-plugin/compare/aba2ef847edb...700644c1bd6d 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/d/optout.
[JIRA] [core] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
Guillaume Boucherie updated JENKINS-14332 Repeated channel/timeout errors from Jenkins slave Hi, First thanks you very much for this tips. And yes current Amazon Linux AMI (ami-892fe1fe) can't be downgraded to 3.4.x. So i install an Ubuntu 12.04 that come with a 3.2.x kernel (ami-00d12677) and all works fine. I also try with an ubuntu 14.04 (3.13.x kernel) and its not good. So I attach the result of "sysctl -a" for kernel 3.2 sysctl_3.2.txt and 3.13 sysctl_3.13.txt if it could help. Regards Change By: Guillaume Boucherie (18/Sep/14 9:58 AM) Attachment: sysctl_3.2.txt Attachment: sysctl_3.13.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/d/optout.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Craig Phillips commented on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) It's okay, I figured it out. I had previously run maven with the wrong settings file and it mis-configured its local repo. I removed the repo (/var/lib/jenkins/.m2/repository) and repeated the build and it worked fine. 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/d/optout.
[JIRA] [discard-old-build] (JENKINS-24072) Should allow to set global defaults retention policy for all jobs
Aviv Yam commented on JENKINS-24072 Should allow to set global defaults retention policy for all jobs I agree. Something thing like Jenkins Environment variables.. 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/d/optout.
[JIRA] [valgrind] (JENKINS-13745) Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception
Johannes Ohlemacher commented on JENKINS-13745 Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception @Artem: you are welcome I am worried about performance too, its on my todo list since quite some time. I have a lot on my plate right now, so this has to wait a few more weeks. 250Mb of valgrind reports seems like a challenging test case 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/d/optout.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Craig Phillips commented on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) I have noticed another "bug" recently. If you set the maximum new error threshold to 1 and you have a build where one new error is added, but at the same time, one is resolve, the delta is zero but the build is flagged as stable. This doesn't seem right. 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/d/optout.
[JIRA] [disk-usage] (JENKINS-14872) disk-usage-plugin: Calculating disk usage is causing very high I/O
Lucie Votypkova commented on JENKINS-14872 disk-usage-plugin: Calculating disk usage is causing very high I/O Hi, now I am dealing with performance issue on big instances. There are problem with lazy loading - I have to cashed size of builds from previous versions, but they are saved in build.xml (so I have to load every build). In big instances with 1 jobs and about 8 builds it causes deadlock. When I solve this serious issue I will look at your suggestions. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23929) Cannot use 'WORKSPACE' variable when creating custom workspace to *modify* the auto-generated workspace
Phil Rutherford commented on JENKINS-23929 Cannot use WORKSPACE variable when creating custom workspace to *modify* the auto-generated workspace @Rob: We run the P4QUICKCLEANWORKSPACE in overnight clean jobs to ensure the workspaces are clean during the day and there are no leftover unused files that make their way into client deliveries. The incremental CI builds that occur throughout the day do not clean the workspace, that would take far too long for each build. Our builds involve over 80Gb per branch consisting of tens of thousands of files and many many build scripts. Ensure these are always perfect and never leave any unused files behind would be impossible. The short answer is that we need to use branches and we need P4QUICKCLEANWORKSPACE to work. @Morne: Yes, we also don't use the '@' separator as it causes trouble with platform specific tools. You can replace it when you launch Jenkins, e.g.: %JAVA% -Dhudson.slaves.WorkspaceList=_ -jar jenkins.war The changes I made do adhere to this convention. 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/d/optout.
[JIRA] [core] (JENKINS-11078) NullPointerException in hudson.maven.Maven3Builder$MavenExecutionListener.recordProjectStarted
SCM/JIRA link daemon commented on JENKINS-11078 NullPointerException in hudson.maven.Maven3Builder$MavenExecutionListener.recordProjectStarted Code changed in jenkins User: Olivier Lamy Path: src/main/java/hudson/maven/Maven3Builder.java http://jenkins-ci.org/commit/maven-plugin/6e8c99da29f60177dd8e14771c3f344871383773 Log: Merge pull request #30 from jenkinsci/JENKINS-11078 JENKINS-11078 prevent NPE Compare: https://github.com/jenkinsci/maven-plugin/compare/0f964451d8e9...6e8c99da29f6 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/d/optout.
[JIRA] [disk-usage] (JENKINS-14872) disk-usage-plugin: Calculating disk usage is causing very high I/O
Kanstantsin Shautsou commented on JENKINS-14872 disk-usage-plugin: Calculating disk usage is causing very high I/O Deadlock maybe the separate issue. This was related to old plugin version, so reporter should try new version and reply. 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/d/optout.
[JIRA] [groovy] (JENKINS-24757) Allow spaces in script parameters
SCM/JIRA link daemon resolved JENKINS-24757 as Fixed Allow spaces in script parameters Change By: SCM/JIRA link daemon (18/Sep/14 11: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/d/optout.
[JIRA] [groovy] (JENKINS-24757) Allow spaces in script parameters
SCM/JIRA link daemon commented on JENKINS-24757 Allow spaces in script parameters Code changed in jenkins User: Vojtech Juranek Path: src/main/java/hudson/plugins/groovy/Groovy.java http://jenkins-ci.org/commit/groovy-plugin/c9c33b17fe9099d64b21b7d4976f0ebf1fb15e44 Log: FIXED JENKINS-24757 Allow spaces in script parameters 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/d/optout.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Craig Phillips commented on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) My previous comment with regards to the bug. This is actually a side effect of the fact the plugin currently compares against the last build instead of the last stable build. If you get a stable build followed by a build that resolves one error and introduces one error, then this build is marked as unstable. However, if there is no change in the following build, the build status for the last build becomes stable again, because the number of new errors is zero, even though there has been one new error introduced since the last time the build was stable. This really does indicate that the comparison of new errors between each build is not right and that my original statement still stands, that the builds should always compare the current results against the last stable build. The last stable build is after all, the benchmark for where the cppcheck results need to be. If new errors have been introduced since then, then the build can't possibly be considered stable - ever. 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/d/optout.
[JIRA] [subversion] (JENKINS-24745) hundson failed to create symlink cause incorrect function
Dominika Tomaszewska updated JENKINS-24745 hundson failed to create symlink cause incorrect function Change By: Dominika Tomaszewska (18/Sep/14 12:17 PM) Environment: systemwin764bitJavaOracleIREjenkins ver.1.565.1jenkins accesthroughlocalhost:8080 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/d/optout.
[JIRA] [core] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
Trevor Baker updated JENKINS-14332 Repeated channel/timeout errors from Jenkins slave The instance I run jenkins on was a 2013.09 version that was upgraded to 2014.03.x via yum updates. I presume you could add the 2013.09 yum repo into /etc/yum.repos.d/ and see the 3.4.x kernels. From experience, 3.4.83-70.111 works with everything else from 2014.03.2 at the latest revisions. I've attached a kernel param dump. Change By: Trevor Baker (18/Sep/14 12:20 PM) Attachment: 3.4.83-70.111.amzn1.x86_64_kernel_params.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/d/optout.
[JIRA] [subversion] (JENKINS-24745) hundson failed to create symlink cause incorrect function
Dominika Tomaszewska commented on JENKINS-24745 hundson failed to create symlink cause incorrect function and what other information are important? Maybe I don't now what I should write or look for in investigation I'm new in Jenkins, so every one piece of information is valuable! 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/d/optout.
[JIRA] [plugin] (JENKINS-24738) Dynamically use Build Toolkit on Slave Machine when path to it is provided as an Environment Variable
Heather Fraser-Dube assigned JENKINS-24738 to Heather Fraser-Dube Dynamically use Build Toolkit on Slave Machine when path to it is provided as an Environment Variable Change By: Heather Fraser-Dube (18/Sep/14 1:11 PM) Assignee: DeluanQuintão HeatherFraser-Dube 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/d/optout.
[JIRA] [plugin] (JENKINS-24738) Dynamically use Build Toolkit on Slave Machine when path to it is provided as an Environment Variable
Heather Fraser-Dube resolved JENKINS-24738 as Not A Defect Dynamically use Build Toolkit on Slave Machine when path to it is provided as an Environment Variable Jenkins doesn't do the substitution of variables. The plugin itself won't do either because I don't think we will have the variables as configured for the slave in order to do the substitution. You can configure the slave to point to a toolkit that is in a different directory than on the master by following the Master-Slave configuration instructions Change By: Heather Fraser-Dube (18/Sep/14 1:20 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/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-24758) Build crashes (network timout) with vSphere slaves
Grégoire Dupé created JENKINS-24758 Build crashes (network timout) with vSphere slaves Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud Created: 18/Sep/14 2:16 PM Description: Hello, I've vSphere slaves witch are "reverted" to a snapshot for each build. Those slaves are used to test the installation of our products. Some builds wait a long time at the beginning of the build before to crash with the following message: Remote build on slave-seven64 (x86_64 seven uiTest java7 autoRestored win x86)FATAL: channel is already closed hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:541) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:739) at hudson.EnvVars.getRemote(EnvVars.java:404) at hudson.model.Computer.getEnvironment(Computer.java:927) at jenkins.model.CoreEnvironmentContributor.buildEnvironmentFor(CoreEnvironmentContributor.java:29) at hudson.model.Run.getEnvironment(Run.java:2248) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:905) at hudson.matrix.MatrixRun$MatrixRunExecution.decideWorkspace(MatrixRun.java:175) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:517) at hudson.model.Run.execute(Run.java:1740) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.io.IOException at hudson.remoting.Channel.close(Channel.java:1027) at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110) at hudson.remoting.PingThread.ping(PingThread.java:120) at hudson.remoting.PingThread.run(PingThread.java:81) Caused by: java.util.concurrent.TimeoutException: Ping started on 1411030796694 hasn't completed at 1411031036694 ... 2 more The problem happens very often but it is not 100% reproducible. I've this problem with 2 different sets of computers. My slave configuration was working properly in a not so far past (about 6 months), but I don't know at witch jenkins update the problem appeared. Sometimes a blocked build is running in slave (according to the Jenkins UI) whereas the computer hosting the slave is down (according to the "vSphere Client"). I also found the following message in a log of a running slave on which a build was waiting before to crash: sept. 18, 2014 3:30:59 PM hudson.remoting.jnlp.Main$CuiListener error SEVERE: The server rejected the connection: ntedtop-seven64 is already connected to this master. Rejecting this connection. java.lang.Exception: The server rejected the connection: ntedtop-seven64 is already connected to this master. Rejecting this connection. at hudson.remoting.Engine.onConnectionRejected(Engine.java:286) at hudson.remoting.Engine.run(Engine.java:261) Is there a workaround for this problem. Regards, Grégoire Environment: jenkins: 1.580 and 1.578 vsphere-cloud-1.1.11 master: linux slaves: Vista and Seven Project: Jenkins Priority: Major Reporter: Grégoire Dupé 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
[JIRA] [job-poll-action] (JENKINS-24759) All the jobs are stuck at SVN checking out after upgrade
Sahil kohli created JENKINS-24759 All the jobs are stuck at SVN checking out after upgrade Issue Type: Bug Assignee: Unassigned Components: job-poll-action Created: 18/Sep/14 2:21 PM Description: Steps : When i kick the build, it tries to pull the code but at some point it gets stuck and job is stuck and it is like forever. Project: Jenkins Priority: Blocker Reporter: Sahil kohli 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/d/optout.
[JIRA] [job-poll-action] (JENKINS-24759) All the jobs are stuck at SVN checking out after upgrade
Sahil kohli commented on JENKINS-24759 All the jobs are stuck at SVN checking out after upgrade "Executor #0 for master : executing Evolution2-Custom-Config-Android #140" Id=50 Group=main RUNNABLE (in native) at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:422) at com.sun.net.ssl.internal.ssl.InputRecord.readV3Record(InputRecord.java:534) at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:489) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:863) locked java.lang.Object@48bfba23 at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:820) at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75) locked com.sun.net.ssl.internal.ssl.AppInputStream@3f7de242 at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read1(BufferedInputStream.java:258) at java.io.BufferedInputStream.read(BufferedInputStream.java:317) locked java.io.BufferedInputStream@164af41d at org.tmatesoft.svn.core.internal.util.ChunkedInputStream.read(ChunkedInputStream.java:75) at java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:221) at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:141) at java.util.zip.GZIPInputStream.read(GZIPInputStream.java:90) at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) locked java.io.InputStreamReader@5b0b0f64 at java.io.InputStreamReader.read(InputStreamReader.java:167) at org.tmatesoft.svn.core.internal.io.dav.http.XMLReader.read(XMLReader.java:39) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1742) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(XMLEntityScanner.java:1416) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2800) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:513) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:815) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:744) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:128) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:543) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:911) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:876) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.java:220) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:480) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:334) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1291) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:839) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:507) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doCheckout(SVNUpdateClient16.java:915) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:19) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:8) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at
[JIRA] [rtc] (JENKINS-24760) Failure building the project
Cyrille Le Clerc created JENKINS-24760 Failure building the project Issue Type: Bug Assignee: Deluan Quintão Components: rtc Created: 18/Sep/14 2:35 PM Description: Can you provide guidance on how to build the `com.ibm.team.build.hjplugin-rtc` project, I get the following exception: [ERROR] Internal error: java.lang.RuntimeException: Failed to load p2 repository with ID 'rtc-401' from location file:/C:/RTC-Client-P2Repo_5.0.0.0-RTC-I20140509-1417: No repository found at file:/C:/RTC-Client-P2Repo_5.0.0.0-RTC-I20140509-1417. - [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Failed to load p2 repository with ID 'rtc-401' from location file:/C:/RTC-Client-P2Repo_5.0.0.0-RTC-I20140509-1417 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) 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:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: java.lang.RuntimeException: Failed to load p2 repository with ID 'rtc-401' from location file:/C:/RTC-Client-P2Repo_5.0.0.0-RTC-I20140509-1417 at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.loadMetadataRepository(TargetPlatformFactoryImpl.java:300) at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.gatherExternalInstallableUnits(TargetPlatformFactoryImpl.java:268) at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:166) at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:119) at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:1) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.computeTargetPlatform(P2TargetPlatformResolver.java:215) at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:100) at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:310) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) ... 11 more Caused by: org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/C:/RTC-Client-P2Repo_5.0.0.0-RTC-I20140509-1417. at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) at org.eclipse.tycho.p2.remote.RemoteMetadataRepositoryManager.loadRepository(RemoteMetadataRepositoryManager.java:59) at org.eclipse.tycho.p2.remote.RemoteMetadataRepositoryManager.loadRepository(RemoteMetadataRepositoryManager.java:52) at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.loadMetadataRepository(TargetPlatformFactoryImpl.java:296) ... 20 more Project: Jenkins Priority: Major Reporter:
[JIRA] [slave-proxy] (JENKINS-24761) Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
Sushant Gupta created JENKINS-24761 Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: slave-proxy, windows-slaves Created: 18/Sep/14 2:40 PM Description: My junking job is failing continuously with this error, earlier it used to pass. I am getting the error on the Jenkins job execution page, but the job is still running on windows node. I don't know if it is Junkins problem or windows slave's issue. Here I am pasting the logs: c:\jenkins\workspace\NSClient-Automation-1FATAL: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at com.sun.proxy.$Proxy56.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:956) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) Caused by: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:951) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: hudson.remoting.Channel$OrderlyShutdown ... 3 more Caused by: Command close created at at hudson.remoting.Command.init(Command.java:56) at hudson.remoting.Channel$CloseCommand.init(Channel.java:921) at hudson.remoting.Channel$CloseCommand.init(Channel.java:919) at hudson.remoting.Channel.close(Channel.java:1002) at hudson.remoting.Channel.close(Channel.java:985) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:926) at hudson.remoting.Channel$2.handle(Channel.java:461) ... 1 more Jenkins ver. 1.565.2 Project: Jenkins Priority: Major Reporter: Sushant Gupta 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
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Craig Phillips commented on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) This fix maintains backwards compatibility with the current strategy (which also remains the default). But it adds the option to change the behaviour such that it compares the current report against the last "stable" report. https://github.com/iwonbigbro/cppcheck-plugin/commit/d639413bf2b06c47ffa14cf3e2fe8c70073faa76 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/d/optout.
[JIRA] [core] (JENKINS-24762) Add space for company logo in banner/UI
Sagar Khushalani created JENKINS-24762 Add space for company logo in banner/UI Issue Type: New Feature Assignee: Unassigned Components: core, ui-changes Created: 18/Sep/14 4:17 PM Description: It would be awesome if y'all could add the ability to set a company/corporate logo in the banner or somewhere else in the UI page. Something like: Manage Jenkins Configure System Add/Upload Company Logo Environment: Jenkins 1.575 CentOS Project: Jenkins Priority: Minor Reporter: Sagar Khushalani 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/d/optout.
[JIRA] [core] (JENKINS-24762) Add space for company logo in banner/UI
Daniel Beck resolved JENKINS-24762 as Wont Fix Add space for company logo in banner/UI Trivial enough to do using e.g. Simple Theme Plugin and five lines of CSS. Change By: Daniel Beck (18/Sep/14 4:49 PM) Status: Open Resolved Resolution: WontFix 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/d/optout.
[JIRA] [gui] (JENKINS-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Daniel Beck commented on JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders Screenshots would help, by the way. Also, what screen resolution is this? Are only folders affected, or the regular 'All' view outside folders as well? 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/d/optout.
[JIRA] [subversion] (JENKINS-24759) All the jobs are stuck at SVN checking out after upgrade
Daniel Beck updated JENKINS-24759 All the jobs are stuck at SVN checking out after upgrade Does this occur on every build? Has this worked before? If so, what changed? Are you on a reliable network? (Wi-Fi doesn't count) How much data are you checking out? Change By: Daniel Beck (18/Sep/14 4:57 PM) Priority: Blocker Critical Component/s: subversion Component/s: job-poll-action 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/d/optout.
[JIRA] [core] (JENKINS-24761) Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
Daniel Beck updated JENKINS-24761 Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown Change By: Daniel Beck (18/Sep/14 5:02 PM) Labels: remoting Component/s: core Component/s: slave-proxy Component/s: windows-slaves 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/d/optout.
[JIRA] [core] (JENKINS-24751) Can't add comments
Daniel Beck resolved JENKINS-24751 as Incomplete Cant add comments Please describe the exact steps you took and the error that occurred. Change By: Daniel Beck (18/Sep/14 4:48 PM) Status: Open Resolved Resolution: Incomplete 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/d/optout.
[JIRA] [ssh-agent] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
Daniel Beck commented on JENKINS-24750 Cannot find user credentials when job is triggered with parameters And job A triggers job B sending job A's parameters Parameterized Trigger plugin? 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/d/optout.
[JIRA] [teamconcert] (JENKINS-24760) Failure building the project
Daniel Beck resolved JENKINS-24760 as Not A Defect Failure building the project Change By: Daniel Beck (18/Sep/14 5:01 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/d/optout.
[JIRA] [teamconcert] (JENKINS-24760) Failure building the project
Daniel Beck updated JENKINS-24760 Failure building the project Please do not use Jira for requests for assistance. Please ask in #jenkins or on the mailing lists instead. Change By: Daniel Beck (18/Sep/14 5:00 PM) Assignee: DeluanQuintão Component/s: teamconcert Component/s: rtc 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/d/optout.
[JIRA] [msbuild] (JENKINS-24753) MSBuild fails with error fatal error C1090: PDB API call failed, error code '23'
Daniel Beck commented on JENKINS-24753 MSBuild fails with error fatal error C1090: PDB API call failed, error code 23 Does this occur every time when building in Jenkins? Are you building multiple VS projects in parallel when this occurs? Try not doing that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-24749) please change the font back - the helvetica font is messing up the whole gui under folders
Daniel Beck resolved JENKINS-24749 as Wont Fix please change the font back - the helvetica font is messing up the whole gui under folders A lot more than font was changed, so this may be incidental. If you're referring to Cloudbees Folders Plugin, create a new view (e.g. List View with regexp pattern .*, configure columns, then go in folder configuration, set that as default view, and then you can delete the previous default 'All' View. Change By: Daniel Beck (18/Sep/14 4:47 PM) Status: Open Resolved Resolution: WontFix 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/d/optout.
[JIRA] [core] (JENKINS-24745) hundson failed to create symlink cause incorrect function
Daniel Beck edited a comment on JENKINS-24745 hundson failed to create symlink cause incorrect function Kanstantsin: Be nice, better too much (+ irrelevant) than too little information. 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/d/optout.
[JIRA] [core] (JENKINS-23929) Cannot use 'WORKSPACE' variable when creating custom workspace to *modify* the auto-generated workspace
Rob Petti commented on JENKINS-23929 Cannot use WORKSPACE variable when creating custom workspace to *modify* the auto-generated workspace I have similarly large builds, and don't have a problem with our clean scripts leaving files behind, so it's certainly not 'impossible'. In any event, if you really want a workspace for each branch, and don't want to use branch switching as I suggested earlier, then why not have one job per branch? That'll let you run builds in parallel as well, and more easily identify what code is actually being built. The way you are trying to do it seems like it would only confuse you and your users. 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/d/optout.
[JIRA] [core] (JENKINS-24745) hundson failed to create symlink cause incorrect function
Daniel Beck updated JENKINS-24745 hundson failed to create symlink cause incorrect function Change By: Daniel Beck (18/Sep/14 5:18 PM) Labels: jna Component/s: core Component/s: subversion 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/d/optout.
[JIRA] [core] (JENKINS-24764) Tabs are wrapping on narrow screens
Daniel Beck resolved JENKINS-24764 as Wont Fix Tabs are wrapping on narrow screens This is deliberate. Change By: Daniel Beck (18/Sep/14 6:24 PM) Status: Open Resolved Resolution: WontFix 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/d/optout.
[JIRA] [core] (JENKINS-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
recampbell updated JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation Change By: recampbell (18/Sep/14 7:21 PM) Summary: LongrunningOldDataMonitor.doDiscard()resultsin livelocks threadstarvation 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/d/optout.
[JIRA] [core] (JENKINS-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
Jesse Glick commented on JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation What makes you think this is really a problem in OldDataMonitor? I look at the thread dump and I see JobConfigHistorySaveableListener being likely at fault. 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/d/optout.
[JIRA] [notification] (JENKINS-24768) Payload doesn't contain SCM details or artifacts for a GIT repository based project
Daniel Beck commented on JENKINS-24768 Payload doesnt contain SCM details or artifacts for a GIT repository based project What project type is it? Freestyle? 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/d/optout.
[JIRA] [core] (JENKINS-24765) Jenkins doesn't escape commas when creating job URLs
Yaniv Kaul created JENKINS-24765 Jenkins doesnt escape commas when creating job URLs Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Sep/14 6:12 PM Description: We create a matrix job, which has one of the axis as such: "test-124 | -m a,b" "test-125 | -m w,z" In the job's shell script we cut the 2nd half and turn it into our parameters for our application. This fails to create a proper URL for the job. Full example (note the "-m%20rc,d%20" - this is the issue): http://example.com:8080/view/View/job/HaComb_Snapshots_Test_Suite_Coverage/CMD=x5290_MP_FC_sym50_rcd1+rcd2_raid+on_SnapBackupTest_sas%7C-n%20sym50%20-m%20rc,d%20-r%20--dcbtest%20SnapBackupTest%20-g%20sas,label_exp=sustainsinglesnapBoazS/ Simple workaround we've used is convert all commas to underscore and later in our script re-set them to commas. Environment: 1.575 Project: Jenkins Labels: url Priority: Minor Reporter: Yaniv Kaul 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/d/optout.
[JIRA] [build-flow] (JENKINS-24748) If running build flow job is aborted, other concurrent and future builds don't run a node's executors.
Daniel Beck resolved JENKINS-24748 as Duplicate If running build flow job is aborted, other concurrent and future builds dont run a nodes executors. I'd expect a build flow that runs on an always-on node to be flyweight as well the underlying reason then would be the same as for JENKINS-24519. Therefore resolving as duplicate. Change By: Daniel Beck (18/Sep/14 5:14 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24765) Jenkins doesn't escape commas when creating job URLs
Daniel Beck commented on JENKINS-24765 Jenkins doesnt escape commas when creating job URLs Could you please provide detailed and complete steps to reproduce the issue from scratch? Is this about the $JOB_URL or $BUILD_URL environment variable? 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/d/optout.
[JIRA] [xcode] (JENKINS-24766) Add support to multiple Xcode versions
Paul Eipper created JENKINS-24766 Add support to multiple Xcode versions Issue Type: New Feature Assignee: Unassigned Components: xcode Created: 18/Sep/14 6:29 PM Description: Using Environment Injector Plugin it is possible to define DEVELOPER_DIR to point to another Xcode installation. This feature request is to incorporate that into Xcode Plugin so that multiple versions can be configured on Jenkins settings and selected on the job setup. See more details here: http://andymolloy.tumblr.com/post/33504271829/specifying-xcode-version-for-jenkins-projects Project: Jenkins Priority: Major Reporter: Paul Eipper 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/d/optout.
[JIRA] [core] (JENKINS-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
recampbell commented on JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation Pull request: https://github.com/jenkinsci/jenkins/pull/1399 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/d/optout.
[JIRA] [core] (JENKINS-24764) Tabs are wrapping on narrow screens
Bruno Meneguello created JENKINS-24764 Tabs are wrapping on narrow screens Issue Type: Bug Assignee: Unassigned Attachments: table-header.png Components: core Created: 18/Sep/14 6:06 PM Description: When displaying Jenkins in narrower widths (splitted screen), my tabs are wrapping as shown in attachment. Project: Jenkins Priority: Major Reporter: Bruno Meneguello 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/d/optout.
[JIRA] [msbuild] (JENKINS-24753) MSBuild fails with error fatal error C1090: PDB API call failed, error code '23'
Sanketh PB commented on JENKINS-24753 MSBuild fails with error fatal error C1090: PDB API call failed, error code 23 This happens atleast twice in 8 builds. We build many projects in parallel. Our intention of using msbuild is to improve the speed and reduce build time by parallelization. I am not sure why this issue occurs. 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/d/optout.
[JIRA] [wiki] (JENKINS-24751) Can't add comments
Hector Magnanao commented on JENKINS-24751 Cant add comments I was in the Jenkins Dashboard. I clicked on manage plugins-PTC Integrity Plugin- this brought me to the plugin page- then I clicked on Add comments, I typed in my comments, but when I clicked on post button, it gives me a window that says 'Comment text is empty. Cannot create empty comments.' 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/d/optout.
[JIRA] [subversion] (JENKINS-24759) All the jobs are stuck at SVN checking out after upgrade
Sahil kohli commented on JENKINS-24759 All the jobs are stuck at SVN checking out after upgrade Yes, It was occurring on every build. Before upgrade of the jenkins Subversion Plugin, It was working perfectly fine. Within 30sec source code was chaecked out. But now i downgraded the jenkins and Restarted. It fixed the problem. Not sure if it was new version of the jenkins OR new version of the subversion plugin. 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/d/optout.
[JIRA] [core] (JENKINS-24745) hundson failed to create symlink cause incorrect function
Daniel Beck commented on JENKINS-24745 hundson failed to create symlink cause incorrect function To clarify, since you assigned this to yourself: you're not planning to fix 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/d/optout.
[JIRA] [p4] (JENKINS-24101) Poll Watching Label Continually Triggering
Michael Rose commented on JENKINS-24101 Poll Watching Label Continually Triggering I just came across the same problem running Jenkins version 1.580 with plugin version 1.0.14. I think it may be related to the polling taking place on a Windows system. Polling works just fine with my Linux project and when I changed the configurations of the project that was constantly polling to Tie the parent configuration to a Linux system (and restarted Jenkins so the change took effect), the continual triggering stopped. Note that I had tried restarting Jenkins without changing the configuration and that didn't help. 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/d/optout.
[JIRA] [msbuild] (JENKINS-24753) MSBuild fails with error fatal error C1090: PDB API call failed, error code '23'
Daniel Beck resolved JENKINS-24753 as Duplicate MSBuild fails with error fatal error C1090: PDB API call failed, error code 23 Duplicates JENKINS-9104. Change By: Daniel Beck (18/Sep/14 6:38 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow] (JENKINS-24748) If running build flow job is aborted, other concurrent and future builds don't run a node's executors.
Daniel Beck commented on JENKINS-24748 If running build flow job is aborted, other concurrent and future builds dont run a nodes executors. Please update this issue if you observe behavior that is inconsistent with the linked issue's explanation. 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/d/optout.
[JIRA] [core] (JENKINS-24761) Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
Kanstantsin Shautsou commented on JENKINS-24761 Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown Hi, this project called "Jenkins", not "junkins" or "junking". Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24763) Long running OldDataMonitor.doDiscard() results in livelocks
recampbell created JENKINS-24763 Long running OldDataMonitor.doDiscard() results in livelocks Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Sep/14 6:01 PM Description: A very large set of OldData can take a long time to discard. While this is running, most Jenkins operations which save any data are blocked. https://gist.github.com/recampbell/9336d3a32270e75a9333 doDiscard is synchronized and hudson.diagnosis.OldDataMonitor#remove also wants to lock OldDataMonitor most threads eventually lock when saving something, at least until the doDiscard eventually completes. Project: Jenkins Priority: Major Reporter: recampbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24759) All the jobs are stuck at SVN checking out after upgrade
Daniel Beck commented on JENKINS-24759 All the jobs are stuck at SVN checking out after upgrade Which are the before/after versions of each? 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/d/optout.
[JIRA] [core] (JENKINS-24763) Long running OldDataMonitor.doDiscard() results in livelocks
recampbell updated JENKINS-24763 Long running OldDataMonitor.doDiscard() results in livelocks Change By: recampbell (18/Sep/14 6:02 PM) Description: AverylargesetofOldDatacantakealongtimetodiscard.Whilethisisrunning,mostJenkinsoperationswhichsaveanydataareblocked.https://gist.github.com/recampbell/9336d3a32270e75a9333doDiscardissynchronizedandhudson.diagnosis.OldDataMonitor#removealsowantstolockOldDataMonitor most .Most threadseventuallylockwhensavingsomething,atleastuntilthedoDiscardeventuallycompletes. 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/d/optout.
[JIRA] [wiki] (JENKINS-24751) Can't add comments
Daniel Beck reopened JENKINS-24751 Cant add comments Change By: Daniel Beck (18/Sep/14 5:39 PM) Resolution: Incomplete 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/d/optout.
[JIRA] [core] (JENKINS-24763) Long running OldDataMonitor.doDiscard() results in livelocks
Daniel Beck updated JENKINS-24763 Long running OldDataMonitor.doDiscard() results in livelocks Appears to be a rather minor issue (with the workaround being to wait for ODM to finish). In what way is this a livelock? Change By: Daniel Beck (18/Sep/14 6:31 PM) Priority: Major Minor 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/d/optout.
[JIRA] [build-timeout] (JENKINS-9203) timer expires, and build is halted, but build is not marked as failed
Colden Rouleau commented on JENKINS-9203 timer expires, and build is halted, but build is not marked as failed Hey, so I'm not 100% sure what happened, but right after I posted my last message I changed the build from a static timeout (which I was using for testing purposes) to use an elastic timeout strategy. 35 minutes later, I got a failure notification email. So clearly, the elastic timeout works fine. I'm not sure what happened there, but I suppose there's no issue as far as I'm concerned. This was what was at the end of the log: Build timed out (after 35 minutes). Marking the build as failed. Build was aborted Sending e-mails to: myem...@something.com Finished: FAILURE 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/d/optout.
[JIRA] [core] (JENKINS-24745) hundson failed to create symlink cause incorrect function
Kanstantsin Shautsou commented on JENKINS-24745 hundson failed to create symlink cause incorrect function What is "Oracle IRE"? What version? Where is other info? "jenkins acces through localhost:8080" is irrelevant info. @ayfer , please read again https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue#Howtoreportanissue-WhatinformationtoprovideforEnvironmentandDescription 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/d/optout.
[JIRA] [core] (JENKINS-24745) hundson failed to create symlink cause incorrect function
Daniel Beck commented on JENKINS-24745 hundson failed to create symlink cause incorrect function Konstantsin: Be nice, better too much (+ irrelevant) than too little information. 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/d/optout.
[JIRA] [build-timeout] (JENKINS-9203) timer expires, and build is halted, but build is not marked as failed
Daniel Beck commented on JENKINS-9203 timer expires, and build is halted, but build is not marked as failed Colden Rouleau: Please file a new issue against the core component. Provide as much information as you can, and link back to this issue for reference. If possible, include full instructions how to reproduce the problem on a new Jenkins instance. See also https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue (FWIW I cannot reproduce the issue on my test instance, so be extra specific) 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/d/optout.
[JIRA] [copyartifact] (JENKINS-14367) Copy Artifact / Archive Artifact: archive as root
ikedam resolved JENKINS-14367 as Duplicate Copy Artifact / Archive Artifact: archive as root Duplicates JENKINS-12379 Change By: ikedam (19/Sep/14 12:19 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24745) hundson failed to create symlink cause incorrect function
Daniel Beck commented on JENKINS-24745 hundson failed to create symlink cause incorrect function What kind of volume is mounted at T: Note that Jenkins creates symbolic links in its home directory for various reasons, and that should therefore be stored on a volume that supports symbolic links. Also, the user Jenkins runs as needs to have permission to create symbolic links AFAIR, Windows allows disabling that e.g. in Group Policy. The corresponding command line utility (to possibly get more information why creation fails) is mklink. 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/d/optout.
[JIRA] [tfs] (JENKINS-16207) Changes Summary diff link broken after migration to TFS 2012
Kyle OConnor commented on JENKINS-16207 Changes Summary diff link broken after migration to TFS 2012 It looks like you are right, the following is working for me as well with 2012: http://TFS Server/tfs/Collection/_versionControl/changeset?id=Changeset ID http://TFS Server/tfs/Collection/_versionControl/changeset/Changeset ID#path=File Path_a=compare 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/d/optout.
[JIRA] [role-strategy] (JENKINS-24767) Role-based Authorization Strategy not working with sub-folders
Daniel Beck updated JENKINS-24767 Role-based Authorization Strategy not working with sub-folders Similar to a file system, you need to provide access to every item in the hierarchy. So Item/Read on Folder1 and any relevant permissions on Folder1/FolderA should do it. Change By: Daniel Beck (18/Sep/14 7:08 PM) Assignee: JesseGlick OlegNenashev Component/s: cloudbees-folder 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/d/optout.
[JIRA] [core] (JENKINS-24763) Long running OldDataMonitor.doDiscard() results in livelocks
recampbell commented on JENKINS-24763 Long running OldDataMonitor.doDiscard() results in livelocks In the meantime, no build can finish, and no slaves can come online. In the incident observed, the discard was taking more than an hour and Jenkins could not complete builds or do basically any other operation. It's unacceptable for Jenkins to be inoperable for minutes at a time, hence a higher severity. I suppose this is really just "starvation' instead of a livelock per se. Will update the description. 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/d/optout.
[JIRA] [build-timeout] (JENKINS-9203) timer expires, and build is halted, but build is not marked as failed
Colden Rouleau commented on JENKINS-9203 timer expires, and build is halted, but build is not marked as failed I am using: Jenkins 1.580 build timeout plugin 1.14 I am trying to get the "fail the build" functionality to work, but instead the build is just getting aborted. Here is what I get at the end of the log file: Build timed out (after 3 minutes). Marking the build as failed. Build was aborted Finished: ABORTED I apologize if this is the wrong place to post, but it appears to be the same issue, perhaps coming back again. 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/d/optout.
[JIRA] [cloudbees-folder] (JENKINS-24767) Role-based Authorization Strategy not working with sub-folders
Eric Anker created JENKINS-24767 Role-based Authorization Strategy not working with sub-folders Issue Type: Bug Assignee: Jesse Glick Components: cloudbees-folder, role-strategy Created: 18/Sep/14 6:37 PM Description: Using the folder structure below, trying to give a user access to ONLY the contents of FolderA. I'd expect .FolderA. to do that. To Reproduce: Create this folder structure: Folder1/ Folder1/FolderA/ Folder1/FolderA/JobA Folder1/FolderB/ Folder1/FolderB/JobB Folder1/Job1 Try these search expressions: - .Folder1. Works - .FolderA. Does NOT work - .JobA. Does NOT work - .FolderB. Does NOT work - .JobB. Does NOT work - .Job1. Does NOT work Environment: Jenkins ver. 1.565.2 CloudBees Folders Plugin 4.6.1 Role-based Authorization Strategy 2.2.0 Windows 7 Project: Jenkins Labels: security folders role regex Priority: Major Reporter: Eric Anker 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/d/optout.
[JIRA] [notification] (JENKINS-24768) Payload doesn't contain SCM details or artifacts for a GIT repository based project
Hrusikesh Panda
created JENKINS-24768
Payload doesnt contain SCM details or artifacts for a GIT repository based project
Issue Type:
Bug
Assignee:
Unassigned
Components:
notification
Created:
18/Sep/14 8:51 PM
Description:
I get this as payload:
{
"name": "dummy-web",
"url": "job/dummy-web/",
"build": {
"full_url": "http://jenkins01.myweb.net:/job/dummy-web/9/",
"number": 9,
"phase": "COMPLETED",
"status": "SUCCESS",
"url": "job/dummy-web/9/"
}
}
This is a GIT repository based project and I have enabled Archive Artifacts in Jenkins. And I can see the artifacts being generated in the build worksapce.
Project:
Jenkins
Labels:
plugin
notification
Priority:
Major
Reporter:
Hrusikesh Panda
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/d/optout.
