[JIRA] [copyartifact-plugin] (JENKINS-22453) Invalid symbolic links get archived but cannot be copied using Copy Artifacts
ikedam closed JENKINS-22453 as Duplicate Invalid symbolic links get archived but cannot be copied using Copy Artifacts Fixed in copyartifact-1.35. It will be available in a day. Change By: ikedam (01/Mar/15 7:16 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] [copyartifact-plugin] (JENKINS-20546) Preserve symlinks when copying artifacts
ikedam closed JENKINS-20546 as Fixed Preserve symlinks when copying artifacts The fix is released in copyartifact-1.35. It will be available in a day. Change By: ikedam (01/Mar/15 7:16 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] [copyartifact-plugin] (JENKINS-26694) Workflow build Parameters are not exposed to CopyArtifact
ikedam closed JENKINS-26694 as Fixed Workflow build Parameters are not exposed to CopyArtifact Fixed in copyartifact-1.35. It will be available in a day. Please try that. Change By: ikedam (01/Mar/15 7:17 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] [workflow-plugin] (JENKINS-26030) Build deletion fails due to file lock
SCM/JIRA link daemon commented on JENKINS-26030 Build deletion fails due to file lock Code changed in jenkins User: ikedam Path: src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java src/test/java/hudson/plugins/copyartifact/CopyArtifactWorkflowTest.java http://jenkins-ci.org/commit/copyartifact-plugin/1308f8da0170ff3010054417bdcf5d88bd536df4 Log: JENKINS-26694 Make tests succeed on Windows: HudsonTestCase using workflow-1.1 fails for JENKINS-26030. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26694) Workflow build Parameters are not exposed to CopyArtifact
SCM/JIRA link daemon commented on JENKINS-26694 Workflow build Parameters are not exposed to CopyArtifact Code changed in jenkins User: ikedam Path: src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java http://jenkins-ci.org/commit/copyartifact-plugin/abd5a3067a3a0769115cd73716978545ff7892bc Log: JENKINS-26694 Added a test to reproduce JENKINS-26694. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26694) Workflow build Parameters are not exposed to CopyArtifact
SCM/JIRA link daemon commented on JENKINS-26694 Workflow build Parameters are not exposed to CopyArtifact Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/ParametersBuildFilter.java src/test/java/hudson/plugins/copyartifact/CopyArtifactWorkflowTest.java http://jenkins-ci.org/commit/copyartifact-plugin/7802e455a2479f545e5f7fa58d1ca6fdd8871028 Log: Merge pull request #59 from ikedam/feature/JENKINS-26694_ParametersBuildFilterForWorkflow JENKINS-26694 Make ParameterBuildFilter applicable to WorkflowJobs. Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/ec41cbdd914d...7802e455a247 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26694) Workflow build Parameters are not exposed to CopyArtifact
SCM/JIRA link daemon commented on JENKINS-26694 Workflow build Parameters are not exposed to CopyArtifact Code changed in jenkins User: ikedam Path: src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java src/test/java/hudson/plugins/copyartifact/CopyArtifactWorkflowTest.java http://jenkins-ci.org/commit/copyartifact-plugin/1308f8da0170ff3010054417bdcf5d88bd536df4 Log: JENKINS-26694 Make tests succeed on Windows: HudsonTestCase using workflow-1.1 fails for JENKINS-26030. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26694) Workflow build Parameters are not exposed to CopyArtifact
SCM/JIRA link daemon resolved JENKINS-26694 as Fixed Workflow build Parameters are not exposed to CopyArtifact Change By: SCM/JIRA link daemon (01/Mar/15 5:54 AM) 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] [copyartifact-plugin] (JENKINS-26694) Workflow build Parameters are not exposed to CopyArtifact
SCM/JIRA link daemon commented on JENKINS-26694 Workflow build Parameters are not exposed to CopyArtifact Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/ParametersBuildFilter.java http://jenkins-ci.org/commit/copyartifact-plugin/53462816b1d9f3455a3422d89bc5d6feaff274f1 Log: [FIXED JENKINS-26694] ParameterBuildFilter now works also for WorkflowRun. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27176) plugin management must log details about upgrades to support forensic analysis
Jason Pyeron commented on JENKINS-27176 plugin management must log details about upgrades to support forensic analysis The UI may also benefit from this change. On restart Jenkins crashed and the admin was left with: Installing Plugins/Upgrades Preparation Checking internet connectivity Checking update center connectivity Success GitHub Plugin Downloaded Successfully. Will be activated during the next boot Git Client Plugin Downloaded Successfully. Will be activated during the next boot Git Plugin Downloaded Successfully. Will be activated during the next boot Script Security Plugin Downloaded Successfully. Will be activated during the next boot JUnit Plugin Downloaded Successfully. Will be activated during the next boot Matrix Project Plugin Downloaded Successfully. Will be activated during the next boot Mailer Downloaded Successfully. Will be activated during the next boot Git Client Plugin Downloaded Successfully. Will be activated during the next boot Restarting Jenkins Running on the screen. If there were version numbers, the SA would have a place to start with debugging. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27177) There should be a command line mechism to disable plugins
Jason Pyeron commented on JENKINS-27177 There should be a command line mechism to disable plugins related: https://wiki.jenkins-ci.org/display/JENKINS/Removing+and+disabling+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] [core] (JENKINS-27175) Loading config.xml sections dependent on failed plugins, must not disable Jenkins
Jason Pyeron updated JENKINS-27175 Loading config.xml sections dependent on failed plugins, must not disable Jenkins Change By: Jason Pyeron (01/Mar/15 2:45 AM) 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] [core] (JENKINS-27177) There should be a command line mechism to disable plugins
Jason Pyeron created JENKINS-27177 There should be a command line mechism to disable plugins Issue Type: New Feature Assignee: Unassigned Components: core Created: 01/Mar/15 2:45 AM Description: The typical system administrator, to urgently recover from a problem, will need to use local system commands to disable plugins indicated a problem in the Jenkins logs. The first step is to include a "README" in the install and/or plugin directories. This readme file may be as simple as to link to the Jenkins online documentation describing the file structure and configurations. Secondly, there should be clear documentation on the "manual" backup/restore/disabling plugins and their configurations. Lastly, if it is not currently possible to disable a plugin via the command line and/or config update a process should be added to Jenkins to do so. See thread https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFuG9t_F4zL%3D7ncg53XdZG9dZD-GdWQ1dtTN53DrKjm8g%40mail.gmail.com Project: Jenkins Priority: Major Reporter: Jason Pyeron This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27176) plugin management must log details about upgrades to support forensic analysis
Jason Pyeron created JENKINS-27176 plugin management must log details about upgrades to support forensic analysis Issue Type: Bug Assignee: Jason Pyeron Components: core Created: 01/Mar/15 2:34 AM Description: The current loging is insufficient level of detial and criticality upgrade: Feb 28, 2015 10:49:57 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of GitHub Plugin on behalf of jpyeron Feb 28, 2015 10:49:57 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading GitHub Plugin Feb 28, 2015 10:49:58 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of Git Client Plugin on behalf of jpyeron Feb 28, 2015 10:49:59 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading Git Client Plugin Feb 28, 2015 10:50:00 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of Git Plugin on behalf of jpyeron Feb 28, 2015 10:50:00 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading Git Plugin Feb 28, 2015 10:50:01 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of Script Security Plugin on behalf of jpyeron Feb 28, 2015 10:50:02 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading Script Security Plugin Feb 28, 2015 10:50:02 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of JUnit Plugin on behalf of jpyeron Feb 28, 2015 10:50:02 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading JUnit Plugin Feb 28, 2015 10:50:02 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of Matrix Project Plugin on behalf of jpyeron Feb 28, 2015 10:50:03 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading Matrix Project Plugin Feb 28, 2015 10:50:03 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of Mailer on behalf of jpyeron Feb 28, 2015 10:50:03 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading Mailer Feb 28, 2015 10:50:03 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of Git Client Plugin on behalf of jpyeron Feb 28, 2015 10:50:04 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading Git Client Plugin Feb 28, 2015 11:20:02 AM hudson.model.UpdateCenter doSafeRestart INFO: Scheduling Jenkins reboot downgrade: Feb 28, 2015 12:28:10 PM hudson.model.UpdateCenter$PluginDowngradeJob run INFO: Starting the downgrade of Matrix Project Plugin on behalf of anonymous Feb 28, 2015 12:28:10 PM hudson.model.UpdateCenter$PluginDowngradeJob run INFO: Downgrade successful: Matrix Project Plugin The upgrade and downgrade actions need to log the old and new version numbers for each plugin change at the warning level, to ensure it being recorded to the log. See thread https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFuG9t_F4zL%3D7ncg53XdZG9dZD-GdWQ1dtTN53DrKjm8g%40mail.gmail.com Project: Jenkins Priority: Critical Reporter: Jason Pyeron This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegro
[JIRA] [nunit-plugin] (JENKINS-27043) NUnit plugin fails while converting to JUnit XML
Bruno P. Kinoshita commented on JENKINS-27043 NUnit plugin fails while converting to JUnit XML Sorry Ren, I haven't had time to reproduce the issue in my dev environment. I'll be busy until mid May with personal and $work errands, but if you have a pull request in GitHub we can discuss and merge/release it. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27175) Loading config.xml sections dependent on failed plugins, must not disable Jenkins
Jason Pyeron created JENKINS-27175 Loading config.xml sections dependent on failed plugins, must not disable Jenkins Issue Type: Bug Assignee: Unassigned Components: core Created: 01/Mar/15 2:24 AM Description: config.xml contained , which relied on a failed plugin. As such the loading of Jenkins was halted. There was no ability to admin Jenkins from the web UI, such as downgrading the ofending plugin. See thread https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFuG9t_F4zL%3D7ncg53XdZG9dZD-GdWQ1dtTN53DrKjm8g%40mail.gmail.com Project: Jenkins Priority: Minor Reporter: Jason Pyeron This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [git-client-plugin] (JENKINS-27174) Git client API reports null pointer exception in log
Mark Waite updated JENKINS-27174 Git client API reports null pointer exception in log Change By: Mark Waite (01/Mar/15 1:59 AM) Summary: Git client call API reports null pointer exception in log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27069) Cannot access subversion repository from Workflow
Ken DeLong edited a comment on JENKINS-27069 Cannot access subversion repository from Workflow That helped! I totally missed the double square brackets. However, it's still not working. With the latest version of the Subversion plugin (2.5), I get this: Running: Allocate node : Start Running on master in /var/jenkins_home/workspace/WorkflowTest Running: Allocate node : Body : Start Running: General SCM Checking out a fresh workspace because /var/jenkins_home/workspace/WorkflowTest/trunk doesn't exist Cleaning local Directory trunk Checking out https://secure3.svnrepository.com/myrepo/trunk at revision '2015-03-01T00:04:50.368 +' ERROR: Failed to check out https://secure3.svnrepository.com/myrepo/trunk org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy at '/var/jenkins_home/workspace/WorkflowTest/trunk' (format '100'). at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDbRoot.(SVNWCDbRoot.java:104) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.init(SVNWCDb.java:242) at org.tmatesoft.svn.core.internal.wc17.SVNWCContext.initWC(SVNWCContext.java:4979) at org.tmatesoft.svn.core.internal.wc17.SVNWCContext.initializeWC(SVNWCContext.java:4928) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:783) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:26) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:11) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:115) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:170) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:133) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:991) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948) at hudson.FilePath.act(FilePath.java:981) at hudson.FilePath.act(FilePath.java:959) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:833) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:106) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:70) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start(AbstractSynchronousStepExecution.java:34) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:136) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:98) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:15) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:69) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:100) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.
[JIRA] [workflow-plugin] (JENKINS-27069) Cannot access subversion repository from Workflow
Ken DeLong
commented on JENKINS-27069
Cannot access subversion repository from Workflow
After finding https://issues.jenkins-ci.org/browse/JENKINS-26458, I downgraded my subversion plugin to 2.4.5. Now I get the "you must override the new overload of checkout" as well, just like with 1.54.
The other solution suggested there was to set Jenkins' overall svn version to 1.8; however, on the Configure System page the largest version available in the dropdown list was 1.7, so I couldn't try that.
My entire workflow script is:
def cid = '123-123-123-123'
node {
checkout scm: [ $class: "SubversionSCM", locations: [[ remote:'https://secure3.svnrepository.com/myrepo/trunk', credentialsId: cid]] ]
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [git-client-plugin] (JENKINS-27174) Git client call reports null pointer exception in log
Mark Waite assigned JENKINS-27174 to Mark Waite Git client call reports null pointer exception in log Change By: Mark Waite (01/Mar/15 1:23 AM) Assignee: Nicolas De Loof Mark Waite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [git-client-plugin] (JENKINS-27174) Git client call reports null pointer exception in log
Mark Waite created JENKINS-27174 Git client call reports null pointer exception in log Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin Created: 01/Mar/15 1:19 AM Description: While reviewing the log of my Jenkins server at work, I found null pointer exceptions from a call to GitObject in the git client plugin. The NPE does not seem to harm functionality, but there really should not be NPE's in the log... Error while serving http://jenkins-events.ca.com:8080/job/EMS-SystemTest-GH/63/api/xml java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor136.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.Chaine
[JIRA] [openid-plugin] (JENKINS-27159) username is the server URL
Daniel Beck resolved JENKINS-27159 as Duplicate username is the server URL You know about JENKINS-26003. Don't file duplicates. Change By: Daniel Beck (01/Mar/15 1:14 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] [jira-plugin] (JENKINS-13364) Can Not Change JIRA Password
Daniel Beck resolved JENKINS-13364 as Not A Defect Can Not Change JIRA Password This Jira is integrated with an LDAP service run by the Jenkins project to share logins between Jira, Confluence, Artifactory, and Subversion. The account management app for this is located at http://jenkins-ci.org/account/ FWIW nobody cared about this report in years because it was reported against the JIRA Plugin for Jenkins, not the Jenkins project infrastructure. Change By: Daniel Beck (01/Mar/15 1:11 AM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27069) Cannot access subversion repository from Workflow
Ken DeLong commented on JENKINS-27069 Cannot access subversion repository from Workflow That helped! I totally missed the double square brackets. However, it's still not working. With the latest version of the Subversion plugin (2.5), I get this: Running: Allocate node : Start Running on master in /var/jenkins_home/workspace/WorkflowTest Running: Allocate node : Body : Start Running: General SCM Checking out a fresh workspace because /var/jenkins_home/workspace/WorkflowTest/trunk doesn't exist Cleaning local Directory trunk Checking out https://secure3.svnrepository.com/myrepo/trunk at revision '2015-03-01T00:04:50.368 +' ERROR: Failed to check out https://secure3.svnrepository.com/myrepo/trunk org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy at '/var/jenkins_home/workspace/WorkflowTest/trunk' (format '100'). at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDbRoot.(SVNWCDbRoot.java:104) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.init(SVNWCDb.java:242) at org.tmatesoft.svn.core.internal.wc17.SVNWCContext.initWC(SVNWCContext.java:4979) at org.tmatesoft.svn.core.internal.wc17.SVNWCContext.initializeWC(SVNWCContext.java:4928) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:783) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:26) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:11) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:115) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:170) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:133) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:991) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948) at hudson.FilePath.act(FilePath.java:981) at hudson.FilePath.act(FilePath.java:959) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:833) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:106) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:70) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start(AbstractSynchronousStepExecution.java:34) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:136) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:98) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:15) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:69) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:100) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.
[JIRA] [matrix-project-plugin] (JENKINS-25783) very long build directory paths are created by Matrix project, and difficult directcory names
Daniel Beck
commented on JENKINS-25783
very long build directory paths are created by Matrix project, and difficult directcory names
FWIW there's a global (Jenkins-wide) option to use short sub-workspace paths for matrix projects: {{ hudson.matrix.MatrixConfiguration.useShortWorkspaceName}}
More information on:
https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-25783) very long build directory paths are created by Matrix project, and difficult directcory names
Daniel Beck edited a comment on JENKINS-25783 very long build directory paths are created by Matrix project, and difficult directcory names FWIW there's a global (Jenkins-wide) option to use short sub-workspace paths for matrix projects: hudson.matrix.MatrixConfiguration.useShortWorkspaceName More information on: https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-25783) very long build directory paths are created by Matrix project, and difficult directcory names
Jordan Spiker edited a comment on JENKINS-25783 very long build directory paths are created by Matrix project, and difficult directcory names @Daniel @Pascal The worst offender is python virtualenv. Wrapper scripts insert the shebang of the interpreter, which is in the workspace. So "myProg.py" would have #!/path/to/my/job/label1&&label2/venv/bin/python ... I unfortunately have to wrap everything in a shell script to re-write the shebang. I'd also like to add (most) linux kernels limit the shebang line to 127 characters, which is easily outdone with big matrix jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-25783) very long build directory paths are created by Matrix project, and difficult directcory names
Jordan Spiker commented on JENKINS-25783 very long build directory paths are created by Matrix project, and difficult directcory names @Daniel @Pascal The worst offender is python virtualenv. Wrapper scripts insert the shebang of the interpreter, which is in the workspace. So "myProg.py" would have #!/path/to/my/job/label1&&label2/venv/bin/python ... I unfortunately have to wrap everything in a shell script to re-write the shebang. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [mstest-plugin] (JENKINS-11332) The "Timeout" and "error" state test result is treated as failed one (VS 2010).
Ivo Bellin Salarin assigned JENKINS-11332 to Ivo Bellin Salarin The "Timeout" and "error" state test result is treated as failed one (VS 2010). Change By: Ivo Bellin Salarin (28/Feb/15 10:15 PM) Assignee: acmarques Ivo Bellin Salarin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [mstest-plugin] (JENKINS-19384) Adding stdout to be displayed in your test results
Ivo Bellin Salarin assigned JENKINS-19384 to Ivo Bellin Salarin Adding stdout to be displayed in your test results Change By: Ivo Bellin Salarin (28/Feb/15 10:14 PM) Assignee: Ivo Bellin Salarin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [mstestrunner-plugin] (JENKINS-13290) MS Test plugin does not correctly wrap it's call to the command line in quotation marks.
Ivo Bellin Salarin edited a comment on JENKINS-13290 MS Test plugin does not correctly wrap it's call to the command line in quotation marks. Moved to mstestrunner-plugin. The mstest plugin doesn't execute mstest.exe. The mstest-plugin finds the trx files in the workspace and converts them to junit format. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [mstestrunner-plugin] (JENKINS-13290) MS Test plugin does not correctly wrap it's call to the command line in quotation marks.
Ivo Bellin Salarin commented on JENKINS-13290 MS Test plugin does not correctly wrap it's call to the command line in quotation marks. Moved to mstestrunner-plugin. The mstest plugin doesn't execute mstest.exe. The mstest-plugin finds the trx files in the workspace and converts them to juni format. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [mstestrunner-plugin] (JENKINS-13290) MS Test plugin does not correctly wrap it's call to the command line in quotation marks.
Ivo Bellin Salarin stopped work on JENKINS-13290 MS Test plugin does not correctly wrap it's call to the command line in quotation marks. Change By: Ivo Bellin Salarin (28/Feb/15 10:11 PM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mstestrunner-plugin] (JENKINS-13290) MS Test plugin does not correctly wrap it's call to the command line in quotation marks.
Ivo Bellin Salarin started work on JENKINS-13290 MS Test plugin does not correctly wrap it's call to the command line in quotation marks. Change By: Ivo Bellin Salarin (28/Feb/15 10:11 PM) 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] [mstestrunner-plugin] (JENKINS-13290) MS Test plugin does not correctly wrap it's call to the command line in quotation marks.
Ivo Bellin Salarin updated JENKINS-13290 MS Test plugin does not correctly wrap it's call to the command line in quotation marks. Change By: Ivo Bellin Salarin (28/Feb/15 10:12 PM) Component/s: mstestrunner-plugin Component/s: mstest-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] [mstest-plugin] (JENKINS-8193) Fix for data-driven tests with mstest (JENKINS-4075)
Ivo Bellin Salarin assigned JENKINS-8193 to Ivo Bellin Salarin Fix for data-driven tests with mstest (JENKINS-4075) Change By: Ivo Bellin Salarin (28/Feb/15 10:09 PM) Assignee: acmarques Ivo Bellin Salarin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [mstest-plugin] (JENKINS-7458) Support for "orderedtest" results
Ivo Bellin Salarin assigned JENKINS-7458 to Ivo Bellin Salarin Support for "orderedtest" results Change By: Ivo Bellin Salarin (28/Feb/15 10:08 PM) Assignee: acmarques Ivo Bellin Salarin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [mstest-plugin] (JENKINS-17610) MSTest plugin don't show VSTS standard console output message for passed test cases in Jenkins.
Ivo Bellin Salarin commented on JENKINS-17610 MSTest plugin don't show VSTS standard console output message for passed test cases in Jenkins. Could you please provide a TRX file corresponding to the case, please? Thanks in advance, Ivo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18537) ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6
dogfood commented on JENKINS-18537 ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6 Integrated in jenkins_main_trunk #3989 [FIXED JENKINS-18537] (Revision 82d6292cf8d9c21cbf9346930cbc3e2a69548fe7) Result = SUCCESS jesse glick : 82d6292cf8d9c21cbf9346930cbc3e2a69548fe7 Files : core/pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-25937) "Given final block not properly padded" after deleting master.key after Java security update
dogfood commented on JENKINS-25937 "Given final block not properly padded" after deleting master.key after Java security update Integrated in jenkins_main_trunk #3989 [FIXED JENKINS-25937] Treat BadPaddingException as an unloadable key and continue. (Revision 16afb73b254504d0f0f1246e34cce1fb5bd65c35) Result = SUCCESS jesse glick : 16afb73b254504d0f0f1246e34cce1fb5bd65c35 Files : core/src/main/java/jenkins/security/DefaultConfidentialStore.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19081) Download update center from master by default
dogfood commented on JENKINS-19081 Download update center from master by default Integrated in jenkins_main_trunk #3989 [FIXED JENKINS-19081] Offer the option of downloading metadata directly from the server. (Revision 33d88c015c7fc6c6cdb093d4a3d04a75aa85fa80) Result = SUCCESS jesse glick : 33d88c015c7fc6c6cdb093d4a3d04a75aa85fa80 Files : core/src/main/resources/jenkins/security/DownloadSettings/help-checkSignature.html test/src/test/java/hudson/model/DownloadServiceTest.java core/src/main/java/hudson/model/DownloadService.java core/src/main/resources/hudson/model/UpdateCenter/PageDecoratorImpl/footer.jelly core/src/main/resources/jenkins/security/DownloadSettings/help-useBrowser.html core/src/main/resources/jenkins/security/DownloadSettings/config.groovy core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/model/UpdateSite.java core/src/main/java/jenkins/security/DownloadSettings.java core/src/main/resources/hudson/PluginManager/advanced.jelly core/src/main/resources/jenkins/security/Messages.properties core/src/main/java/hudson/model/UpdateCenter.java core/src/main/java/hudson/util/FormValidation.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21341) Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int)
dogfood commented on JENKINS-21341 Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int) Integrated in jenkins_main_trunk #3989 [FIXED JENKINS-21341] Merge pull request #1169 from pliljenberg/master (Revision 90e989827e9e7a826c12997d7f7109ac21b0411b) Result = SUCCESS jesse glick : 90e989827e9e7a826c12997d7f7109ac21b0411b Files : core/src/main/java/hudson/util/ProcessTree.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [mstest-plugin] (JENKINS-18632) Jenkins hangs during builds
Ivo Bellin Salarin resolved JENKINS-18632 as Cannot Reproduce Jenkins hangs during builds Change By: Ivo Bellin Salarin (28/Feb/15 10:01 PM) Status: Open Resolved 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] [mstest-plugin] (JENKINS-19360) Missing classname when used with reports generated from VSTest.Console.exe
Ivo Bellin Salarin resolved JENKINS-19360 as Fixed Missing classname when used with reports generated from VSTest.Console.exe Change By: Ivo Bellin Salarin (28/Feb/15 10:00 PM) Status: Open Resolved Assignee: acmarques Ivo Bellin Salarin 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] [mstest-plugin] (JENKINS-26262) Unable to execute the Unit Test cases using MSTest Plugin
Ivo Bellin Salarin resolved JENKINS-26262 as Not A Defect Unable to execute the Unit Test cases using MSTest Plugin This is not an issue, this is rather a question concerning the setup of the plugin. This plugin doesn't execute mstest/vstest test fixtures. This plugin analyzes the results collected by the mstestrunner-plugin or the vstestrunner-plugin. It's up to you to select your favourite runner. Please have a look at the documentation for those plugins. Change By: Ivo Bellin Salarin (28/Feb/15 9:51 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [mstest-plugin] (JENKINS-26262) Unable to execute the Unit Test cases using MSTest Plugin
Ivo Bellin Salarin assigned JENKINS-26262 to Ivo Bellin Salarin Unable to execute the Unit Test cases using MSTest Plugin Change By: Ivo Bellin Salarin (28/Feb/15 9:48 PM) Assignee: acmarques Ivo Bellin Salarin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-25937) "Given final block not properly padded" after deleting master.key after Java security update
SCM/JIRA link daemon commented on JENKINS-25937 "Given final block not properly padded" after deleting master.key after Java security update Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/jenkins/security/DefaultConfidentialStore.java http://jenkins-ci.org/commit/jenkins/16afb73b254504d0f0f1246e34cce1fb5bd65c35 Log: [FIXED JENKINS-25937] Treat BadPaddingException as an unloadable key and continue. (cherry picked from commit 6318b8d800abdf8b280f4e1b8ce8bf22e49242ad) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-19081) Download update center from master by default
SCM/JIRA link daemon commented on JENKINS-19081 Download update center from master by default Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/model/DownloadService.java core/src/main/java/hudson/model/UpdateCenter.java core/src/main/java/hudson/model/UpdateSite.java core/src/main/java/hudson/util/FormValidation.java core/src/main/java/jenkins/security/DownloadSettings.java core/src/main/resources/hudson/PluginManager/advanced.jelly core/src/main/resources/hudson/model/UpdateCenter/PageDecoratorImpl/footer.jelly core/src/main/resources/jenkins/security/DownloadSettings/config.groovy core/src/main/resources/jenkins/security/DownloadSettings/help-checkSignature.html core/src/main/resources/jenkins/security/DownloadSettings/help-useBrowser.html core/src/main/resources/jenkins/security/Messages.properties test/src/test/java/hudson/model/DownloadServiceTest.java http://jenkins-ci.org/commit/jenkins/33d88c015c7fc6c6cdb093d4a3d04a75aa85fa80 Log: [FIXED JENKINS-19081] Offer the option of downloading metadata directly from the server. (cherry picked from commit 1ac77750e93f9a1970fecbecdf7f84279d0a62b9) Conflicts: core/src/main/java/hudson/model/DownloadService.java core/src/main/java/hudson/model/UpdateSite.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-25937) "Given final block not properly padded" after deleting master.key after Java security update
SCM/JIRA link daemon commented on JENKINS-25937 "Given final block not properly padded" after deleting master.key after Java security update Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/jenkins/security/DefaultConfidentialStore.java http://jenkins-ci.org/commit/jenkins/16afb73b254504d0f0f1246e34cce1fb5bd65c35 Log: [FIXED JENKINS-25937] Treat BadPaddingException as an unloadable key and continue. (cherry picked from commit 6318b8d800abdf8b280f4e1b8ce8bf22e49242ad) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18537) ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6
SCM/JIRA link daemon commented on JENKINS-18537 ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6 Code changed in jenkins User: Kohsuke Kawaguchi Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/82d6292cf8d9c21cbf9346930cbc3e2a69548fe7 Log: [FIXED JENKINS-18537] Integrated the new version of XStream that contains the fix. (cherry picked from commit 585eb87c2d1fdd93c585efca2b993ad734afdb20) Conflicts: changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19081) Download update center from master by default
SCM/JIRA link daemon commented on JENKINS-19081 Download update center from master by default Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/model/DownloadService.java core/src/main/java/hudson/model/UpdateCenter.java core/src/main/java/hudson/model/UpdateSite.java core/src/main/java/hudson/util/FormValidation.java core/src/main/java/jenkins/security/DownloadSettings.java core/src/main/resources/hudson/PluginManager/advanced.jelly core/src/main/resources/hudson/model/UpdateCenter/PageDecoratorImpl/footer.jelly core/src/main/resources/jenkins/security/DownloadSettings/config.groovy core/src/main/resources/jenkins/security/DownloadSettings/help-checkSignature.html core/src/main/resources/jenkins/security/DownloadSettings/help-useBrowser.html core/src/main/resources/jenkins/security/Messages.properties test/src/test/java/hudson/model/DownloadServiceTest.java http://jenkins-ci.org/commit/jenkins/33d88c015c7fc6c6cdb093d4a3d04a75aa85fa80 Log: [FIXED JENKINS-19081] Offer the option of downloading metadata directly from the server. (cherry picked from commit 1ac77750e93f9a1970fecbecdf7f84279d0a62b9) Conflicts: core/src/main/java/hudson/model/DownloadService.java core/src/main/java/hudson/model/UpdateSite.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18537) ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6
SCM/JIRA link daemon commented on JENKINS-18537 ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6 Code changed in jenkins User: Kohsuke Kawaguchi Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/82d6292cf8d9c21cbf9346930cbc3e2a69548fe7 Log: [FIXED JENKINS-18537] Integrated the new version of XStream that contains the fix. (cherry picked from commit 585eb87c2d1fdd93c585efca2b993ad734afdb20) Conflicts: changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21341) Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int)
SCM/JIRA link daemon commented on JENKINS-21341 Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int) Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/util/ProcessTree.java http://jenkins-ci.org/commit/jenkins/90e989827e9e7a826c12997d7f7109ac21b0411b Log: [FIXED JENKINS-21341] Merge pull request #1169 from pliljenberg/master Ugly hack to fix destroyProcess for Java8 (cherry picked from commit 19640e7b4aa6d54865bc0816b604f4c0a9add6b6) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21341) Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int)
SCM/JIRA link daemon commented on JENKINS-21341 Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int) Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/util/ProcessTree.java http://jenkins-ci.org/commit/jenkins/90e989827e9e7a826c12997d7f7109ac21b0411b Log: [FIXED JENKINS-21341] Merge pull request #1169 from pliljenberg/master Ugly hack to fix destroyProcess for Java8 (cherry picked from commit 19640e7b4aa6d54865bc0816b604f4c0a9add6b6) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [multijob-plugin] (JENKINS-27173) MultiJobBuilder waits for all subjobs of the same project instead of direct subjob instance
Danny Campbell created JENKINS-27173 MultiJobBuilder waits for all subjobs of the same project instead of direct subjob instance Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 28/Feb/15 8:32 PM Description: I have a parent MultiJob that executes a number of child MultiJobs in order to modularize the tasks that I am running. The said child MultiJob build is often built by itself (without the parent MultiJob). When the child is built by itself and a separate parent MultiJob is built afterwards (and in turn the parent MultiJob builds a new instance of the child job), the parent MultiJob's child will wait until the extant stand-alone built Multijob child is done. Basically a given MultiJob will wait for all jobs in the queue that are of the same project of the given MultiJob's subjob instead of the intended purpose of waiting for an executor to free up ONLY for the given MultiJob's subjob. Is there anything I can do in the time being to avoid this? Here is where this wait happens: https://github.com/jenkinsci/tikal-multijob-plugin/blob/master/src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobBuilder.java#L187-L189 Probably not super important, but here is my stacktrace when i saw the parent MultiJob blocked (note multijob 1.16 source lines different): at java.lang.Thread.sleep(Native Method) at java.lang.Thread.sleep(Thread.java:321) at java.util.concurrent.TimeUnit.sleep(TimeUnit.java:356) at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:191) 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 com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134) at hudson.model.Run.execute(Run.java:1759) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Environment: Jenkins 1.592 Multijob 1.16 Project: Jenkins Priority: Major Reporter: Danny Campbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24494) FingerprinterAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Astro Ashtar closed JENKINS-24494 as Cannot Reproduce FingerprinterAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions I do not see this issue anymore. I'm assuming it's been resolved Change By: Astro Ashtar (28/Feb/15 8:26 PM) 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] [core] (JENKINS-24494) FingerprinterAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Astro Ashtar resolved JENKINS-24494 as Cannot Reproduce FingerprinterAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions No longer reproducible. Change By: Astro Ashtar (28/Feb/15 8:26 PM) Status: Open Resolved 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] [core] (JENKINS-27172) After job completion, spinning loading icon
Astro Ashtar created JENKINS-27172 After job completion, spinning loading icon Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Feb/15 8:24 PM Description: After the job is finished, and the Jenkins job states "Finished", but then just hangs there. Job never finishes. is there a way to debug this? i turned on logging for hudson.model.run. anything else i can do? C:\jenkins\workspace\Run-a-Windows-Job\bin>exit 0 Build step 'Console output (build log) parsing' changed build result to FAILURE Finished: FAILURE Project: Jenkins Priority: Critical Reporter: Astro Ashtar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [git-plugin] (JENKINS-27166) CLONE - Git SCM-polling doesn't work when using a parametrized branch-name
Mark Waite assigned JENKINS-27166 to Unassigned CLONE - Git SCM-polling doesn't work when using a parametrized branch-name Change By: Mark Waite (28/Feb/15 8:04 PM) Assignee: Mark Waite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [matrix-project-plugin] (JENKINS-25783) very long build directory paths are created by Matrix project, and difficult directcory names
Pascal Bach commented on JENKINS-25783 very long build directory paths are created by Matrix project, and difficult directcory names You are right if the path was quoted correctly everywhere there would be no issue. However if you build a whole linux distribution with hundreds of third party packages it is very likely that some components get it wrong. To fix this is a huge effort and not possible to fix in the short term. So I also would appreciate an option that would allow to get more "standard" paths. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27057) CME in WorkflowRun.logsToCopy
Jesse Glick updated JENKINS-27057 CME in WorkflowRun.logsToCopy Change By: Jesse Glick (28/Feb/15 4:50 PM) Labels: testing threads xstream This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-26740) Failed to set Jenkins Identity header on email. java.lang.NullPointerException
Guy Rozendorn commented on JENKINS-26740 Failed to set Jenkins Identity header on email. java.lang.NullPointerException Also exists in the Mailer plug-in v1.15 on Jenkins 1.598 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Samuel Sapalski edited a comment on JENKINS-20941 Stored git credentials not used when submodule is updated I'm facing the same problem with "Amazon Linux AMI" slaves which are provisioned via the "Amazon EC2" plugin. An official fix is very much appreciated, I'm looking forward to it ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-25783) very long build directory paths are created by Matrix project, and difficult directcory names
Daniel Beck commented on JENKINS-25783 very long build directory paths are created by Matrix project, and difficult directcory names Jordan Spiker: Wouldn't it suffice to just consistently double-quote references to the folder? What specifically breaks? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [change-assembly-version-plugin] (JENKINS-26763) Assembly Version field value is not loaded when editing job
leonardo kobus resolved JENKINS-26763 as Fixed Assembly Version field value is not loaded when editing job The fix comes in the new version. Change By: leonardo kobus (28/Feb/15 3:25 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] [change-assembly-version-plugin] (JENKINS-26763) Assembly Version field value is not loaded when editing job
leonardo kobus commented on JENKINS-26763 Assembly Version field value is not loaded when editing job The problem was a field that has been refactored but only the getter method, so when jelly try to find the field, he get a empty field (this make the sensation of not saving) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27084) SVN authentication fails using subversion plugin v.2.5
Jordan Spiker commented on JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 I'm seeing the same issue in a Linux environment, but our svn server uses NTLM. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [matrix-project-plugin] (JENKINS-25783) very long build directory paths are created by Matrix project, and difficult directcory names
Jordan Spiker commented on JENKINS-25783 very long build directory paths are created by Matrix project, and difficult directcory names Label _expression_ axis can also create bad paths. If I have "label1&&label2" _expression_, the path then include /job/label1&&label2/... This makes for some nasty workarounds in shell scripts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cloudformation-plugin] (JENKINS-26304) Output variables missing while using AWS CloudFormation as build-step
Mike Chambers
edited a comment on JENKINS-26304
Output variables missing while using AWS CloudFormation as build-step
Hi Amit
To recreate this issue:
Use a CF template with Outputs specified, e.g.:
"Outputs": {
"VPCId": {
"Description": "Virtual Private Cloud identifiers",
"Value": {
"Ref": "VPCdev"
}
}
}
Create a Jenkins job
Within: 'Build Environment' > 'Create AWS Cloud Formation stack' - Add CF json with all mandatory feilds completed.
Within: 'Build' > 'Execute Shell' - add 'env'
After running this build the VPCid CF Output is shown (amoungst other things) in the 'Console Output' of the env command.
Now edit the job configuration...
Delete the 'Build Environment' CF entry
Add a 'Build' > 'AWS Cloud Formation' with the same details as before.
Ensure the 'Execute Shell' - 'env' is still after the CF build block.
Now, after running, the VPCid CF Output is NOT shown in the 'Console Output' of the env command.
The use case where this matters is where scripts need to be run before building a number of CF stacks, for example the script may create the CF json template in a step prior to each stack build, and use outputs from the previous stack to generate the next CF template.
Jenkins 1.535 + 1.599
jenkins-cloudformation-plugin 0.14
Jenkins, TurnKey Linux 13.0 / Debian 7.2 Wheezy (AWS AMI from Marketplace)
Tests run as 'admin' user.
More than happy to do anything I can to help resolve this issue. However my Java leaves a lot to be desired.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [cloudformation-plugin] (JENKINS-26304) Output variables missing while using AWS CloudFormation as build-step
Mike Chambers
edited a comment on JENKINS-26304
Output variables missing while using AWS CloudFormation as build-step
Hi Amit
To recreate this issue:
Use a CF template with Outputs specified, e.g.:
"Outputs": {
"VPCId": {
"Description": "Virtual Private Cloud identifiers",
"Value": {
"Ref": "VPCdev"
}
}
}
Create a Jenkins job
Within: 'Build Environment' > 'Create AWS Cloud Formation stack' - Add CF json with all mandatory feilds completed.
Within: 'Build' > 'Execute Shell' - add 'env'
After running this build the VPCid CF Output is shown (amoungst other things) in the 'Console Output' of the env command.
Now edit the job configuration...
Delete the 'Build Environment' CF entry
Add a 'Build' > 'AWS Cloud Formation' with the same details as before.
Ensure the 'Execute Shell' - 'env' is still after the CF build block.
Now, after running, the VPCid CF Output is NOT shown in the 'Console Output' of the env command.
The use case where this matters is where scripts need to be run before building a number of CF stacks, for example the script may create the CF json template in a step prior to each stack build, and use outputs from the previous stack to generate the next CF template.
Jenkins 1.535
jenkins-cloudformation-plugin 0.14
Jenkins, TurnKey Linux 13.0 / Debian 7.2 Wheezy (AWS AMI from Marketplace)
Tests run as 'admin' user.
More than happy to do anything I can to help resolve this issue. However my Java leaves a lot to be desired.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [cloudformation-plugin] (JENKINS-26304) Output variables missing while using AWS CloudFormation as build-step
Mike Chambers
commented on JENKINS-26304
Output variables missing while using AWS CloudFormation as build-step
Hi Amit
To recreate this issue:
Use a CF template with Outputs specified, e.g.:
"Outputs": {
"VPCId": Unknown macro: {"Description"}
}
Create a Jenkins job
Within: 'Build Environment' > 'Create AWS Cloud Formation stack' - Add CF json with all mandatory feilds completed.
Within: 'Build' > 'Execute Shell' - add 'env'
After running this build the VPCid CF Output is shown (amoungst other things) in the 'Console Output' of the env command.
Now edit the job configuration...
Delete the 'Build Environment' CF entry
Add a 'Build' > 'AWS Cloud Formation' with the same details as before.
Ensure the 'Execute Shell' - 'env' is still after the CF build block.
Now, after running, the VPCid CF Output is NOT shown in the 'Console Output' of the env command.
The use case where this matters is where scripts need to be run before building a number of CF stacks, for example the script may create the CF json template in a step prior to each stack build, and use outputs from the previous stack to generate the next CF template.
Jenkins 1.535
jenkins-cloudformation-plugin 0.14
Jenkins, TurnKey Linux 13.0 / Debian 7.2 Wheezy (AWS AMI from Marketplace)
Tests run as 'admin' user.
More than happy to do anything I can to help resolve this issue. However my Java leaves a lot to be desired.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [conditional-buildstep-plugin] (JENKINS-19802) Conditional Build Step for "Current build status" never triggers - or doesn't seem to
Michael Weinrich commented on JENKINS-19802 Conditional Build Step for "Current build status" never triggers - or doesn't seem to Sorry, you are right. Thanks for looking into this again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-27171) Conditions are evaluated for each actions
Kanstantsin Shautsou commented on JENKINS-27171 Conditions are evaluated for each actions Also if you want exclude evaluation, then add "flexible publish" in actions and set "execute always" with group of Actions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [flexible-publish-plugin] (JENKINS-27171) Conditions are evaluated for each actions
Kanstantsin Shautsou commented on JENKINS-27171 Conditions are evaluated for each actions This is designed functionality. Current design that it allows to not configure the same statement for every publisher and evaluation must be evaluated every time to ensure that action need to be executed, i.e. "build status" that can be failed by one of previous actions. If it not obvious, than add help page. Don't treat things that you doesn't understand as a bugs. Case "evaluate once" makes sense, but will be enhancement. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [gradle-jpi-plugin] (JENKINS-17130) Plugin messes up repository URLs
Daniel Spilker closed JENKINS-17130 as Fixed Plugin messes up repository URLs Change By: Daniel Spilker (28/Feb/15 1:05 PM) 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] [gradle-jpi-plugin] (JENKINS-17129) Gradle plugin does not support HudsonTestCase
Daniel Spilker closed JENKINS-17129 as Fixed Gradle plugin does not support HudsonTestCase Change By: Daniel Spilker (28/Feb/15 1:05 PM) 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] [core] (JENKINS-18643) Make tests run on Windows
ikedam commented on JENKINS-18643 Make tests run on Windows All problems I listed in the description are resolved. Thanks a lot! I tried run all tests on Windows with the latest master (dac7dfe), and saw following new problems: hudson.PluginManagerTest#prevalidateConfig Tries to access a local file with a query string (trailing ?param=value). This is the same problem to 5cfc002 and can be fixed in the same way. hudson.tasks.MavenTest#sensitiveParameters The build log contains the content of the password parameter. The build log was: Legacy code started this job. No cause information is available Building in workspace C:\Users\ikedam\Desktop\workspace\jenkins\test\target\hudson5918984730964172897test\workspace\test0 Deleting existing workspace C:\Users\ikedam\Desktop\workspace\jenkins\test\target\hudson5918984730964172897test\workspace\test0 Staging file:/C:/Users/ikedam/Desktop/workspace/jenkins/test/target/test-classes/hudson/tasks/maven-empty.zip [test0] $ cmd.exe /C '"mvn.bat -Dstring2=Value2 -Dstring=defaultValue -Dpassword=12345 clean package && exit %%ERRORLEVEL%%"' I'm not sure what's the expected result. hudson.bugs.JnlpAccessWithSecuredHudsonTest#testServiceUsingDirectSecret Hangs up. It can stack for 1 minutes for its implementation, but apparently it stacked over 10 minutes... Let me have more time to see details of those failures. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [conditional-buildstep-plugin] (JENKINS-15833) exception with latest Conditional buildstep plugin, with jenkins version 1.490
Dominik Bartholdi resolved JENKINS-15833 as Duplicate exception with latest Conditional buildstep plugin, with jenkins version 1.490 Change By: Dominik Bartholdi (28/Feb/15 12:26 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] [conditional-buildstep-plugin] (JENKINS-25918) Conditional Build Step - Add support for else clause
Dominik Bartholdi resolved JENKINS-25918 as Duplicate Conditional Build Step - Add support for else clause Change By: Dominik Bartholdi (28/Feb/15 12:23 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] [conditional-buildstep-plugin] (JENKINS-21636) When using Contional steps(multiple) plugin config the Fitnesse configuration values are getting null
Dominik Bartholdi assigned JENKINS-21636 to Antoine Aumjaud When using Contional steps(multiple) plugin config the Fitnesse configuration values are getting null Change By: Dominik Bartholdi (28/Feb/15 12:21 PM) Assignee: Dominik Bartholdi Antoine Aumjaud This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [conditional-buildstep-plugin] (JENKINS-21636) When using Contional steps(multiple) plugin config the Fitnesse configuration values are getting null
Dominik Bartholdi commented on JENKINS-21636 When using Contional steps(multiple) plugin config the Fitnesse configuration values are getting null Unfortunate this issue is cased by the fitness-plugin not using the DataBoundConstructor as intended. Even though the plugin defines a constructor [1] with '@DataBoundConstructor', its usage is wrong. Insted it expects the instance to be created by 'descriptor.newInstance()' [2] with some JSON parsing. There are two ways to solve this issue: 1. remove the '@DataBoundConstructor' annotation at all, this will make the conditional-buildstep plugin ignore this plugin and there fore users will not be confused anymore. or 2. implement the constructor the correct way as intended by newer plugins btw. the groovy plugin used to have the same issue [3] [1] https://github.com/jenkinsci/fitnesse-plugin/blob/master/src/main/java/hudson/plugins/fitnesse/FitnesseBuilder.java#L61-L65 [2] https://github.com/jenkinsci/fitnesse-plugin/blob/master/src/main/java/hudson/plugins/fitnesse/FitnesseBuilder.java#L410-L429 [3] https://issues.jenkins-ci.org/browse/JENKINS-6797 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [conditional-buildstep-plugin] (JENKINS-22501) advanced options (e.g., "fail the build") are not saved or executed
Dominik Bartholdi resolved JENKINS-22501 as Not A Defect advanced options (e.g., "fail the build") are not saved or executed Change By: Dominik Bartholdi (28/Feb/15 12:00 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [conditional-buildstep-plugin] (JENKINS-22501) advanced options (e.g., "fail the build") are not saved or executed
Dominik Bartholdi commented on JENKINS-22501 advanced options (e.g., "fail the build") are not saved or executed I think this is a missunderstanding of the purpose of the conditional buildstep plugin. This plugin allows you to execute aribtrary build steps if a given condition is met. As such the "fail the build" option has a small label called "On evaluation failure", this means: fail the build if the condition it self has a problem. This get more obvious if you use a condition like the "regular _expression_" condition, if the configured regex has a wrong syntax, then the build will fail. So this checkbox is more to help the user to identify configuration errors then anything else. For your case, you don't need the conditional buildstep plugin at all. Just use "Shell" step and do a "ls myfile.txt" - if the file exists, this will return '0' and Jenkins will continue the build, if the file is missing then jenkins will mark the build as faild. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [conditional-buildstep-plugin] (JENKINS-23719) Adding a system groovy conditional build step causes "angry jenkins" stacktrace
Dominik Bartholdi resolved JENKINS-23719 as Fixed Adding a system groovy conditional build step causes "angry jenkins" stacktrace this was fixed with JENKINS-6797, please upgrade your groovy plugin Change By: Dominik Bartholdi (28/Feb/15 11:45 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep-plugin] (JENKINS-19802) Conditional Build Step for "Current build status" never triggers - or doesn't seem to
Dominik Bartholdi edited a comment on JENKINS-19802 Conditional Build Step for "Current build status" never triggers - or doesn't seem to because the conditions are part of a different plugin https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin and not as such under controll of the conditional buildstep plugin ...I see if I can make it configurable This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [conditional-buildstep-plugin] (JENKINS-19802) Conditional Build Step for "Current build status" never triggers - or doesn't seem to
Dominik Bartholdi commented on JENKINS-19802 Conditional Build Step for "Current build status" never triggers - or doesn't seem to because the conditions are part of a different plugin https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin and not as such under controll of the conditional buildstep 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] [conditional-buildstep-plugin] (JENKINS-19802) Conditional Build Step for "Current build status" never triggers - or doesn't seem to
Michael Weinrich commented on JENKINS-19802 Conditional Build Step for "Current build status" never triggers - or doesn't seem to I'm ok with it being the wrong approach, but why not remove that option altogether to avoid question/bug reports like these? Wouldn't that make more sense instead of just closing it as "Won't 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Samuel Sapalski commented on JENKINS-20941 Stored git credentials not used when submodule is updated I'm facing the same problem with "Amazon Linux AMI" slaves which are provisioned via the "Amazon EC2" plugin. An official fix is very much appreciated, I'm looking forward it ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep-plugin] (JENKINS-21795) Easily wrap existing build steps with a condition
Dominik Bartholdi resolved JENKINS-21795 as Not A Defect Easily wrap existing build steps with a condition actually, this is already awailable, please have a look at https://wiki.jenkins-ci.org/pages/viewpage.action?pageId=59507542 Change By: Dominik Bartholdi (28/Feb/15 10:47 AM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [conditional-buildstep-plugin] (JENKINS-22471) Do not save Gradle version on single build step
Dominik Bartholdi resolved JENKINS-22471 as Incomplete Do not save Gradle version on single build step Change By: Dominik Bartholdi (28/Feb/15 10:42 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep-plugin] (JENKINS-25763) Conditional steps plugin with wrong syntax parameters
Dominik Bartholdi commented on JENKINS-25763 Conditional steps plugin with wrong syntax parameters If the value starts with '$', then maybe we could use a regex to verify the Token Expansion Model as described here: https://wiki.jenkins-ci.org/display/JENKINS/Token+Macro+Plugin ...any regex guru around? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [conditional-buildstep-plugin] (JENKINS-27149) Conditional step (single) not processing for Failed build
Dominik Bartholdi resolved JENKINS-27149 as Won't Fix Conditional step (single) not processing for Failed build I'm sorry to say, but this a duplicated of JENKINS-19802 and a conceptional problem within the core of jenkins, therefore can't be fixed Change By: Dominik Bartholdi (28/Feb/15 10:30 AM) Status: Open Resolved Resolution: Won't 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] [conditional-buildstep-plugin] (JENKINS-19802) Conditional Build Step for "Current build status" never triggers - or doesn't seem to
Dominik Bartholdi commented on JENKINS-19802 Conditional Build Step for "Current build status" never triggers - or doesn't seem to Lance Smith as mention above, this can not be fixed in this plugin and its also very unlikely to be fixed anywhere else in the core. From a conceptional point of view the current behaviour is correct and you should not be using the build status. I would suggest you take a look at the workflow plugin, then you might be able to work around the issue by using more advanced configurations with "try/catch/finally" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [conditional-buildstep-plugin] (JENKINS-19802) Conditional Build Step for "Current build status" never triggers - or doesn't seem to
Dominik Bartholdi resolved JENKINS-19802 as Won't Fix Conditional Build Step for "Current build status" never triggers - or doesn't seem to Change By: Dominik Bartholdi (28/Feb/15 10:09 AM) Status: Open Resolved Resolution: Won't 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] [repository-connector-plugin] (JENKINS-24896) Repoistory Connector plugin fails to resolve LATEST version
Dominik Bartholdi resolved JENKINS-24896 as Not A Defect Repoistory Connector plugin fails to resolve LATEST version Change By: Dominik Bartholdi (28/Feb/15 9:56 AM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-24896) Repoistory Connector plugin fails to resolve LATEST version
Dominik Bartholdi commented on JENKINS-24896 Repoistory Connector plugin fails to resolve LATEST version In general this should work, I have tested it with 'http://repo1.maven.org/maven2' to resolve 'commons-logging:commons-logging:jar:LATEST' and 'commons-logging:commons-logging:jar:RELEASE' But looking at your stacktrace, it looks more that you have not configured the correct repository in the global Jenkins configuration. Please see the screenshot here: https://wiki.jenkins-ci.org/display/JENKINS/Repository+Connector+Plugin If this is not the case, please feel free to reopen this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-24243) Add ability to disable using the global configured proxy
Dominik Bartholdi commented on JENKINS-24243 Add ability to disable using the global configured proxy resolved with 1.1.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-25395) org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml
Dominik Bartholdi commented on JENKINS-25395 org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml This might be related to JENKINS-24243 - please have try with the new version 1.1.1 and let me know if it worked This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-24243) Add ability to disable using the global configured proxy
SCM/JIRA link daemon resolved JENKINS-24243 as Fixed Add ability to disable using the global configured proxy Change By: SCM/JIRA link daemon (28/Feb/15 9:22 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-24243) Add ability to disable using the global configured proxy
SCM/JIRA link daemon commented on JENKINS-24243 Add ability to disable using the global configured proxy Code changed in jenkins User: Robert Kleinschmager Path: .gitignore src/main/java/org/jvnet/hudson/plugins/repositoryconnector/aether/Aether.java src/test/java/org/jvnet/hudson/plugins/repositoryconnector/aether/AetherTest.java http://jenkins-ci.org/commit/repository-connector-plugin/fe32bb0e1adae152d150f5adb8073329cf85c4e8 Log: [FIXED JENKINS-24243] respecting nonProxySettings moved proxy configuration to MavenRepositorySystemSession creation added intellijfile to gitignore This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
