[JIRA] [core] (JENKINS-27939) DefaultJnlpSlaveReceiver should return true when rejecting a takeover.
Oleg Nenashev started work on JENKINS-27939 DefaultJnlpSlaveReceiver should return true when rejecting a takeover. Change By: Oleg Nenashev (15/Apr/15 6:58 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [maven-plugin] (JENKINS-27947) JDK 1.6 maven builds fail when running on Tomcat 8
Daniel Beck commented on JENKINS-27947 JDK 1.6 maven builds fail when running on Tomcat 8 JENKINS-25272? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27925) Build step is not always saved
Daniel Beck commented on JENKINS-27925 Build step is not always saved The json argument looks fine, first the shell, then the batch. And after submitting that, the job still contains two batch build steps? There have been no warnings logged in /log/all? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [nodejs-plugin] (JENKINS-27944) Auto-installer list not populating on Ubuntu Server
Daniel Beck commented on JENKINS-27944 Auto-installer list not populating on Ubuntu Server Force an update of the update center metadata by clicking 'Update Now' in the Advanced tab of Manage Plugins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
lacostej commented on JENKINS-23958 Pipe Broken As indicated earlier, I posted a message on the dev list: https://groups.google.com/d/msg/jenkinsci-dev/LjHaBd6yUW8/LstWtVCaOHwJ But I didn't get feedback. I am considering to start patching the remoting lib to get more debugging. I don't understand why the pipe gets broken. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
Daniel Beck commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value If BUILD_TIMESTAMP is a Jenkins variable, why can't it be used directly (without using the Zentimestamp plugin). That variable is not provided by Jenkins core. It's not defined without Zentimestamp. Jenkins core changed the storage format and therefore the format of the BUILD_ID variable contents. If you were using it for something other than a reference to the build folder name (e.g. to indicate start date and time of a build), you now need to switch to using BUILD_TIMESTAMP provided by Zentimestamp, or determine the date on your own (some solutions provided in comments above). The recent change in core was a documentation fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27928) environment variable changes are not applied.
Daniel Beck resolved JENKINS-27928 as Duplicate environment variable changes are not applied. It looks like you're using a plugin (Tikal Multijob) with a hard dependency on env-inject. That was unexpected, sorry about that. That said, this looks a lot like JENKINS-27739, so resolving as duplicate. Feel free to help investigate the cause over there. Change By: Daniel Beck (15/Apr/15 4:23 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] [tfs-plugin] (JENKINS-23344) TFS plugin does not create label as trigger value is not saved in config
Olivier Dagenais closed JENKINS-23344 as Fixed TFS plugin does not create label as trigger value is not saved in config Fixed in version 3.2.0 Change By: Olivier Dagenais (15/Apr/15 2:22 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-3002) TFS Support to get labels
Olivier Dagenais closed JENKINS-3002 as Fixed TFS Support to get labels Fixed in version 3.2.0 Change By: Olivier Dagenais (15/Apr/15 2:23 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-23033) TFS Password visible in view source
Olivier Dagenais closed JENKINS-23033 as Fixed TFS Password visible in view source Fixed in version 3.2.0 Change By: Olivier Dagenais (15/Apr/15 2:23 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Alex Earl commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module This happens intermittently for me. Jenkins 1.596.2 Windows 2012 R2 (64-bit) master Windows 7 (32bit) slave Java: Oracle 1.8 java.lang.IllegalStateException: Invalid object ID 182 iota=183 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) at ..remote call to vme-sv-exe-d12(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy73.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.Launcher$ProcStarter.join(Launcher.java:388) at org.jenkinsci.plugins.managedscripts.ScriptBuildStep.perform(ScriptBuildStep.java:177) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #182 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Tue Apr 14 17:19:36 MST 2015 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Released at Tue Apr 14 17:19:36 MST 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:382) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command hudson.remoting.UnexportCommand@17b6a6d created at at hudson.remoting.Command.(Command.java:67) at hudson.remoting.Command.(Command.java:50) at hudson.remoting.UnexportCommand.(UnexportCommand.java:33) at
[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.
dogfood commented on JENKINS-10629 Tar implimentation can't handle > 8GB and doesn't error out. Integrated in jenkins_main_trunk #4082 Result = SUCCESS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-27927) Some interface idioms do not work in Groovy CPS
Thomas Dalton commented on JENKINS-27927 Some interface idioms do not work in Groovy CPS If I replace a = b as Foo with Foo a = b It doesn't work either I'm afraid , same exception. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [repo-plugin] (JENKINS-23262) Permission denied when using repo plugin with ssh-agent plugin
Scott Anderson resolved JENKINS-23262 as Fixed Permission denied when using repo plugin with ssh-agent plugin Change By: Scott Anderson (14/Apr/15 11:08 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repo-plugin] (JENKINS-23262) Permission denied when using repo plugin with ssh-agent plugin
Scott Anderson commented on JENKINS-23262 Permission denied when using repo plugin with ssh-agent plugin That's exactly right, and the fix is already in the master branch but unreleased: https://github.com/jenkinsci/repo-plugin/commit/12d723a0b24218f8a77f97d38f398c0847b9e0e3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [maven-plugin] (JENKINS-27947) JDK 1.6 maven builds fail when running on Tomcat 8
pmv created JENKINS-27947 JDK 1.6 maven builds fail when running on Tomcat 8 Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 14/Apr/15 10:50 PM Description: This seems to be a duplicate of JENKINS-16920, but a newer iteration. Due to the recent talk on the mailing list about removing 1.6 support, as well as the git plugin dropping 1.6 support, we decided to upgrade our Jenkins from running on Java 6/Tomcat 6 to Java 7/Tomcat 8. However, it appears Tomcat 8 ships a version of servlet-api built with Java 7. Jessie's original analysis on why this was a problem is here: https://issues.jenkins-ci.org/browse/JENKINS-16920?focusedCommentId=174350&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-174350 I suspect this is either the same or a very similar issue. Here is the stack trace: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:178) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at hudson.maven.Maven3Builder.call(Maven3Builder.java:134) at hudson.maven.Maven3Builder.call(Maven3Builder.java:69) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.ClassFormatError: Failed to load javax.servlet.ServletException at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:325) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:237) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at hudson.ExtensionList.lookup(ExtensionList.java:350) at hudson.FilePath.actAsync(FilePath.java:1046) at hudson.FilePath.copyRecursiveTo(FilePath.java:2070) at hudson.FilePath.copyRecursiveTo(FilePath.java:2013) at hudson.FilePath.copyRecursiveTo(FilePath.java:1996) at hudson.maven.reporters.AbstractMavenJavadocArchiver.postExecute(AbstractMavenJavadocArchiver.java:98) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:628) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:610) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.si
[JIRA] [veracode-scanner-plugin] (JENKINS-27823) error while Configuring a Jenkins Job for Veracode Analysis
Stephen Joyce commented on JENKINS-27823 error while Configuring a Jenkins Job for Veracode Analysis This error is from an older version of the Veracode Jenkins plugin, and a correction is available on the Veracode Help Center. Please contact your Veracode customer support group for assistance if needed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
Malcolm Fernandes commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value If BUILD_TIMESTAMP is a Jenkins variable, why can't it be used directly (without using the Zentimestamp 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-27922) Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread
Jamie Doornbos updated JENKINS-27922 Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread Server failed sooner than expected, probably due to a large increase in job load for our current testing cycle. Attached a new thread dump, a grand total of 937 AgentServer threads. The system log shows the same java.lang.OutOfMemoryError: unable to create new native thread. I have to restart the service again to move forward with my development. Change By: Jamie Doornbos (14/Apr/15 10:17 PM) Attachment: Thread dump [Jenkins].html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27927) Some interface idioms do not work in Groovy CPS
Jesse Glick commented on JENKINS-27927 Some interface idioms do not work in Groovy CPS Well my first suggestion is to try actual Java syntax: Foo a = b; in case it is the as keyword which causes the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27927) Some interface idioms do not work in Groovy CPS
Thomas Dalton
commented on JENKINS-27927
Some interface idioms do not work in Groovy CPS
Ahh.. in which case I apologies for the miscommunication on my part, I actually tried the Java syntax first - I then reduced the problem to simpler forms to post the issue.
Here is what I tried originally:
interface Foo {
String name()
}
class Bar implements Foo {
def String name() {
return "Ronald"
}
}
node {
b = new Bar()
a = b as Foo
echo a.name()
}
This doesn't work either and the same exception Cannot invoke method visit() on null object is thrown.
Yet under a groovy console:
interface Foo {
String name()
}
class Bar implements Foo {
def String name() {
return "Ronald"
}
}
b = new Bar()
a = b as Foo
println a.name()
It works fine. Hence I think it is likely a problem with all uses of interface and why I'm on the lookout for a decent workaround
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27925) Build step is not always saved
Rasmus Pedersen commented on JENKINS-27925 Build step is not always saved Q: In the developer tools of your browser, what is the request sent on clicking 'Send' in step 7? A: The request-body: Content-Type: application/x-www-form-urlencoded Content-Length: 5363 name=rupt+test+tos&description=&_.daysToKeepStr=&_.numToKeepStr=&_.artifactDaysToKeepStr=&_.artifactNumToKeepStr=&stapler-class=hudson.tasks.LogRotator&%24class=hudson.tasks.LogRotator&stapler-class-bag=true&quiet_period=5&scmCheckoutRetryCount=0&_.customWorkspace=&_.displayNameOrNull=&scm=0&_.cvsRoot=&_.password=&_.branchName=&stapler-class=hudson.scm.CvsRepositoryLocation%24BranchRepositoryLocation&%24class=hudson.scm.CvsRepositoryLocation%24BranchRepositoryLocation&stapler-class=hudson.scm.CvsRepositoryLocation%24HeadRepositoryLocation&%24class=hudson.scm.CvsRepositoryLocation%24HeadRepositoryLocation&_.tagName=&stapler-class=hudson.scm.CvsRepositoryLocation%24TagRepositoryLocation&%24class=hudson.scm.CvsRepositoryLocation%24TagRepositoryLocation&_.remoteName=&_.localName=&stapler-class=hudson.scm.browsers.FishEyeCVS&%24class=hudson.scm.browsers.FishEyeCVS&stapler-class=hudson.scm.browsers.OpenGrok&%24class=hudson.scm.browsers.OpenGrok&stapler-class=hudson.scm.browsers.ViewCVS&%24class=hudson.scm.browsers.ViewCVS&_.pattern=&_.compressionLevel=-1&_.canUseUpdate=on&_.pruneEmptyDirectories=on&_.cvsRoot=&_.password=&_.branchName=&stapler-class=hudson.scm.CvsRepositoryLocation%24BranchRepositoryLocation&%24class=hudson.scm.CvsRepositoryLocation%24BranchRepositoryLocation&stapler-class=hudson.scm.CvsRepositoryLocation%24HeadRepositoryLocation&%24class=hudson.scm.CvsRepositoryLocation%24HeadRepositoryLocation&_.tagName=&stapler-class=hudson.scm.CvsRepositoryLocation%24TagRepositoryLocation&%24class=hudson.scm.CvsRepositoryLocation%24TagRepositoryLocation&_.remoteName=&_.localName=&_.projectsetFileName=&stapler-class=hudson.scm.browsers.FishEyeCVS&%24class=hudson.scm.browsers.FishEyeCVS&stapler-class=hudson.scm.browsers.OpenGrok&%24class=hudson.scm.browsers.OpenGrok&stapler-class=hudson.scm.browsers.ViewCVS&%24class=hudson.scm.browsers.ViewCVS&_.pattern=&_.compressionLevel=-1&_.canUseUpdate=on&_.username=&_.password=&_.pruneEmptyDirectories=on&stapler-class=hudson.scm.browsers.CvsFacadeRepositoryBrowser&%24class=hudson.scm.browsers.CvsFacadeRepositoryBrowser&stapler-class=hudson.scm.browsers.FishEyeCVS&%24class=hudson.scm.browsers.FishEyeCVS&stapler-class=hudson.scm.browsers.OpenGrok&%24class=hudson.scm.browsers.OpenGrok&stapler-class=hudson.scm.browsers.ViewCVS&%24class=hudson.scm.browsers.ViewCVS&_.remote=&_.local=.&depthOption=infinity&stapler-class=hudson.scm.subversion.UpdateUpdater&%24class=hudson.scm.subversion.UpdateUpdater&stapler-class=hudson.scm.subversion.CheckoutUpdater&%24class=hudson.scm.subversion.CheckoutUpdater&stapler-class=hudson.scm.subversion.UpdateWithCleanUpdater&%24class=hudson.scm.subversion.UpdateWithCleanUpdater&stapler-class=hudson.scm.subversion.UpdateWithRevertUpdater&%24class=hudson.scm.subversion.UpdateWithRevertUpdater&stapler-class=hudson.scm.browsers.Assembla&%24class=hudson.scm.browsers.Assembla&stapler-class=hudson.scm.browsers.CollabNetSVN&%24class=hudson.scm.browsers.CollabNetSVN&stapler-class=hudson.scm.browsers.FishEyeSVN&%24class=hudson.scm.browsers.FishEyeSVN&stapler-class=hudson.scm.browsers.SVNWeb&%24class=hudson.scm.browsers.SVNWeb&stapler-class=hudson.scm.browsers.Sventon&%24class=hudson.scm.browsers.Sventon&stapler-class=hudson.scm.browsers.Sventon2&%24class=hudson.scm.browsers.Sventon2&stapler-class=hudson.scm.browsers.ViewSVN&%24class=hudson.scm.browsers.ViewSVN&stapler-class=hudson.scm.browsers.WebSVN&%24class=hudson.scm.browsers.WebSVN&_.excludedRegions=&_.includedRegions=&_.excludedUsers=&_.excludedCommitMessages=&_.excludedRevprop=&_.upstreamProjects=&ReverseBuildTrigger.threshold=SUCCESS&_.spec=&scmpoll_spec=&command=hello+from+shell&stapler-class=hudson.tasks.Shell&kind=hudson.tasks.Shell&%24class=hudson.tasks.Shell&command=hello+from+batch+2&stapler-class=hudson.tasks.BatchFile&kind=hudson.tasks.BatchFile&%24class=hudson.tasks.BatchFile&core%3Aapply=&json=%7B%22name%22%3A+%22rupt+test+tos%22%2C+%22description%22%3A+%22%22%2C+%22logrotate%22%3A+false%2C+%22%22%3A+%220%22%2C+%22buildDiscarder%22%3A+%7B%22daysToKeepStr%22%3A+%22%22%2C+%22numToKeepStr%22%3A+%22%22%2C+%22artifactDaysToKeepStr%22%3A+%22%22%2C+%22artifactNumToKeepStr%22%3A+%22%22%2C+%22stapler-class%22%3A+%22hudson.tasks.LogRotator%22%2
[JIRA] [core] (JENKINS-27925) Build step is not always saved
Rasmus Pedersen
updated JENKINS-27925
Build step is not always saved
Change By:
Rasmus Pedersen
(14/Apr/15 9:15 PM)
Description:
When changing a build step from a {{Windows batch command}} to a {{Shell command}}
and at
the
same time puts two hyphens, {{--}}, in the shell command, the
content of the shell command is not always saved.*Steps to reproduce:*# Create two {{Windows batch command}} build steps.# Click {{Save}}# Click {{Configure}}# Delete one of the build steps# Create a {{Shell command}} build step and enter some text in it
containing two hyphens, e
.
g. {noformat}some text -- some thing{noformat}
# Move the just created build step to the top.# Click {{Save}}*What I expected to happen:*The content of the {{Shell command}} build step is saved.*What actually happens:*The content isn't saved.I've tried the above method in both Firefox (with addons disabled), IE and Chrome and I've only successfully reproduced it in Firefox (is it a bug in Firefox?).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-27925) Build step is not always saved
Rasmus Pedersen commented on JENKINS-27925 Build step is not always saved Q: Does this work for newly created projects? A: Yes. Q: Are they freestyle projects? A: Yes Q: Are any errors shown in the JS console of your browser? A: No, but there are some warnings about getAttributeNode() and getPreventDefault(). Q: In the developer tools of your browser, what is the request sent on clicking 'Send' in step 7? A: I'll have a look at that tomorrow. Q: Is this reproducible 100% of the time, or only sometimes? A: It is reproducible 100% of the time. Q: Are the two original Windows batch commands empty, or do they contain text? A: It doesn't seem to matter whether they are empty or not. I don't know why I've been so focused on the hyphens, it doesn't seem to matter what text you enter in the Shell command text box. I'll 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] [htmlpublisher-plugin] (JENKINS-27946) When rename the HTML Report title, the HTML report disappeared.
yueran zeng updated JENKINS-27946 When rename the HTML Report title, the HTML report disappeared. Change By: yueran zeng (14/Apr/15 9:10 PM) Attachment: DefaultReportTitleSettings.png Attachment: DefaultReportTitleSettings2.png Attachment: EditedReportTitleSettings.png Attachment: EditedReportTitleSettings2.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [htmlpublisher-plugin] (JENKINS-27946) When rename the HTML Report title, the HTML report disappeared.
yueran zeng created JENKINS-27946 When rename the HTML Report title, the HTML report disappeared. Issue Type: Bug Assignee: mcrooney Components: htmlpublisher-plugin Created: 14/Apr/15 9:09 PM Description: Problem found with Jenkins 1.609 Problem is with the HTML Publisher plugin When I edit the HTML Report title from default 'HTML Report' to 'test', the HTML report disappeared from the project. Project: Jenkins Priority: Minor Reporter: yueran zeng This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [websphere-deployer-plugin] (JENKINS-27945) Support for deployment on cluster
Valerio Ponte created JENKINS-27945 Support for deployment on cluster Issue Type: Improvement Assignee: Valerio Ponte Components: websphere-deployer-plugin Created: 14/Apr/15 9:01 PM Description: For some reason deployment on cluster is disabled. The code is almost already in place but there is no way to specify a cluster on the web interface options, therefore when you try to deploy on a cluster it fails. I open this issue for 2 reasons: 1. provide a PR on github that will allow deployment on clusters 2. understand why deployment on clusters is currently disallowed, since maybe there is some reason I am missing Project: Jenkins Labels: improvement plugin Priority: Major Reporter: Valerio Ponte This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-26781) regression resolving Descriptor using "$class" vs "kind"
SCM/JIRA link daemon commented on JENKINS-26781 regression resolving Descriptor using "$class" vs "kind" Code changed in jenkins User: Jesse Glick Path: changelog.html cli/pom.xml core/pom.xml core/src/main/java/hudson/FilePath.java core/src/main/java/hudson/model/Descriptor.java core/src/main/java/hudson/org/apache/tools/tar/TarInputStream.java core/src/main/java/hudson/org/apache/tools/tar/TarOutputStream.java core/src/main/java/hudson/tools/DownloadFromUrlInstaller.java core/src/main/java/hudson/util/io/TarArchiver.java core/src/main/java/jenkins/AgentProtocol.java core/src/test/java/hudson/FilePathTest.java plugins/pom.xml pom.xml test/pom.xml war/pom.xml http://jenkins-ci.org/commit/jenkins/b62a07c0dbba637001539c1e668be814a164f701 Log: Merge branch 'master' into JENKINS-26781 and fixing @since TODO. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-26781) regression resolving Descriptor using "$class" vs "kind"
SCM/JIRA link daemon commented on JENKINS-26781 regression resolving Descriptor using "$class" vs "kind" Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Descriptor.java core/src/main/resources/lib/form/class-entry.jelly http://jenkins-ci.org/commit/jenkins/2dcb6d3505d7166a94a6410c3c146a5e4350f8c1 Log: Merge branch 'JENKINS-26781' of github.com:jenkinsci/jenkins into JENKINS-26781 Compare: https://github.com/jenkinsci/jenkins/compare/3c4b1e63a271...2dcb6d3505d7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [nodejs-plugin] (JENKINS-27944) Auto-installer list not populating on Ubuntu Server
Todd Morrison updated JENKINS-27944 Auto-installer list not populating on Ubuntu Server Change By: Todd Morrison (14/Apr/15 8:41 PM) Description: The Auto-installer listing shows an input field (vs drop-down displayed in the screenshots for the plugin) when using 'install from npmjs . org' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [nodejs-plugin] (JENKINS-27944) Auto-installer list not populating on Ubuntu Server
Todd Morrison commented on JENKINS-27944 Auto-installer list not populating on Ubuntu Server Attempts to add a valid npmjs.org version tag to the 'installation' field results in 'Invalid tool ID v0.XX.XX' (respective to the version attempted).Invalid tool ID v0.10.36 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27928) environment variable changes are not applied.
marlene cote commented on JENKINS-27928 environment variable changes are not applied. I reinstalled the envinject plugin and my jobs are back.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-10629) Tar implimentation can't handle > 8GB and doesn't error out.
Oleg Nenashev commented on JENKINS-10629 Tar implimentation can't handle > 8GB and doesn't error out. Marked the issue as LTS candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [nodejs-plugin] (JENKINS-27944) Auto-installer list not populating on Ubuntu Server
Todd Morrison updated JENKINS-27944 Auto-installer list not populating on Ubuntu Server Change By: Todd Morrison (14/Apr/15 8:33 PM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-27944) Auto-installer list not populating on Ubuntu Server
Todd Morrison created JENKINS-27944 Auto-installer list not populating on Ubuntu Server Issue Type: Bug Assignee: Unassigned Components: nodejs-plugin Created: 14/Apr/15 8:32 PM Description: The Auto-installer listing shows an input field (vs drop-down displayed in the screenshots for the plugin). Environment: Jenkins ver. 1.609; os.arch: amd64; os.name: Linux; os.version: 3.13.0-48-generic; Ubuntu-Server Project: Jenkins Priority: Minor Reporter: Todd Morrison This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-10629) Tar implimentation can't handle > 8GB and doesn't error out.
SCM/JIRA link daemon commented on JENKINS-10629 Tar implimentation can't handle > 8GB and doesn't error out. Code changed in jenkins User: Oleg Nenashev Path: core/pom.xml core/src/main/java/hudson/FilePath.java core/src/main/java/hudson/org/apache/tools/tar/TarInputStream.java core/src/main/java/hudson/org/apache/tools/tar/TarOutputStream.java core/src/main/java/hudson/util/io/TarArchiver.java http://jenkins-ci.org/commit/jenkins/b6c7b83e7ba1a7538382d220d044626f2b2e65be Log: JENKINS-10629 - Migrate the Tar archives handling code to commons-compress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-10629) Tar implimentation can't handle > 8GB and doesn't error out.
SCM/JIRA link daemon commented on JENKINS-10629 Tar implimentation can't handle > 8GB and doesn't error out. Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/util/io/TarArchiver.java http://jenkins-ci.org/commit/jenkins/4ddeeb84195fa29c964ef2e55661b669c310baeb Log: FIXED JENKINS-10629] - Enable BigNumber mode to support archiving of files with size >8Gb BIGNUMBER_STAR mode has been selected, because it utilizes GNU extensions (like LONGFILE_GNU does). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-10629) Tar implimentation can't handle > 8GB and doesn't error out.
SCM/JIRA link daemon commented on JENKINS-10629 Tar implimentation can't handle > 8GB and doesn't error out. Code changed in jenkins User: Oleg Nenashev Path: core/src/test/java/hudson/FilePathTest.java http://jenkins-ci.org/commit/jenkins/32dca8819c003ee6d815d1c9858dccb19f64b71d Log: JENKINS-10629 - Direct unit test for the issue This test also introduces additional round-trip tests for small files This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [coverity-plugin] (JENKINS-18317) Coverity - Default Defect Filter selects no defects when non-default component map is associated with a stream in Coverity
Chuck Aude commented on JENKINS-18317 Coverity - Default Defect Filter selects no defects when non-default component map is associated with a stream in Coverity Same result as others, Jenkins 1.609, Coverity plugin 1.50, CIM 7.6.0. Streams using the default component map work fine, streams using non-default component maps return zero defects/issues to Jenkins. The analysis and issues are uploaded to the CIM and can be viewed there. However the lack of visibility from Jenkins represents a serious bug in this 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-27928) environment variable changes are not applied.
marlene cote commented on JENKINS-27928 environment variable changes are not applied. Apr 14, 2015 3:53:25 PM hudson.model.ItemGroupMixIn loadChildren WARNING: could not load D:\Jenkins\jobs\The-A-Team\jobs\08-THEATEAM-INT-UCC-BUILD java.io.IOException: Unable to read D:\Jenkins\jobs\The-A-Team\jobs\08-THEATEAM-INT-UCC-BUILD\config.xml at hudson.XmlFile.read(XmlFile.java:144) at hudson.model.Items.load(Items.java:316) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:109) at com.cloudbees.hudson.plugins.folder.Folder.onLoad(Folder.java:238) at hudson.model.Items.load(Items.java:317) at jenkins.model.Jenkins$17.run(Jenkins.java:2651) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: com.thoughtworks.xstream.mapper.CannotResolveClassException: com.tikal.jenkins.plugins.multijob.MultiJobProject at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:74) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.SecurityMapper.realClass(SecurityMapper.java:71) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.XStream2$CompatibilityMapper.realClass(XStream2.java:280) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at org.jenkinsci.jruby.JRubyMapper.realClass(JRubyMapper.java:34) at hudson.util.xstream.MapperDelegate.realClass(MapperDelegate.java:43) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:48) at com.thoughtworks.xstream.core.util.HierarchicalStreams.readClassType(HierarchicalStreams.java:29) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:133) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189) at hudson.util.XStream2.unmarshal(XStream2.java:113) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1053) at hudson.XmlFile.read(XmlFile.java:142) ... 13 more
[JIRA] [core] (JENKINS-27928) environment variable changes are not applied.
marlene cote commented on JENKINS-27928 environment variable changes are not applied. I just did a safe restart of jenkins server and now all of my jobs are gone! I see them in the folder on the disk, and I tried reload from disk without success. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [docker-plugin] (JENKINS-23301) Support unix protocol for connection
Kanstantsin Shautsou commented on JENKINS-23301 Support unix protocol for connection Of course supporting everything will be plus. But now it minor. When i firstly followed docs i opened http access and configured configuration. So if you follow docs, then everything should work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27904) Access to currentBuild.getStartTime in Jenkins Workflow
Jesse Glick resolved JENKINS-27904 as Duplicate Access to currentBuild.getStartTime in Jenkins Workflow Or you can use the currentStartTime and whatever DateFormat you like. Change By: Jesse Glick (14/Apr/15 7:52 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] [docker-plugin] (JENKINS-23301) Support unix protocol for connection
Jesse Glick commented on JENKINS-23301 Support unix protocol for connection As a usability / out-of-the-box experience issue this seemed pretty high up there: docker from the command line works fine in the default package installed on Linux, but trying to use the Docker plugin in Jenkins does not work unless you change your system configuration. The inline help should improve matters somewhat, but it would certainly be better if the plugin could connect to the Docker daemon at the standard socket location without special configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)
Tommy Tynjä commented on JENKINS-26726 java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70) Thank you for the update Dmytro! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-27905) stage concurrency allows 1 thread to be blocked at a time, others fail and hang job
Jesse Glick commented on JENKINS-27905 stage concurrency allows 1 thread to be blocked at a time, others fail and hang job I am not saying there are no conceivable use cases, just that stage is designed and written to implement one particular logical operation (a kind of semaphore), and what you are asking about would require a different step with a different implementation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [prioritysorter-plugin] (JENKINS-27770) AdvancedQueueSorter call to sort violates the comparison contract
Magnus Sandberg closed JENKINS-27770 as Fixed AdvancedQueueSorter call to sort violates the comparison contract Fixed in 2.11 Change By: Magnus Sandberg (14/Apr/15 7:42 PM) Status: Open Closed 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] [workflow-plugin] (JENKINS-27927) Some interface idioms do not work in Groovy CPS
Jesse Glick commented on JENKINS-27927 Some interface idioms do not work in Groovy CPS I would just try using Java-compatible syntax first. More likely to already be supported. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27943) ItemGroupMixin triggers SaveableListener.onChange() on incomplete Object
James Nord created JENKINS-27943 ItemGroupMixin triggers SaveableListener.onChange() on incomplete Object Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Apr/15 7:35 PM Description: The ItemGroupMixin calls save() on a newly created item before it adds the item to the parent ItemGroup - see code. Unfortunately the call to save will trigger SaveableListener.onChange() to be called. The issue here is the Object that gets passed to the SaveableListener will have a parent that knows nothing about this Item. Arguably onChange() should not even be called for the item - as by definition it has not changed - just been born. Note this was observed whilst inspecting code around a proprietary plugin. Project: Jenkins Labels: jenkins Priority: Minor Reporter: James Nord This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-26127) java.net.MalformedURLException: no protocol: http%3A%2F%2Fmyserver
Zihao Yu commented on JENKINS-26127 java.net.MalformedURLException: no protocol: http%3A%2F%2Fmyserver I'm seeing this error too. Can we release a new version of the plugin to get the fix shipped? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [svn-tag-plugin] (JENKINS-3725) Build Parameters in SVN URL confuse svn-tag
Ravi Kumar Alagappan assigned JENKINS-3725 to Renjith V Build Parameters in SVN URL confuse svn-tag Change By: Ravi Kumar Alagappan (14/Apr/15 7:25 PM) Assignee: Ravi Kumar Alagappan Renjith V This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [svn-tag-plugin] (JENKINS-3725) Build Parameters in SVN URL confuse svn-tag
Ravi Kumar Alagappan assigned JENKINS-3725 to Ravi Kumar Alagappan Build Parameters in SVN URL confuse svn-tag Change By: Ravi Kumar Alagappan (14/Apr/15 7:25 PM) Assignee: Renjith V Ravi Kumar Alagappan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [svn-tag-plugin] (JENKINS-3725) Build Parameters in SVN URL confuse svn-tag
Ravi Kumar Alagappan assigned JENKINS-3725 to Renjith V Build Parameters in SVN URL confuse svn-tag Change By: Ravi Kumar Alagappan (14/Apr/15 7:22 PM) Assignee: k2nakamura Renjith V This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-dsl-plugin] (JENKINS-27932) Pull Request Publisher
Daniel Spilker resolved JENKINS-27932 as Fixed Pull Request Publisher Will be released in 1.33. Change By: Daniel Spilker (14/Apr/15 7:08 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-16365) allPermissions should try to load Jenkins's list of permissions
Daniel Spilker resolved JENKINS-16365 as Fixed allPermissions should try to load Jenkins's list of permissions Change By: Daniel Spilker (14/Apr/15 7:07 PM) Status: Reopened 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] [job-dsl-plugin] (JENKINS-27932) Pull Request Publisher
SCM/JIRA link daemon commented on JENKINS-27932 Pull Request Publisher Code changed in jenkins User: Daniel Spilker Path: docs/Home.md docs/Job-reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PullRequestPublisherContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/5ee360e84f43ab2b614b6a84717aed03ecf2de80 Log: Merge branch 'JENKINS-27932' Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/f3211d313682...5ee360e84f43 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-27365) Perforce ticketed credentials in p4 plugin incompatible with p4 command-line behavior
Russ Tremain commented on JENKINS-27365 Perforce ticketed credentials in p4 plugin incompatible with p4 command-line behavior Bug is limited to clustered p4d datacenter configurations. Fix to p4-java is pending. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [prioritysorter-plugin] (JENKINS-27770) AdvancedQueueSorter call to sort violates the comparison contract
SCM/JIRA link daemon commented on JENKINS-27770 AdvancedQueueSorter call to sort violates the comparison contract Code changed in jenkins User: emsa23 Path: src/main/java/jenkins/advancedqueue/sorter/AdvancedQueueSorter.java src/test/java/jenkins/advancedqueue/test/BasicTest.java http://jenkins-ci.org/commit/priority-sorter-plugin/52b80242c9d6d2781cb2f6c0d79937cee958d07b Log: JENKINS-27770 Makse sorter adhere to Java 7 compare contract. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [maven-plugin] (JENKINS-10406) Maven Jobs with "build modules in parallel" always ABORTED
Peter Buckley commented on JENKINS-10406 Maven Jobs with "build modules in parallel" always ABORTED I see (I think related?) issues with the "build modules in parallel" using 1.580.1. Symptoms can vary as any of the following: 1. sub-module builds don't report back (some sub-modules show up as "didn't run" but they did run) 2. overall build status is UNSTABLE and shows "No test failures" but sub-modules have test failures 3. a few sub-module builds are from build #2160 (a non-existent build) but the overall build was #2159 It would be great to get this "build modules in parallel" feature working well, it would be a more useful feature if it were stable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [release-plugin] (JENKINS-27942) MAven release build from jenkins using release plugin + Accurev as source code
Karthic Bala updated JENKINS-27942 MAven release build from jenkins using release plugin + Accurev as source code Change By: Karthic Bala (14/Apr/15 6:23 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [release-plugin] (JENKINS-27942) MAven release build from jenkins using release plugin + Accurev as source code
Karthic Bala assigned JENKINS-27942 to Karthic Bala MAven release build from jenkins using release plugin + Accurev as source code Change By: Karthic Bala (14/Apr/15 6:22 PM) Assignee: Karthic Bala This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [release-plugin] (JENKINS-27942) MAven release build from jenkins using release plugin + Accurev as source code
Karthic Bala created JENKINS-27942 MAven release build from jenkins using release plugin + Accurev as source code Issue Type: Bug Assignee: Unassigned Components: release-plugin Created: 14/Apr/15 6:22 PM Description: I am getting below error message, when i am trying to do release build from jenkins Waiting for Jenkins to finish collecting data[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on project release-engg-testing: An error occurred during the status check process: Can't login. 10:12:49 [ERROR] Failed authentication. Please re-try the 'login' command. 10:12:49 [ERROR] -> [Help 1] 10:12:49 [ERROR] 10:12:49 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. 10:12:49 [ERROR] Re-run Maven using the -X switch to enable full debug logging. 10:12:49 [ERROR] 10:12:49 [ERROR] For more information about the errors and possible solutions, please read the following articles: 10:12:49 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException Environment: In my testing environment. Project: Jenkins Priority: Minor Reporter: Karthic Bala This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27922) Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread
Jamie Doornbos updated JENKINS-27922 Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread I had to restart my server yesterday, so this thread dump represents about a day of build up. I can see the trajectory of doom here: there are 658 AgentServer threads. I can post another dump tomorrow or so when the server falls over. Change By: Jamie Doornbos (14/Apr/15 6:13 PM) Attachment: Thread dump [Jenkins].html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [urltrigger-plugin] (JENKINS-27941) Proxy user cannot be empty even if the proxy does not require authentication
Dave Hunt created JENKINS-27941 Proxy user cannot be empty even if the proxy does not require authentication Issue Type: Bug Assignee: Gregory Boissinot Components: urltrigger-plugin Created: 14/Apr/15 6:08 PM Description: When checking the box to use the Jenkins proxy, polling fails if a username is not defined, even if the proxy does not require authentication. Project: Jenkins Priority: Minor Reporter: Dave Hunt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [repo-plugin] (JENKINS-23262) Permission denied when using repo plugin with ssh-agent plugin
Geert Pante commented on JENKINS-23262 Permission denied when using repo plugin with ssh-agent plugin I have the same issue, even when my passphrase is empty. I think it's got to do with how ssh-agent works: http://www.snailbook.com/faq/about-agent.auto.html The ssh-agent injects variables into the environment, which can be picked up by other processes within the same session. The repo plugin probably does not run in the same session as the SSH Agent 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] [publish-over-ssh-plugin] (JENKINS-27703) Failure to connect - jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: TheKey]
Chadwick Bushnell commented on JENKINS-27703 Failure to connect - jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: TheKey] Worked perfectly. Thank you so much. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
ben s commented on JENKINS-23958 Pipe Broken Unfortunately I don't have any specific way to reproduce it. Most of our jobs are rather long, however. In fact when a job undergoes a fresh import into a new workspace, the likelihood of this error occurring seems to increase. The larger the project (the more assets) the more frequent. It often happens after Unity lists "Used Assets, sorted by uncompressed size:" 0.0 kb 0.0% Assets/Resources/path/to/some/file1 0.0 kb 0.0% Assets/Resources/path/to/some/file2 Failure on remote java.io.IOException: Pipe broken at java.io.PipedInputStream.read(PipedInputStream.java:322) at java.io.PipedInputStream.read(PipedInputStream.java:378) at java.io.InputStream.read(InputStream.java:101) at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64) But it also occurs in other points in time: Unloading 0 unused Assets to reduce memory usage. Loaded Objects now: 488. Total: 1.677543 ms (FindLiveObjects: 0.061794 ms CreateObjectMapping: 0.023056 ms MarkObjects: 1.508662 ms DeleteObjects: 0.005961 ms) Failure on remote java.io.IOException: Pipe broken at java.io.PipedInputStream.read(PipedInputStream.java:322) at java.io.PipedInputStream.read(PipedInputStream.java:378) at java.io.InputStream.read(InputStream.java:101) at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64) And: DisplayProgressbar: Android build DisplayProgressbar: Fetching assembly references DisplayProgressbar: Creating staging area DisplayProgressbar: Rebuilding resources DisplayProgressbar: Compiling resources DisplayProgressbar: Creating streaming package DisplayProgressbar: Creating asset package DisplayProgressbar: Creating APK package Failure on remote java.io.IOException: Pipe broken at java.io.PipedInputStream.read(PipedInputStream.java:322) at java.io.PipedInputStream.read(PipedInputStream.java:378) at java.io.InputStream.read(InputStream.java:101) at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64) All of the above are taken from completely separate projects. And yes, all of our jobs use the -logFile option -batchmode -quit -logFile "$WORKSPACE/unity.log" -projectPath $WORKSPACE -executeMethod Foo.bar I've never seen the error occur more than once per build, and it never seems to cause the build to fail, but if something else causes the build to fail it can be a serious red herring. After the "pipe broken" error, the Jenkins log picks up with the next immediate build step. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [fitnesse-plugin] (JENKINS-27940) Consider using jUnit output from FitNesse
Serge Zukov created JENKINS-27940 Consider using jUnit output from FitNesse Issue Type: New Feature Assignee: Unassigned Components: fitnesse-plugin Created: 14/Apr/15 4:54 PM Description: In addition to XML format current version of FitNesse supports jUnit format output. It is very basic at this point (but could expended). Environment: FitNesse plugin 1.12 Jenkins 1.600 Project: Jenkins Priority: Minor Reporter: Serge Zukov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
lacostej commented on JENKINS-23958 Pipe Broken Ben, > It's not clear to me how this is different from JENKINS-22492 since > they both appear to be identical according to the descriptions. I'm not sure which one I should watch, so I'm watching both Let's fix both then Do you happen to have a reliable way to reproduce this ? If not, have you tried to create one ? Is your job long running ? Do you use the -logFile option ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27939) DefaultJnlpSlaveReceiver should return true when rejecting a takeover.
David Hoover created JENKINS-27939 DefaultJnlpSlaveReceiver should return true when rejecting a takeover. Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Apr/15 4:48 PM Description: See https://github.com/jenkinsci/jenkins/pull/1649 In summary: JnlpAgentReceiver is documented as returning true after calling handshake.error() in case of failure to indicate that the receiver DID claim this node but had issues, but DefaultJnlpSlaveReceiver returns false. https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol2.java#L56-61 loops over all receivers until one claims it, so this is giving other receivers a chance at a node they shouldn't grab since the receiver wanted it but couldn't grab it. Assuming no others do, it also then continues on and gives the erroneous log message about not recognizing the node's name. Project: Jenkins Priority: Minor Reporter: David Hoover This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27917) Stack Trace when Checking for Updates
Mark Nejman commented on JENKINS-27917 Stack Trace when Checking for Updates The problem here is that this requires an assumption such as 'all invalid JSON responses are due to no proxy being set up', something I doubt is reasonably accurate. There can be any number of reasons. (In fact, the redirect seems to be fairly braindead to me, as it'll break all kinds of tools not used interactively. It should at least set some HTTP error code in the response so automated tools know to fail.) Do you think it would it help to wrap the error in a more generic 'failed to parse JSON update center metadata', and maybe show an excerpt of the data? Yes, I understand, you don't want to write error messages that are guessing what the issue is. I do think your proposed error message would be clear though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [fitnesse-plugin] (JENKINS-27938) Unable to expand collapsed SLIM tables
Serge Zukov created JENKINS-27938 Unable to expand collapsed SLIM tables Issue Type: Bug Assignee: Unassigned Components: fitnesse-plugin Created: 14/Apr/15 4:41 PM Description: New styling added in the latest FitNesse plugin makes SLIM tables appear as collapsed inside captured details, however there is no way to expand them. It seems like FitNesse plugin is missing some essential java-script to allow those tables behave same way they do in FitNesse. Another option is that java-script is included but unable to interact with elements inside Jenkins page. Environment: FitNesse plugin 1.12 Jenkins 1.600 Project: Jenkins Priority: Minor Reporter: Serge Zukov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-19752) Download build artifacts as zip generates a corrupted file
Andreas Kotes edited a comment on JENKINS-19752 Download build artifacts as zip generates a corrupted file btw: I also noticed that extended attributes (like an executable bit) are not preserved in those archives (created JENKINS-27937) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27937) Archives of Workspaces / Artifacts don't preserve extended attributes (like 'executable') although the Zip format supports it
Andreas Kotes created JENKINS-27937 Archives of Workspaces / Artifacts don't preserve extended attributes (like 'executable') although the Zip format supports it Issue Type: Improvement Assignee: Unassigned Components: core Created: 14/Apr/15 4:38 PM Description: Zips would support including extended attributes like the executable bit of files - this currently isn't done, so when a zipfile of a folder is downloaded, shell scripts stop being executable after unzipping Project: Jenkins Labels: archive workspace artifact artifact-download zip zipfile Priority: Minor Reporter: Andreas Kotes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-19752) Download build artifacts as zip generates a corrupted file
Andreas Kotes commented on JENKINS-19752 Download build artifacts as zip generates a corrupted file btw: I also noticed that extended attributes (like an executable bit) are not preserved in those archives This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [fitnesse-plugin] (JENKINS-27936) When few FitNesse test results being published in a single job they renamed into Summary
Serge Zukov created JENKINS-27936 When few FitNesse test results being published in a single job they renamed into Summary Issue Type: Bug Assignee: Unassigned Components: fitnesse-plugin Created: 14/Apr/15 4:33 PM Description: Expected: Test name for published test results to always match content of . Actual: When job contains more than one FitNesse test results published then test name appears as "Summary". Steps to reproduce: Given you have two test suites: TestSuite1 and TestSuite2 In a single job run TestSuite1 and produce TestSuite1.xml Run TestSuite2 and produce TestSuite2.xml Publish FitNesse tests using *.xml as a mask Upon execution FitNesse test results (and test history) will contain Summary as test name. P.S. Same would occur if you use copy artifacts plugin to collect all FitNesse XML files into a single job and publish them simultaneously. Environment: Jenkins ver. 1.608; FitNesse Plugin 1.12 Project: Jenkins Priority: Minor Reporter: Serge Zukov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [slack-plugin] (JENKINS-27935) Slack plugin 1.7 fails to post to channel; had to revert to 1.2
M Chon updated JENKINS-27935 Slack plugin 1.7 fails to post to channel; had to revert to 1.2 Change By: M Chon (14/Apr/15 4:18 PM) Description: For some reason, on a few of our Jenkins servers, the Slack 1.7 plugin fails to post messages to the slack channel. We have had to revert to version 1.2 of the plugin. In comparing the project configs and the console logs, there is no apparent reason for this. This is with projects we have imported onto these machines from older machines. New projects created after the 1.7 plugin was installed seem to post just fine. The new machines are all behind a proxy server. Not sure if that makes a difference. However, since newly created jobs seem to use the Slack 1.7 plugin just fine, it is probably a red herring. I'm happy to collect debug data if you can provide any suggestions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [slack-plugin] (JENKINS-27935) Slack plugin 1.7 fails to post to channel; had to revert to 1.2
M Chon updated JENKINS-27935 Slack plugin 1.7 fails to post to channel; had to revert to 1.2 Change By: M Chon (14/Apr/15 4:18 PM) Description: For some reason, on a few of our Jenkins servers, the Slack 1.7 plugin fails to post messages to the slack channel. We have had to revert to version 1.2 of the plugin. In comparing the project configs and the console logs, there is no apparent reason for this. This is with projects we have imported onto these machines from older machines. New projects created after the 1.7 plugin was installed seem to post just fine. The new machines are all behind a proxy server. Not sure if that makes a difference. However, since newly created jobs seem to use the Slack 1.7 plugin just fine, it is probably a red herring.I'm happy to collect debug data if you can provide any suggestions for doing so . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
ben s edited a comment on JENKINS-23958 Pipe Broken It's not clear to me how this is different from JENKINS-22492 since they both appear to be identical according to the descriptions. I'm not sure which one I should watch, so I'm watching both Anyway, we are having the broken pipe issue as well. Details: Linux master (Ubuntu) Unity builds occur on remote Mac OSX slaves Jenkins v1.607 Unity3d plugin v0.7 Various Unity versions: 3.5.7, 4.5.4, 4.6.4. Doesn't seem to make a difference. I'm here today because I feel like after our recent Jenkins update to 1.607 this error has started occurring more frequently, however I can't say for certain. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [slack-plugin] (JENKINS-27935) Slack plugin 1.7 fails to post to channel; had to revert to 1.2
M Chon created JENKINS-27935 Slack plugin 1.7 fails to post to channel; had to revert to 1.2 Issue Type: Bug Assignee: Unassigned Components: slack-plugin Created: 14/Apr/15 4:15 PM Description: For some reason, on a few of our Jenkins servers, the Slack 1.7 plugin fails to post messages to the slack channel. We have had to revert to version 1.2 of the plugin. In comparing the project configs and the console logs, there is no apparent reason for this. This is with projects we have imported onto these machines from older machines. New projects created after the 1.7 plugin was installed seem to post just fine. The new machines are all behind a proxy server. Not sure if that makes a difference. However, since newly created jobs seem to use the Slack 1.7 plugin just fine, it is probably a red herring. Environment: Ubuntu 14.04.2 Jenkins 1.596.1 Slack Plugin 1.7 Project: Jenkins Priority: Minor Reporter: M Chon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
ben s commented on JENKINS-23958 Pipe Broken It's not clear to me how this is different from JENKINS-22492 since they both appear to be identical according to the descriptions. I'm not sure which one I should watch, so I'm watching both Anyway, we are having the broken pipe issue as well. Details: Linux master (Ubuntu) Unity builds occur on remote Mac OSX slaves Jenkins v1.607 Unity3d plugin v0.7 I'm here today because I feel like after our recent Jenkins update to 1.607 this error has started occurring more frequently, however I can't say for certain. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [_test] (JENKINS-27934) Can not add promotion process named 'Closed Beta'
Andrei Petrov created JENKINS-27934 Can not add promotion process named 'Closed Beta' Issue Type: Bug Assignee: Oleg Nenashev Components: _test Created: 14/Apr/15 4:10 PM Description: 1. Create new Multi-Configurational project from the template 2. Add promotion process called 'Closed beta' 3. You will get an exception as described below A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: java.lang.IllegalArgumentException: Job Closed beta already exists at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) Project: Jenkins Priority: Critical Reporter: Andrei Petrov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [throttle-concurrent-builds-plugin] (JENKINS-20211) Pairs of throttled node labels no longer seem to work starting from version 1.536
Dwane Pottratz commented on JENKINS-20211 Pairs of throttled node labels no longer seem to work starting from version 1.536 I am currently seeing this issue. Jenkins 1.609 with Throttle 1.8.4 I have read that 'Priority Sort Plugin' can cause issues with Throttle. I have Priority 2.9. I have tried several different configurations. I don't see anything that is working. I think that throttling per project is working but have not been able to confirm it. I have tired setting the max per label. I have tried without setting a max per label. Nothing seems to work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27927) Some interface idioms do not work in Groovy CPS
Thomas Dalton
commented on JENKINS-27927
Some interface idioms do not work in Groovy CPS
I'm glad the intention is aligned with the desire to have these groovy language features available and understand that support for interface will require work in the groovy CPS.
In the short term though, is there a recommended workaround that could provide some interface like equivalent? Or is it just not possible to do anything like this at this stage?
Perhaps pass HashMaps of Closures between the top level "classes" as per
https://github.com/jenkinsci/workflow-plugin/blob/master/cps-global-lib/README.md#writing-shared-code
e.g.
org/foo/Zot.groovy
package org.foo
// Closures define the interface for Zot
Closure show
Closure name
def specify_interface (Hashmap hm) {
this.show = hm["show"]
this.name = hm["name"]
}
flow.groovy
node {
def z = new org.foo.Zot()
z.specify_interface(["show": { echo "Hello" }, "name": { return "Bernard" }])
// you can then pass z around beyond the scope of flow.groovy
z.show()
echo z.name()
}
Or is there a more elegant way within the constraints of what is and what is not possible today?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-27928) environment variable changes are not applied.
marlene cote commented on JENKINS-27928 environment variable changes are not applied. I need to schedule the restart of jenkins to finish the uninstall of the plugin.. I will get back to you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27928) environment variable changes are not applied.
Daniel Beck
commented on JENKINS-27928
environment variable changes are not applied.
Node specific env vars ("environment variables, list of key-value pairs") are a core feature.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [workflow-plugin] (JENKINS-27905) stage concurrency allows 1 thread to be blocked at a time, others fail and hang job
Thomas Dalton
commented on JENKINS-27905
stage concurrency allows 1 thread to be blocked at a time, others fail and hang job
A stage within parallel could be a common use-case for CI. For example, a given workflow may need multiple builds as well as multiple independent tests, all of which could run in parallel on the same server - each of these flows could easily benefit from having stages.
You could work around this by defining flows for each of the parallel builds, and then kicking these off e.g.
parallel([build_1: {build job: "FooFlow"}, build_2: {build job: "BarFlow"}])
Where FooFlow and BarFlow could identify their own stages, but this would require further setup on the jenkins server, more jobs to configure, and detract from the usefulness of the workflow-plugin to do this programmatically.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-plugin] (JENKINS-26158) Active Directory authentication for Subversion plugin fails
Benny Prange
commented on JENKINS-26158
Active Directory authentication for Subversion plugin fails
I'm having the same issue. My workaround is to use in ant and call svn directly from commandline. Eg:
"svn">
"checkout --non-interactive --trust-server-cert --username ${svn.user} --password ${svn.psw} ${svn.url} ${param.dep.dest}" />
Nevertheless I would love to see this bug 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] [envinject-plugin] (JENKINS-27496) NPE during submission of EnvInject JobProperty when the formis empty
Oleg Nenashev resolved JENKINS-27496 as Fixed NPE during submission of EnvInject JobProperty when the formis empty 1.91.2 has been released today. Marking as fixed Change By: Oleg Nenashev (14/Apr/15 3:13 PM) Status: In Progress 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] [workflow-plugin] (JENKINS-27927) Some interface idioms do not work in Groovy CPS
Jesse Glick commented on JENKINS-27927 Some interface idioms do not work in Groovy CPS Sure, the intention is to support all Groovy language features, but there is a way to go before we get there. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27925) Build step is not always saved
Daniel Beck commented on JENKINS-27925 Build step is not always saved Interesting. Does this work for newly created projects? Are they freestyle projects? Are any errors shown in the JS console of your browser? In the developer tools of your browser, what is the request sent on clicking 'Send' in step 7? Is this reproducible 100% of the time, or only sometimes? Are the two original Windows batch commands empty, or do they contain text? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27928) environment variable changes are not applied.
marlene cote edited a comment on JENKINS-27928 environment variable changes are not applied. won't I lose the ability to specify and use env variables if I uninstall that 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-27928) environment variable changes are not applied.
marlene cote commented on JENKINS-27928 environment variable changes are not applied. won't I lose the ability to specify env variables if I uninstall that 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] [clearcase-ucm-plugin] (JENKINS-26985) Poll rebase functionality (case 12578)
Mads Nielsen resolved JENKINS-26985 as Fixed Poll rebase functionality (case 12578) Change By: Mads Nielsen (14/Apr/15 2:44 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27928) environment variable changes are not applied.
Daniel Beck commented on JENKINS-27928 environment variable changes are not applied. Does the same issue occur without envinject? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27928) environment variable changes are not applied.
marlene cote updated JENKINS-27928 environment variable changes are not applied. Change By: marlene cote (14/Apr/15 2:42 PM) Environment: jenkins server - windows server 2008 R2 SP1 64 bit jenkins client - windows server 2008 R2 SP1 64 bit jenkins server version 1.608 recently upgraded from 1.598I have not tried to downgrade because the teams were not changing this variable before now either.multiple browsers tried, no effect. firefox v-37.0.1, IE v10windows installer usedslaves installed vi web page - windows service installed - started via java web start java on server - standard edition 7_67 32 bitjava on client - standard edition 7_67 32 bitsystem info page data below. Description: When changing an existing node environment variable (%JENKINS_BUILD_REPOSITORY%) value in the node's configuration dialog, the change is not applied. Looking at the systemInfo of the node shows, that the variable still has got the old value. Also reloading the Jenkins configuration from disk did not help.The only thing that seems to help is a reboot of the jenkins server. Restarting the slave isn't enough. Here is some more detail from the developers using Jenkins for their builds.I know you should only have to restart the Jenkins slave service and know how to do that. I’ve tried that. I’ve also tried rebooting the machine, which also restarts the Jenkins slave service. Same result.I’ve checked the environment variables on our build server (BOSBLD-TEAM6): JENKINS_BUILD_REPOSITORY=MakoSP2_Bld_0400I’ve run a build job and captured the batch file that gets deployed to our build server to actually run the build, the contents of which are:echo %JENKINS_BUILD_REPOSITORY%cd "%JENKINS_INT_BUILD_VIEW%\release_eng\Build_scripts\scripts\PS"powershell.exe -NoProfile -ExecutionPolicy unrestricted -Command "%JENKINS_INT_BUILD_VIEW%\release_eng\Build_scripts\scripts\PS\PSBuild.ps1" ait DB -DownloadProprietaryIfNewer "%JENKINS_BUILD_REPOSITORY%"exit %ERRORLEVEL%I’ve executed this batch file on our build server directly and get the expected results:Using staging area: '\\bosrdfs1\MakoSP2_Build\MakoSP2_Bld_0400'. The problem is, when the build is run from our Jenkins page, it doesn’t reflect the proper version:Using staging area: '\\bosrdfs1\MakoSP2_Build\MakoSP2_Bld_0200'. from system information pageawt.toolkit sun.awt.windows.WToolkit executable-war D:\Jenkins\jenkins.war file.encoding Cp1252 file.encoding.pkg sun.io file.separator \ hudson.diyChunking true hudson.lifecycle hudson.lifecycle.WindowsServiceLifecycle java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.awt.windows.WPrinterJob java.class.path D:\Jenkins\jenkins.war java.class.version 51.0 java.endorsed.dirs D:\Jenkins\jre\lib\endorsed java.ext.dirs D:\Jenkins\jre\lib\ext;C:\Windows\Sun\Java\lib\ext java.home D:\Jenkins\jre java.io.tmpdir C:\Windows\TEMP\ java.library.path D:\Jenkins\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\7-zip;C:\Program Files (x86)\IBM\RationalSDLC\Clearquest\cqcli\bin;C:\Program Files (x86)\IBM\RationalSDLC\common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files (x86)\IBM\RationalSDLC\ClearCase\bin;c:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft Team Foundation Server 2012 Power Tools\;C:\Program Files (x86)\Microsoft Team Foundation Server 2012 Power Tools\Best Practices Analyzer\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\IBM\RationalSDLC\ClearCase\RemoteClient\cteapis;C:\Program Files (x86)\IBM\gsk8\lib;C:\Program Files (x86)\IBM\gsk8\bin;c:\opscode\chef\bin;;. java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.7.0_25-b17 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://
[JIRA] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)
Dmytro Kryvenko closed JENKINS-26726 as Cannot Reproduce java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70) Change By: Dmytro Kryvenko (14/Apr/15 2:15 PM) Status: Open Closed Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-27927) Some interface idioms do not work in Groovy CPS
Thomas Dalton commented on JENKINS-27927 Some interface idioms do not work in Groovy CPS Hi Jesse, Thanks for getting back to me again. The reason I'm looking at the workflow-plugin is because it allows a programmatic interface, and it is potentially a very powerful means to share jenkins job setups across multiple teams and engineers, and even more so if it can work in a way that provides the extensibility and reuse that the groovy language can offer. This means things like class inheritance, interfaces and other OO techniques are desirable and of particular interest to me. Moreover, the flows I'm looking at are inherently quite complex and I would ideally like to generate infra for them that could be used by a number of people/teams - not just copy/pasted. If I go with conservative, I fear I will end up with multiple copies of the same rehashed code for each instance where it is actually used - and that means more places for it to go wrong and maintain. So what would really set the workflow-plugin apart from e.g. a typical multijob setup is the ability to do some of the less "conservative", more "groovy" things Regards, Tom. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [mailer-plugin] (JENKINS-27933) mailer-plugin does not support mail adresses without an @-sign anymore
Patric Rufflar created JENKINS-27933 mailer-plugin does not support mail adresses without an @-sign anymore Issue Type: Bug Assignee: Unassigned Components: mailer-plugin Created: 14/Apr/15 2:08 PM Description: The mailer-plugin does not support mail adresses without an '@' anymore (assuming that a default mail suffix has not been configured). While this is reasonable for internet email traffic, internal/local mail adresses like 'jenkins-ci' might be perfectly valid. This is caused by jenkins.plugins.mailer.tasks.MimeMessageBuilder.toNormalizedAddress(String) which returns null in such cases. Project: Jenkins Priority: Major Reporter: Patric Rufflar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)
Dmytro Kryvenko commented on JENKINS-26726 java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70) Sorry for a delay. I was trying to reproduce this one again with no luck. It seems like a 3rd party plugin caused this behaviour originally and probably it has been fixed on their side. Closing this issue for now, will reopen in case of luck with reproducing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
