[JIRA] (JENKINS-36229) API for UI to honour permissions
Title: Message Title Vivek Pandey commented on JENKINS-36229 Re: API for UI to honour permissions James Dumay I am going to make first cut of jenkins config object in this ticket. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36229) API for UI to honour permissions
Title: Message Title James Dumay commented on JENKINS-36229 Re: API for UI to honour permissions That is, Making it extensible Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36229) API for UI to honour permissions
Title: Message Title James Dumay commented on JENKINS-36229 Re: API for UI to honour permissions Brilliant idea Vivek - now we have a good home for the config of other things too! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37327) Allow stashing/unstashing empty sets
Title: Message Title Daniel Sobral created an issue Jenkins / JENKINS-37327 Allow stashing/unstashing empty sets Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Aug/11 5:10 AM Priority: Minor Reporter: Daniel Sobral The stash step fails if there's no files are selected to be stashed. Allowing that to optionally work would make it easier to make Jenkinsfile more generic, by stashing files that might not get generated on some repositories, instead of passing information around with fields, or catching failure when unstashing (which still leaves the corresponding log marked as Failure in the build). Add Comment
[JIRA] (JENKINS-37293) ECS Agents are not deleted because Jenkins is unable to delete logs due to NFS locks
Title: Message Title Evan Borgstrom commented on JENKINS-37293 Re: ECS Agents are not deleted because Jenkins is unable to delete logs due to NFS locks FWIW, I remounted our EFS files system with the noatime,nodiratime options today and it seems to be a solid workaround for the issue, slaves are being cleaned up as expected. While I intend to leave those mount options on, this should still be fixed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37196) DSL for Violation Comments to GitHub Plugin
Title: Message Title Tomas Bjerre commented on JENKINS-37196 Re: DSL for Violation Comments to GitHub Plugin The wiki is a bit slow. But 1.14 is in the update site: http://mirror.xmission.com/jenkins/updates/current/update-center.json Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36229) API for UI to honour permissions
Title: Message Title Vivek Pandey commented on JENKINS-36229 Re: API for UI to honour permissions James Dumay Good idea, we can do that using BluePageDecorator, it will inject config objet on window element. I think we are doing things like this from some of the plugins anyways. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37179) Unable to scroll down/up jobs in view, in case if job doesn't fit to area
Title: Message Title Andrey Shevtsov resolved as Fixed Scrolling does not fit the dashboard concept. Job filtering feature was added in v0.9.1, this will allow to split/group one dashboard into a couple or a few dashboards with smaller number of jobs displayed. Jenkins / JENKINS-37179 Unable to scroll down/up jobs in view, in case if job doesn't fit to area Change By: Andrey Shevtsov Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-34373) Ability to filter jobs in mission control
Title: Message Title Andrey Shevtsov resolved as Fixed Released new version - 0.9.1 that has an option to enable job filtering (regular _expression_). Jenkins / JENKINS-34373 Ability to filter jobs in mission control Change By: Andrey Shevtsov Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-37196) DSL for Violation Comments to GitHub Plugin
Title: Message Title Giriraj Gujar commented on JENKINS-37196 Re: DSL for Violation Comments to GitHub Plugin Hi Tomas, Thank you so much. However I don't see it here: https://wiki.jenkins-ci.org/display/JENKINS/Violation+Comments+to+GitHub+Plugin It is still showing "Latest Release" as 1.12 only? Does it usually takes time to update on wiki? Thanks, Giriraj Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37326) build in java spawn powsershell(x86) in 64bit OS
Title: Message Title Bill Wang created an issue Jenkins / JENKINS-37326 build in java spawn powsershell(x86) in 64bit OS Issue Type: Bug Assignee: Unassigned Components: powershell-plugin Created: 2016/Aug/11 3:20 AM Environment: windows installer running on Win 10 Priority: Minor Reporter: Bill Wang the plugin invoking x86 version of powershell. ref: http://stackoverflow.com/questions/27270450/jenkins-powershell-plugin-class-not-registered-error-in-windows-server-2008 Add Comment
[JIRA] (JENKINS-36894) Refactor shortcuts of matrix-combination plugin
Title: Message Title ikedam updated JENKINS-36894 Jenkins / JENKINS-36894 Refactor shortcuts of matrix-combination plugin Change By: ikedam Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36229) API for UI to honour permissions
Title: Message Title James Dumay commented on JENKINS-36229 Re: API for UI to honour permissions Vivek Pandey what about a app config JSON object that gets embedded on window.blueoceanConfig when the index.jelly gets rendered? No round trip required. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37325) Make static analysis results visible from a Pipeline
Title: Message Title Daniel Sobral created an issue Jenkins / JENKINS-37325 Make static analysis results visible from a Pipeline Issue Type: Improvement Assignee: Ulli Hafner Components: analysis-core-plugin Created: 2016/Aug/11 1:41 AM Priority: Minor Reporter: Daniel Sobral I'd like to be able to tell if the static analysis publisher I executed failed the build. That is easy on serial pipelines by checking the currentBuild.result, but when executing tasks in parallel, I cannot rely on that. It would be even better if the actual data was made available, in which case I could drop the thresholds and use more complex logic. Add Comment
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title James Dumay created an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step via flow nodes Issue Type: Task Assignee: Jesse Glick Attachments: unnamed-2.png Components: workflow-plugin Created: 2016/Aug/11 12:28 AM Labels: blueocean x-team Priority: Minor Reporter: James Dumay We want to provide the developer a more meaningful description of the steps in Blue Ocean. For example, if we have a shell script being executed we'd like to provide the command as the description of that step. If we don't have that information, we'd like to fall back to a description of the step otherwise fall back to the step name. Add Comment
[JIRA] (JENKINS-37300) Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
Title: Message Title
Jesse Luehrs commented on JENKINS-37300
Re: Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
I'm also running into this issue, with Jenkins version 1.651.3, jenkins-multijob-plugin version 1.22, and ez-templates version 1.2.0. The multijob plugin initially failed to load after upgrading, since it was throwing errors about the ez-templates plugin not being installed. After installing the ez-templates plugin, most things seem to work except that visiting a job page for a multijob project shows this stack trace
Caused by: java.lang.NoClassDefFoundError: com/joelj/jenkins/eztemplates/InheritenceStep/EzTemplateBuilder at com.tikal.jenkins.plugins.multijob.views.MultiJobView.addMultiProject(MultiJobView.java:127) at com.tikal.jenkins.plugins.multijob.views.MultiJobView.addTopLevelProject(MultiJobView.java:112) at com.tikal.jenkins.plugins.multijob.views.MultiJobView.getRootItem(MultiJobView.java:106) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) ... 83 more {/code} There are no errors in the Jenkins log file.
Add Comment
[JIRA] (JENKINS-37300) Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
Title: Message Title
Jesse Luehrs edited a comment on JENKINS-37300
Re: Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
I'm also running into this issue, with Jenkins version 1.651.3, jenkins-multijob-plugin version 1.22, and ez-templates version 1.2.0. The multijob plugin initially failed to load after upgrading, since it was throwing errors about the ez-templates plugin not being installed. After installing the ez-templates plugin, most things seem to work except that visiting a job page for a multijob project shows this stack trace{code}Caused by: java.lang.NoClassDefFoundError: com/joelj/jenkins/eztemplates/InheritenceStep/EzTemplateBuilder at com.tikal.jenkins.plugins.multijob.views.MultiJobView.addMultiProject(MultiJobView.java:127) at com.tikal.jenkins.plugins.multijob.views.MultiJobView.addTopLevelProject(MultiJobView.java:112) at com.tikal.jenkins.plugins.multijob.views.MultiJobView.getRootItem(MultiJobView.java:106) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) ... 83 more{ / code}There are no errors in the Jenkins log file.
Add Comment
[JIRA] (JENKINS-37116) Add support for Jenkins Pipeline to the shiningpanda-plugin
Title: Message Title
matthew snyder commented on JENKINS-37116
Re: Add support for Jenkins Pipeline to the shiningpanda-plugin
+1 for getting this working. In the mean time, using the workflowlibs plugin https://github.com/jenkinsci/workflow-cps-global-lib-plugin I have working virtual environments. I'm using vex here to run commands https://pypi.python.org/pypi/vex , as activating the virtualenv doesn't stay active across sh invocations in pipeline scripts. It's a bit hackish, I just got it going, but maybe this will be useful for someone else.
% cat workflowLibs/src/com/testing/jenkins/python_utils.groovy
package com.testing.jenkins;
def create_virtualenv(){
withEnv(["PATH+VEX=~/.local/bin"]){
sh 'pwd > pwd.current'
env.WORKSPACE = readFile('pwd.current').trim()
sh "virtualenv ${env.WORKSPACE}/.virtualenv"
}
}
def create_virtualenv_py3(){
withEnv(["PATH+VEX=~/.local/bin"]){
sh 'pwd > pwd.current'
env.WORKSPACE = readFile('pwd.current').trim()
sh "virtualenv --python=python3 ${env.WORKSPACE}/.virtualenv"
}
}
def run_cmd(pycmd){
withEnv(["PATH+VEX=~/.local/bin"]){
sh "vex --path=${env.WORKSPACE}/.virtualenv ${pycmd}"
}
}
In the pipeline script: def vex = new com.testing.jenkins.python_utils() vex.create_virtualenv_py3() vex.run_cmd("python --version") vex.run_cmd("pip install -r requirements.txt") vex.run_cmd("some_script.py")
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37323 Ensure that Pipeline Graph can handle stage blocks Change By: James Dumay Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37323 Ensure that Pipeline Graph can handle stage blocks Change By: James Dumay Sprint: 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37323 Ensure that Pipeline Graph can handle stage blocks Change By: James Dumay Vivek to add notes after meeting with Sam Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title James Dumay created an issue Jenkins / JENKINS-37323 Ensure that Pipeline Graph can handle stage blocks Issue Type: Task Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Aug/10 11:48 PM Priority: Minor Reporter: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-36249) Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen
Title: Message Title C T commented on JENKINS-36249 Re: Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen My workflow-scm-step version is 2.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37322) Pipeline documentation missing archiveArtifact documetnation
Title: Message Title Cole Mickens created an issue Jenkins / JENKINS-37322 Pipeline documentation missing archiveArtifact documetnation Issue Type: Bug Assignee: Oleg Nenashev Components: pipeline-_unsorted Created: 2016/Aug/10 11:37 PM Priority: Minor Reporter: Cole Mickens When you go to http://jenkins_install/job/some_pipeline_job/pipeline-syntax/html you get a page documenting the DSL in Jenkinsfile. 'archive' is listed as a deprecated step. Users are told to use 'archiveArtifacts' instead, but it's not actually documented anywhere on the page. Sorry if the component is wrong, it was hard to choose. Add Comment
[JIRA] (JENKINS-37321) classes api doesn't work with recent impl split
Title: Message Title Ivan Meredith created an issue Jenkins / JENKINS-37321 classes api doesn't work with recent impl split Issue Type: Bug Assignee: Ivan Meredith Components: blueocean-plugin Created: 2016/Aug/10 11:25 PM Priority: Blocker Reporter: Ivan Meredith Needs to be Jenkins.getInstance().getPluginManager().uberClassLoader.loadClass(name); Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35874) Stage duration trends
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35874 Stage duration trends Change By: James Dumay *In Scope** Identify slowdowns in a particular stage* Identify the average runtime of a stage* Identify the average runtime of the pipeline*Example* !stage-duration.png |thumbnail ! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35874) Stage duration trends
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35874 Stage duration trends Change By: James Dumay As discussed on https://issues.jenkins *In Scope** Identify slowdowns in a particular stage* Identify the average runtime of a stage* Identify the average runtime of the pipeline*Example* !stage - ci duration . org/browse/JENKINS-33185?focusedCommentId=249220=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-249220 png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35874) Stage duration trends
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35874 Stage duration trends Change By: James Dumay Attachment: stage-duration.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36249) Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen
Title: Message Title C T commented on JENKINS-36249 Re: Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen I also get this message: "SEVERE: found cycle in plugin dependencies: (root=Plugin:git, deactivating all involved) Plugin:git -> Plugin:workflow-scm-step -> Plugin:git" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36249) Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen
Title: Message Title C T commented on JENKINS-36249 Re: Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen I get the following exceptions: INFO: Injecting JRuby into XStream Trying to load models from /var/lib/jenkins/plugins/rvm/WEB-INF/classes/models Loading /var/lib/jenkins/plugins/rvm/WEB-INF/classes/models/rvm_wrapper.rb Aug 10, 2016 10:40:26 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading plugin managed-scripts java.io.IOException: Dependency config-file-provider (2.0) doesn't exist at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:523) at hudson.PluginManager$2$1$1.run(PluginManager.java:409) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:1009) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Aug 10, 2016 10:40:26 PM hudson.plugins.virtualbox.VirtualBoxPlugin start INFO: Starting VirtualBoxPlugin Aug 10, 2016 10:40:26 PM jenkins.bouncycastle.api.SecurityProviderInitializer addSecurityProvider INFO: Initializing Bouncy Castle security provider. Aug 10, 2016 10:40:26 PM jenkins.bouncycastle.api.SecurityProviderInitializer addSecurityProvider INFO: Bouncy Castle security provider initialized. Aug 10, 2016 10:40:26 PM org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$DescriptorImpl INFO: Using new style Permission with PermissionScope Trying to load models from /var/lib/jenkins/plugins/chef/WEB-INF/classes/models Loading /var/lib/jenkins/plugins/chef/WEB-INF/classes/models/chef-builder.rb Aug 10, 2016 10:40:33 PM hudson.ExtensionFinder$GuiceFinder$SezpozModule configure WARNING: Failed to load net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition$DescriptorImpl java.lang.NoClassDefFoundError: hudson/plugins/git/GitSCM at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.privateGetPublicMethods(Class.java:2902) at java.lang.Class.getMethods(Class.java:1615) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:480) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:509) at com.google.inject.AbstractModule.configure(AbstractModule.java:62) at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:230) at com.google.inject.spi.Elements.getElements(Elements.java:103) at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:136) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) at com.google.inject.Guice.createInjector(Guice.java:96) at com.google.inject.Guice.createInjector(Guice.java:73) at hudson.ExtensionFinder$GuiceFinder.(ExtensionFinder.java:280) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at
[JIRA] (JENKINS-36249) Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen
Title: Message Title C T commented on JENKINS-36249 Re: Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen Thomas Sauter, I am having the same problem. What steps did you follow to "manually" update the workflow-scm-step plugin ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36229) API for UI to honour permissions
Title: Message Title Vivek Pandey started work on JENKINS-36229 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36229) API for UI to honour permissions
Title: Message Title Vivek Pandey commented on JENKINS-36229 Re: API for UI to honour permissions James Dumay yes JWT gets issues for anonymous user. I see your point, I think UI needs to display Login button if security is turned on. Putting such information in JWT token is bit odd though, its jenkins config information and there could be more going forward. Perhaps, right place could be in /organizations/:id API, where it provides organization level config information. Why does UI needs to load on every page, could it not cache it? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36067) A branch name (which is incorrect) is shown in the branch column of non multibranch jobs
Title: Message Title Ivan Meredith updated JENKINS-36067 Jenkins / JENKINS-36067 A branch name (which is incorrect) is shown in the branch column of non multibranch jobs Change By: Ivan Meredith Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title
Jesse Glick commented on JENKINS-31155
Re: Workflow shared library improvements
A sticky point is checking out a specified SCM at a specified tag. SCMSource does not really support this; it defines “heads” but these are generally only implemented to be branches. SCM does not offer any API to select even a branch, much less a tag, though typical implementations would allow the critical configuration field to be interpolated with build variables during checkout. I am thinking of a two-pronged approach:
Extend SCMSource to allow you to specify a version string and get back an SCMRevision that it resolves to; a Git implementation could accept branch names, tag names, other refs, short or long hashes—whatever Git normally accepts as per gitrevisions(7). Then build would check out the specified revision. This would provide the best experience, for sufficiently up-to-date SCM plugins.
As a fallback for older SCMSource implementations, or SCM plugins not implementing SCMSource at all, allow SingleSCMSource to be used, but add an EnvironmentContributor which sets variables with predictable names to the library versions used by the build. Then the global configuration would define, say, a library foo using GitSCM with a BranchSpec like ${lib.foo.version}, and leave it to checkout time to actually resolve that to something.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36076) Write acceptance tests for external workspace manager
Title: Message Title Alexandru Somai started work on JENKINS-36076 Change By: Alexandru Somai Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36898) Implement DiskInfoProvider extension point
Title: Message Title Alexandru Somai resolved as Done Done https://github.com/jenkinsci/external-workspace-manager-plugin/pull/27 Jenkins / JENKINS-36898 Implement DiskInfoProvider extension point Change By: Alexandru Somai Status: In Progress Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-36962) Integrate Job Restrictions plugin for Disk Pool restriction feature
Title: Message Title Alexandru Somai updated JENKINS-36962 Jenkins / JENKINS-36962 Integrate Job Restrictions plugin for Disk Pool restriction feature Change By: Alexandru Somai Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34981) Make valgrind-plugin compatible with pipeline
Title: Message Title Nenad Miksa commented on JENKINS-34981 Re: Make valgrind-plugin compatible with pipeline Any progress on this? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36899) Implement DiskAllocationStrategy extension point
Title: Message Title Alexandru Somai commented on JENKINS-36899 Re: Implement DiskAllocationStrategy extension point Done https://github.com/jenkinsci/external-workspace-manager-plugin/pull/33 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36899) Implement DiskAllocationStrategy extension point
Title: Message Title Alexandru Somai resolved as Done Jenkins / JENKINS-36899 Implement DiskAllocationStrategy extension point Change By: Alexandru Somai Status: In Progress Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37308) browserInstance null causes an NPE in Sauce On Demand plugin 1.154
Title: Message Title Gavin Mogan commented on JENKINS-37308 Re: browserInstance null causes an NPE in Sauce On Demand plugin 1.154 Hi Orlando Soto Thanks for the great bug report. I'm going to try and get this prioritized before the next release. How critical is it for you. Can you wait a couple weeks for the next release? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37263) Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash)
Title: Message Title
Quentin Dufour updated an issue
Jenkins / JENKINS-37263
Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash)
Change By:
Quentin Dufour
h2. Description of the problemI've a multibranch pipeline project configured with the local branch extension and many branch following the git flow model (features/). When I push a commit on the feature branch, this commit is detected by Jenkins, and pulled by the master to read the Jenkinsfile. The first time it works, but after that, the local branch is selected instead of the remote branch, amd the new commits are not fetch. The bug only occurs on branches with a slash in their names.h2. InvestigationI've connected my debugger to my Jenkins installation. !jenkins-local-branch-bug-1.PNG|thumbnail! It appears that Jenkins has detected 2 branches matching the name. One local and one remote. The local one is created by the local branch git extension.I can't explicitly specify to Jenkins to use the remote one because I use the pipeline plugin, and this checkout is made automatically to retrieve the Jenkinsfile. So, the git implementation takes the first one, which is generally the local branch which is not yet updated...{code:java}Revision marked = candidates.iterator().next();{code}h2. Logs{noformat}16:10:31 Multiple candidate revisions16:10:31 Checking out Revision 604398f062b459c797f31d6c13b568dd7612362d (features/my-feature-branch)16:10:31 > git.exe config core.sparsecheckout # timeout=3016:10:31 > git.exe checkout -f 604398f062b459c797f31d6c13b568dd7612362d # timeout=12016:10:32 > git.exe branch -a -v --no-abbrev # timeout=3016:10:32 > git.exe branch -D features/my-feature-branch # timeout=3016:10:32 > git.exe checkout -b features/my-feature-branch 604398f062b459c797f31d6c13b568dd7612362d # timeout=12016:10:32 > git.exe rev-list 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d # timeout=30{noformat}h2. How to fix itPossibilities I see : * Update the workflow-multibranch-plugin / branch-api-plugin to checkout on origin (prefix with refs/remotes/origin/) * Update the git-plugin to order the list, and prioritize remote branchesPersonally, I think the first one is safer, but I've not yet played with this plugin. Here is my proposition on Github: https://github.com/jenkinsci/branch-api-plugin/pull/47 h2. How to reproduce# Create a new repository and initialize it (on github, with a README.md for example)# Clone it on your computer: {noformat}git clone https://lausivoiduts.visualstudio.com/QuarahMC/_git/JENKINS-37263cd JENKINS-37263{noformat}# Create a new branch: {noformat}git checkout -b features/this-bug{noformat}# Add something in the Jenkinsfile: {noformat}echo "echo 'first commit' " > Jenkinsfile{noformat}# Commit and push it: {noformat}git add Jenkinfilegit commit -m "first commit" git push --set-upstream origin features/this-bug{noformat}# Add a new Multibranch Pipeline Project in Jenkins, add as Source your git repository. Click on "Add Behaviour", select "Checkout to a local
[JIRA] (JENKINS-37320) SAML SSO plugin change - Enable Unified Jenkins profile config for SSO
Title: Message Title
Anita Dongare created an issue
Jenkins / JENKINS-37320
SAML SSO plugin change - Enable Unified Jenkins profile config for SSO
Issue Type:
New Feature
Assignee:
Ben McCann
Components:
saml-plugin
Created:
2016/Aug/10 8:41 PM
Environment:
Jenkins version : 1.642.18.1 SAML-plugin version : 0.5 (we noticed this issue in 0.5 version, we have not tested the new 0.6 version)
Priority:
Major
Reporter:
Anita Dongare
We require a small change in Jenkins SAML plugin code, to fulfill our requirement of having a unified Jenkins SSO profile. It's a one line code. Should we make that change and create a pull request on the SAML github repo? Or if some one from your team could make the required change and create new artifact version for SAML. So we can use the updated version in our Jenkins setup. Code change we need: File: SamlSecurityRealm.java / private Saml2Client newClient() { Preconditions.checkNotNull(this.idpMetadata); Saml2Client client = new Saml2Client(); //this line needs to be added client. setSpEntityId( "OUR OWN ID PREFERABLE CONFIGURED IN THE FILE" ); client.setIdpMetadata(this.idpMetadata); client.setCallbackUrl(getConsumerServiceUrl()); client.setDestinationBindingType("urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"); client.setMaximumAuthenticationLifetime(Integer.valueOf(this.maximumAuthenticationLifetime)); return client; }
[JIRA] (JENKINS-37307) Java stack exception shown inspite of installing supress stack trace plugin
Title: Message Title Maitrey Mishra updated an issue Jenkins / JENKINS-37307 Java stack exception shown inspite of installing supress stack trace plugin Change By: Maitrey Mishra Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37319) Add "maxlines" to "FILE" token macro
Title: Message Title Shannon Kerr created an issue Jenkins / JENKINS-37319 Add "maxlines" to "FILE" token macro Issue Type: Improvement Assignee: David van Laatum Components: email-ext-plugin, token-macro-plugin Created: 2016/Aug/10 7:37 PM Environment: Jenkins 1.642.3 Priority: Minor Reporter: Shannon Kerr We read in a readme file to include in our email announcement and we'd like to limit the number of lines to (for example) the first 50 of that file. So, a "maxLines" parameter like the BUILD_LOG token has would be perfect. Add Comment
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-31155 Workflow shared library improvements Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Jesse Glick commented on JENKINS-31155 Re: Workflow shared library improvements will it replace cps-global-lib Probably I would add options to the same plugin. Either way, the existing feature is not going to go anywhere. do you have any particular timetable for this feature? I am looking into it. Rough outline of proposed implementation: a configuration fragment defining a “library”, including SCM details and default version choice (branch/tag/revision); the repository should have the same layout as the current global library repo, plus a resources folder a configuration fragment for a list of libraries with symbolic names, some of which may be loaded by default (Jenkinsfile need do nothing to start using them) a global configuration setting available with RUN_SCRIPTS a folder property an ASTTransformation allowing some annotation to be processed in Jenkinsfile specifying libraries to use, optionally with versions a per-job per-library private workspace on master to check out SCM a per-build JAR of loaded libraries as checked out at the start of the build (including the patternset src/,vars/,resources/)—allows consistent snapshots of branches to be used; prevents network I/O when resuming a build; and allows Replay to see what was used a GroovyShellDecorator adding those JARs to the classpath some step to load resources for trusted libraries, third-party code via @Grab (already implemented in JENKINS-26192 but integration would need to be tested) GlobalVariableList using the last-loaded versions of global libraries for reference documentation (perhaps also for folder-level libraries, with some API hooks) Add Comment
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Jesse Glick started work on JENKINS-31155 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Oleg Nenashev commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Created https://github.com/jenkinsci/remoting/pull/99 and https://github.com/jenkinsci/jenkins/pull/2503, which seem to solve/suppress issue in my case. Need a code review BTW Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Kevin Phillips edited a comment on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection [~pwiseman] In some cases, where checkouts take dozens of minutes or more, this overhead can be even more significant. Also, besides the obvious performance impact of having multiple checkouts of the same repository across a build farm are is the storage overhead this causes on the Jenkins master. Suppose you have a large repository with dozens of gigabytes of data, and your teams are encouraged to follow agile methodologies and create feature branches regularly. Each one of these short-lived branches would then be checked out in it's entirety on the master consuming enormous amounts of space. Combine this with the fact that these "temporary" workspaces seem to persist indefinitely would inevitably result in the Jenkins master running out of storage space.IMO this is a fundamental design flaw with the pipeline plugin that completely prevents it from being usable at scale. :(PS: Even though there are ways to checkout subsets of a repository with certain SCM tools like SVN, many popular alternatives (ie: Git) either can't do such operations at all or at the very least are very difficult to do so. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Kevin Phillips commented on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection Peter Wiseman In some cases, where checkouts take dozens of minutes or more, this overhead can be significant. Also, besides the obvious performance impact of having multiple checkouts of the same repository across a build farm are the storage overhead this causes on the Jenkins master. Suppose you have a large repository with dozens of gigabytes of data, and your teams are encouraged to follow agile methodologies and create feature branches regularly. Each one of these short-lived branches would then be checked out in it's entirety on the master consuming enormous amounts of space. Combine this with the fact that these "temporary" workspaces seem to persist would inevitably result in the Jenkins master running out of storage space. IMO this is a fundamental design flaw with the pipeline plugin that completely prevents it from being usable at scale. PS: Even though there are ways to checkout subsets of a repository with certain SCM tools like SVN, many popular alternatives (ie: Git) either can't do such operations at all or at the very least are very difficult to do so. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Kevin Phillips edited a comment on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection [~pwiseman] In some cases, where checkouts take dozens of minutes or more, this overhead can be even more significant. Also, besides the obvious performance impact of having multiple checkouts of the same repository across a build farm are the storage overhead this causes on the Jenkins master. Suppose you have a large repository with dozens of gigabytes of data, and your teams are encouraged to follow agile methodologies and create feature branches regularly. Each one of these short-lived branches would then be checked out in it's entirety on the master consuming enormous amounts of space. Combine this with the fact that these "temporary" workspaces seem to persist would inevitably result in the Jenkins master running out of storage space.IMO this is a fundamental design flaw with the pipeline plugin that completely prevents it from being usable at scale. :(PS: Even though there are ways to checkout subsets of a repository with certain SCM tools like SVN, many popular alternatives (ie: Git) either can't do such operations at all or at the very least are very difficult to do so. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title gitt commented on JENKINS-31155 Re: Workflow shared library improvements We currently do not use cps-global-lib and store our shared modules in SCM because of lack of versioning support in cps-global-lib. We then checkout the files from SCM and use load step to load them in Jenkinsfiles in different pipelines. My question is: if you implement the feature as described above (seems exactly what many teams need), will it replace cps-global-lib? And do you have any particular timetable for this feature? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Kevin Phillips edited a comment on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection Would there not be a way to simply have a pipeline / multibranch job checkout the code for a specific branch on a specific node, and then execute the DSL from the Jenkinsfile directly on that node so that the checkout and build may be performed in the same workspace on the same agent? This would seem to be more inline with how other, more modern CI systems work like travis-ci.I could be wrong, but it seems to me the design of the pipeline / multibranch plugins seems to assume that the configuration file should will be stored independently from the code being built by the job orchestration. This seems like a design flaw to me seeing as how the main benefit of these plugins is in having the config file stored with the application code. That being If storing the case Jenkinsfile with the code is in fact a requirement for these plugins then any solution that requires the application code (ie: an entire repository in the Git case) to be checked out multiple times in multiple locations for each build is simply unscalable. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Kevin Phillips edited a comment on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection Would there not be a way to simply have a pipeline / multibranch job checkout the code for a specific branch on a specific node, and then execute the DSL from the Jenkinsfile directly on that node so that the checkout and build may be performed in the same workspace on the same agent? This would seem to be more inline with how other, more modern CI systems work like travis-ci.I could be wrong, but it seems to me the design of the pipeline / multibranch plugins seems to assume that the configuration file should be stored independently from the code being built by the job orchestration. This seems like a design flaw to me seeing as how the main benefit of these plugins is in having the config file stored with the application code. That being the case any solution that requires the application code (ie: an entire repository in the Git case) to be checked out multiple times in multiple locations for each build is simply unscalable. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Kevin Phillips commented on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection Would there not be a way to simply have a pipeline / multibranch job checkout the code for a specific branch on a specific node, and then execute the DSL from Jenkinsfile directly on that node so that the checkout and build may be performed in the same workspace on the same agent? This would seem to be more inline with how other, more modern CI systems work like travis-ci. I could be wrong, but it seems to me the design of the pipeline / multibranch plugins seems to assume that the configuration file should be stored independently from the code being built by the job orchestration. This seems like a design flaw to me seeing as how the main benefit of these plugins is in having the config file stored with the application code. That being the case any solution that requires the application code (ie: an entire repository in the Git case) to be checked out multiple times in multiple locations for each build is simply unscalable. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37318) Generate a background thread to allow for integration with Plugin Usage Plugin
Title: Message Title Dan Tranter updated an issue Jenkins / JENKINS-37318 Generate a background thread to allow for integration with Plugin Usage Plugin Change By: Dan Tranter Provide the needed ability to generate a list of plugins and usage count on a background thread, and then offer a link when finished. This will circumvent performance issues (especially on large instances with thousands of jobs) that would result from creating the computation inside an HTTP request thread Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37318) Generate a background thread to allow for integration with Plugin Usage Plugin
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-37318 Generate a background thread to allow for integration with Plugin Usage Plugin Issue Type: Improvement Assignee: Steven Christou Components: support-core-plugin Created: 2016/Aug/10 6:05 PM Priority: Minor Reporter: Dan Tranter Provide the needed generate on a background thread, and then offer a link when finished. This will circumvent performance issues (especially on large instances with thousands of jobs) that would result from creating the computation inside an HTTP request thread Add Comment
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Jesse Glick commented on JENKINS-31155 Re: Workflow shared library improvements Would this also include a default version or would default always be Master/Head unless specified on job? TBD, but probably a global or folder-level setting could specify a version. I assume this won't be true for folder level if that is done. Right, folder-level settings would not be trusted as far as Overall/RunScripts is concerned. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Patrick Wolf edited a comment on JENKINS-31155 Re: Workflow shared library improvements Jesse's list from above with commentsMust Have:* Must allow library code to be pulled from an external location on demand, rather than pushed into Jenkins.* Must allow each job using a library, or other developer-level configuration, to choose whether to pick the latest version, or a specific version.* * Would this also include a default version or would default always be Master/Head unless specified on job? Setting version used at Folder level might be a nice way to allow teams to migrate to newer version at own pace. Then again if we use a folder level library the folder level library could define a default version of the global library to be used.* Must support the “external location” being in any SCM plugin supported by Jenkins, where “latest version” is a branch and “specific version” is a revision or tag. (TBD whether conformance is to the old SCM API, the newer SCMSource with fewer implementations, or either.)* Must allow library code developed by, or on behalf of, a Jenkins administrator to run outside the Groovy sandbox.** for Global library. I assume this won't be true for folder level if that is done.* Must require library code developed by others to run inside the Groovy sandbox.* Must support both syntax options currently supported by workflow-cps-global-lib: class library, or global variable/function.* Accompanying functional tests must prove that behavior properly persists across Jenkins restarts, and (in CloudBees Jenkins Enterprise) after resuming from checkpoint.* Build resumption must not make network connections.* Must be possible to use a named library in a job without specifying connection details such as URL or credentials.* Must be possible to use the Replay feature to temporarily test the effect of changing some code inside a library on a given job.Nice to have:* Possibility for “external location” to be an artifact repository rather than an SCM, for example via @Grab.* Ability to implicitly load a library in all jobs in the system or within a folder (as in workflow-cps-global-lib).* Global Variables Reference support for the global variable mode of a library (as in workflow-cps-global-lib).* Ability to load non-Groovy support files packaged with the library, probably as String.* Ability to load third-party binary libraries, for example via @Grab.* Step to dynamically load a specified library into a running build, assuming its types were not already consulted during parsing. Add Comment
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Patrick Wolf commented on JENKINS-31155 Re: Workflow shared library improvements Jesse's list from above with comments Must Have: Must allow library code to be pulled from an external location on demand, rather than pushed into Jenkins. Must allow each job using a library, or other developer-level configuration, to choose whether to pick the latest version, or a specific version. * Would this also include a default version or would default always be Master/Head unless specified on job? Setting version used at Folder level might be a nice way to allow teams to migrate to newer version at own pace. Then again if we use a folder level library the folder level library could define a default version of the global library to be used. Must support the “external location” being in any SCM plugin supported by Jenkins, where “latest version” is a branch and “specific version” is a revision or tag. (TBD whether conformance is to the old SCM API, the newer SCMSource with fewer implementations, or either.) Must allow library code developed by, or on behalf of, a Jenkins administrator to run outside the Groovy sandbox. for Global library. I assume this won't be true for folder level if that is done. Must require library code developed by others to run inside the Groovy sandbox. Must support both syntax options currently supported by workflow-cps-global-lib: class library, or global variable/function. Accompanying functional tests must prove that behavior properly persists across Jenkins restarts, and (in CloudBees Jenkins Enterprise) after resuming from checkpoint. Build resumption must not make network connections. Must be possible to use a named library in a job without specifying connection details such as URL or credentials. Must be possible to use the Replay feature to temporarily test the effect of changing some code inside a library on a given job. Nice to have: Possibility for “external location” to be an artifact repository rather than an SCM, for example via @Grab. Ability to implicitly load a library in all jobs in the system or within a folder (as in workflow-cps-global-lib). Global Variables Reference support for the global variable mode of a library (as in workflow-cps-global-lib). Ability to load non-Groovy support files packaged with the library, probably as String. Ability to load third-party binary libraries, for example via @Grab.
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Patrick Wolf edited a comment on JENKINS-31155 Re: Workflow shared library improvements Jesse's list from above with commentsMust Have:* Must allow library code to be pulled from an external location on demand, rather than pushed into Jenkins.* Must allow each job using a library, or other developer-level configuration, to choose whether to pick the latest version, or a specific version.** Would this also include a default version or would default always be Master/Head unless specified on job? Setting version used at Folder level might be a nice way to allow teams to migrate to newer version at own pace. Then again if we use a folder level library the folder level library could define a default version of the global library to be used.* Must support the “external location” being in any SCM plugin supported by Jenkins, where “latest version” is a branch and “specific version” is a revision or tag. (TBD whether conformance is to the old SCM API, the newer SCMSource with fewer implementations, or either.)* Must allow library code developed by, or on behalf of, a Jenkins administrator to run outside the Groovy sandbox.** for Global library. I assume this won't be true for folder level if that is done.* Must require library code developed by others to run inside the Groovy sandbox.* Must support both syntax options currently supported by workflow-cps-global-lib: class library, or global variable/function.* Accompanying functional tests must prove that behavior properly persists across Jenkins restarts, and (in CloudBees Jenkins Enterprise) after resuming from checkpoint.* Build resumption must not make network connections.* Must be possible to use a named library in a job without specifying connection details such as URL or credentials.* Must be possible to use the Replay feature to temporarily test the effect of changing some code inside a library on a given job. Nice to have:* Possibility for “external location” to be an artifact repository rather than an SCM, for example via @Grab.* Ability to implicitly load a library in all jobs in the system or within a folder (as in workflow-cps-global-lib).* Global Variables Reference support for the global variable mode of a library (as in workflow-cps-global-lib).* Ability to load non-Groovy support files packaged with the library, probably as String.* Ability to load third-party binary libraries, for example via @Grab.* Step to dynamically load a specified library into a running build, assuming its types were not already consulted during parsing. Add Comment
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title
Jesse Glick edited a comment on JENKINS-31155
Re: Workflow shared library improvements
What I think the mandatory requirements are:* Must allow library code to be pulled from an external location on demand, rather than pushed into Jenkins.* Must allow each job using a library, or other developer-level configuration, to choose whether to pick the latest version, or a specific version.* Must support the “external location” being in any SCM plugin supported by Jenkins, where “latest version” is a branch and “specific version” is a revision or tag. (TBD whether conformance is to the old {{SCM}} API, the newer {{SCMSource}} with fewer implementations, or either.)* Must allow library code developed by, or on behalf of, a Jenkins administrator to run outside the Groovy sandbox.* Must require library code developed by others to run inside the Groovy sandbox.* Must support both syntax options currently supported by {{workflow-cps-global-lib}}: class library, or global variable/function.* Accompanying functional tests must prove that behavior properly persists across Jenkins restarts, and (in CloudBees Jenkins Enterprise) after resuming from {{checkpoint}}.* Build resumption must not make network connections.* Must be possible to use a named library in a job without specifying connection details such as URL or credentials.* Must be possible to use the _Replay_ feature to temporarily test the effect of changing some code inside a library on a given job.Nice to have:* Possibility for “external location” to be an artifact repository rather than an SCM, for example via {{@Grab}}.* Ability to implicitly load a library in all jobs in the system or within a folder (as in {{workflow-cps-global-lib}}).* _Global Variables Reference_ support for the global variable mode of a library (as in {{workflow-cps-global-lib}}).* Ability to load non-Groovy support files packaged with the library, probably as {{String}}.* Ability to load third-party binary libraries, for example via {{@Grab}}. * Step to dynamically load a specified library into a running build, assuming its types were not already consulted during parsing.
Add Comment
This message was sent
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Jesse Glick commented on JENKINS-31155 Re: Workflow shared library improvements What I think the mandatory requirements are: Must allow library code to be pulled from an external location on demand, rather than pushed into Jenkins. Must allow each job using a library, or other developer-level configuration, to choose whether to pick the latest version, or a specific version. Must support the “external location” being in any SCM plugin supported by Jenkins, where “latest version” is a branch and “specific version” is a revision or tag. (TBD whether conformance is to the old SCM API, the newer SCMSource with fewer implementations, or either.) Must allow library code developed by, or on behalf of, a Jenkins administrator to run outside the Groovy sandbox. Must require library code developed by others to run inside the Groovy sandbox. Must support both syntax options currently supported by workflow-cps-global-lib: class library, or global variable/function. Accompanying functional tests must prove that behavior properly persists across Jenkins restarts, and (in CloudBees Jenkins Enterprise) after resuming from checkpoint. Build resumption must not make network connections. Must be possible to use a named library in a job without specifying connection details such as URL or credentials. Must be possible to use the Replay feature to temporarily test the effect of changing some code inside a library on a given job. Nice to have: Possibility for “external location” to be an artifact repository rather than an SCM, for example via @Grab. Ability to implicitly load a library in all jobs in the system or within a folder (as in workflow-cps-global-lib). Global Variables Reference support for the global variable mode of a library (as in workflow-cps-global-lib). Ability to load non-Groovy support files packaged with the library, probably as String. Ability to load third-party binary libraries, for example via @Grab.
[JIRA] (JENKINS-37317) Variant plugin not working when requiredClasses don't exist
Title: Message Title Alvaro Lobato commented on JENKINS-37317 Re: Variant plugin not working when requiredClasses don't exist Filed PR with a proposed fix https://github.com/jenkinsci/variant-plugin/pull/1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37317) Variant plugin not working when requiredClasses don't exist
Title: Message Title Alvaro Lobato started work on JENKINS-37317 Change By: Alvaro Lobato Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37196) DSL for Violation Comments to GitHub Plugin
Title: Message Title Tomas Bjerre commented on JENKINS-37196 Re: DSL for Violation Comments to GitHub Plugin I just made a new release, changed the DSL a bit. Use the examples from the README at: https://github.com/jenkinsci/violation-comments-to-github-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36468) Tasks fail to run on ECS after upgrade to 1.4
Title: Message Title Luis Silva updated an issue Jenkins / JENKINS-36468 Tasks fail to run on ECS after upgrade to 1.4 Change By: Luis Silva Environment: Jenkins 2. 11 17 ECS-plugin 1.4 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36468) Tasks fail to run on ECS after upgrade to 1.4
Title: Message Title
Luis Silva edited a comment on JENKINS-36468
Re: Tasks fail to run on ECS after upgrade to 1.4
Hi Jan, Sorry for the late reply but I 've been off.I can't give you access to that Env I'm sorry, company policy. I ran this again with 1.4 with the Scenario below:- nothing running in running in Jenkins- nothing running/pending on ECS- Only 1 server in the ASG that serves ECS and correctly registered with ECS * Analysis * :It looks like Jenkins triggers the task but times out after 9/10 seconds. In the meantime, ECS is happily pulling the image from ECR but when it is ready to notify Jenkins that the container is up and running, Jenkins is long gone. During that period Jenkins keeps trying to launch the task on ECS multiple time, but there aren't any more resources available because the first task is still spooling up in ECS and it takes up almost all of the resources on that server. Check the logs below: * Jenkins log * :{quote}Aug 10, 2016 4:31:26 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl applyINFO: Started provisioning ECS Slave MyTests from JenkinsSlavesECS with 1 executors. Remaining excess workload: 0Aug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Found 1 instancesAug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Resources found in instance arn:aws:ecs:eu-west-1:ACCOUNT_ID:container-instance/2506c5b8-946c-41c6-b01d-x: [{Name: CPU,Type: INTEGER,DoubleValue: 0.0,LongValue: 0,IntegerValue: 1024,StringSetValue: []}, {Name: MEMORY,Type: INTEGER,DoubleValue: 0.0,LongValue: 0,IntegerValue: 3767,StringSetValue: []}, {Name: PORTS,Type: STRINGSET,DoubleValue: 0.0,LongValue: 0,IntegerValue: 0,StringSetValue: [22, 2376, 2375, 51678]}, {Name: PORTS_UDP,Type: STRINGSET,DoubleValue: 0.0,LongValue: 0,IntegerValue: 0,StringSetValue: []}]Aug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Instance arn:aws:ecs:eu-west-1:ACCOUNT_ID:container-instance/2506c5b8-946c-41c6-b01d-x has 3,767mb of free memory. 3,200mb are requiredAug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Instance arn:aws:ecs:eu-west-1:ACCOUNT_ID:container-instance/2506c5b8-946c-41c6-b01d-x has 1,024 units of free cpu. 1,024 units are requiredAug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback callINFO: Created Slave: JenkinsSlavesECS-yyAug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback callINFO: Slave JenkinsSlavesECS-yy - Slave Task Started : arn:aws:ecs:eu-west-1:ACCOUNT_ID:task/ed743e1e-7be1-455b-a01d-zzAug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback callWARNING: ECS Slave JenkinsSlavesECS-yy (ecs task arn:aws:ecs:eu-west-1:ACCOUNT_ID:task/ed743e1e-7be1-455b-a01d-zz) not connected since 8/10/16 4:31 PM secondsAug 10, 2016 4:31:36 PM hudson.slaves.NodeProvisioner$2 runWARNING: Provisioned agent ECS Slave MyTests failed to launchjava.lang.IllegalStateException: ECS Slave JenkinsSlavesECS-yy (ecs task arn:aws:ecs:eu-west-1:ACCOUNT_ID:task/ed743e1e-7be1-455b-a01d-zz) not connected since 8/10/16 4:31 PM secondsat com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:278)at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:219)at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
[JIRA] (JENKINS-36468) Tasks fail to run on ECS after upgrade to 1.4
Title: Message Title
Luis Silva edited a comment on JENKINS-36468
Re: Tasks fail to run on ECS after upgrade to 1.4
Hi Jan,I can't give you access to that Env I'm sorry, company policy. I ran this again with 1.4 with the Scenario below:- nothing running in running in Jenkins- nothing running/pending on ECS- Only 1 server in the ASG that serves ECS and correctly registered with ECSAnalysis:It looks like Jenkins triggers the task but times out after 9/10 seconds. In the meantime, ECS is happily pulling the image from ECR but when it is ready to notify Jenkins that the container is up and running, Jenkins is long gone. During that period Jenkins keeps trying to launch the task on ECS multiple time, but there aren't any more resources available because the first task is still spooling up in ECS and it takes up almost all of the resources on that server. Check the logs below: Jenkins log:{quote}Aug 10, 2016 4:31:26 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl applyINFO: Started provisioning ECS Slave MyTests from JenkinsSlavesECS with 1 executors. Remaining excess workload: 0Aug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Found 1 instancesAug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Resources found in instance arn:aws:ecs:eu-west-1:ACCOUNT_ID:container-instance/2506c5b8-946c-41c6-b01d-x: [{Name: CPU,Type: INTEGER,DoubleValue: 0.0,LongValue: 0,IntegerValue: 1024,StringSetValue: []}, {Name: MEMORY,Type: INTEGER,DoubleValue: 0.0,LongValue: 0,IntegerValue: 3767,StringSetValue: []}, {Name: PORTS,Type: STRINGSET,DoubleValue: 0.0,LongValue: 0,IntegerValue: 0,StringSetValue: [22, 2376, 2375, 51678]}, {Name: PORTS_UDP,Type: STRINGSET,DoubleValue: 0.0,LongValue: 0,IntegerValue: 0,StringSetValue: []}]Aug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Instance arn:aws:ecs:eu-west-1:ACCOUNT_ID:container-instance/2506c5b8-946c-41c6-b01d-x has 3,767mb of free memory. 3,200mb are requiredAug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResourcesINFO: Instance arn:aws:ecs:eu-west-1:ACCOUNT_ID:container-instance/2506c5b8-946c-41c6-b01d-x has 1,024 units of free cpu. 1,024 units are requiredAug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback callINFO: Created Slave: JenkinsSlavesECS-yyAug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback callINFO: Slave JenkinsSlavesECS-yy - Slave Task Started : arn:aws:ecs:eu-west-1:ACCOUNT_ID:task/ed743e1e-7be1-455b-a01d-zzAug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback callWARNING: ECS Slave JenkinsSlavesECS-yy (ecs task arn:aws:ecs:eu-west-1:ACCOUNT_ID:task/ed743e1e-7be1-455b-a01d-zz) not connected since 8/10/16 4:31 PM secondsAug 10, 2016 4:31:36 PM hudson.slaves.NodeProvisioner$2 runWARNING: Provisioned agent ECS Slave MyTests failed to launchjava.lang.IllegalStateException: ECS Slave JenkinsSlavesECS-yy (ecs task arn:aws:ecs:eu-west-1:ACCOUNT_ID:task/ed743e1e-7be1-455b-a01d-zz) not connected since 8/10/16 4:31 PM secondsat com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:278)at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:219)at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)at
[JIRA] (JENKINS-36393) Cannot find sbt options in Manage system with sbt-plugin
Title: Message Title Emmett Keyser commented on JENKINS-36393 Re: Cannot find sbt options in Manage system with sbt-plugin sbt configuration is now located under Manage Jenkins -> Global Tool Configuration Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36468) Tasks fail to run on ECS after upgrade to 1.4
Title: Message Title
Luis Silva commented on JENKINS-36468
Re: Tasks fail to run on ECS after upgrade to 1.4
Hi Jan, I can't give you access to that Env I'm sorry, company policy. I ran this again with 1.4 with the Scenario below:
nothing running in running in Jenkins
nothing running/pending on ECS
Only 1 server in the ASG that serves ECS and correctly registered with ECS
Analysis: It looks like Jenkins triggers the task but times out after 9/10 seconds. In the meantime, ECS is happily pulling the image from ECR but when it is ready to notify Jenkins that the container is up and running, Jenkins is long gone. Check the logs below: Jenkins log:
Aug 10, 2016 4:31:26 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning ECS Slave MyTests from JenkinsSlavesECS with 1 executors. Remaining excess workload: 0 Aug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResources INFO: Found 1 instances Aug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResources INFO: Resources found in instance arn:aws:ecs:eu-west-1:ACCOUNT_ID:container-instance/2506c5b8-946c-41c6-b01d-x: [
Unknown macro: {Name}
,
Unknown macro: {Name}
,
Unknown macro: {Name}
,
Unknown macro: {Name}
] Aug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResources INFO: Instance arn:aws:ecs:eu-west-1:ACCOUNT_ID:container-instance/2506c5b8-946c-41c6-b01d-x has 3,767mb of free memory. 3,200mb are required Aug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResources INFO: Instance arn:aws:ecs:eu-west-1:ACCOUNT_ID:container-instance/2506c5b8-946c-41c6-b01d-x has 1,024 units of free cpu. 1,024 units are required Aug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback call INFO: Created Slave: JenkinsSlavesECS-yy Aug 10, 2016 4:31:27 PM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback call INFO: Slave JenkinsSlavesECS-yy - Slave Task Started : arn:aws:ecs:eu-west-1:ACCOUNT_ID:task/ed743e1e-7be1-455b-a01d-zz Aug 10, 2016 4:31:27 PM
[JIRA] (JENKINS-37317) Variant plugin not working when requiredClasses don't exist
Title: Message Title Alvaro Lobato updated an issue Jenkins / JENKINS-37317 Variant plugin not working when requiredClasses don't exist Change By: Alvaro Lobato Summary: Variant plugin not workin working when requiredClasses don't exist Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37317) Variant plugin not workin when requiredClasses don't exist
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-37317 Variant plugin not workin when requiredClasses don't exist Issue Type: Bug Assignee: Alvaro Lobato Components: other Created: 2016/Aug/10 5:08 PM Priority: Minor Reporter: Alvaro Lobato The Variant Plugin (https://github.com/jenkinsci/variant-plugin/) is not working properly when you specify `requiredClasses` and one of them do not exists. There are two observed situations. If the annotated class extends the non existent class this exception is thrown: WARNING: Failed to load org.jenkinsci.plugins.variant.Negative4 java.lang.InstantiationException: java.lang.NoClassDefFoundError: org/jenkinsci/plugins/Beer at net.java.sezpoz.IndexItem.element(IndexItem.java:146) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:504) at com.google.inject.AbstractModule.configure(AbstractModule.java:62) at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:230) at com.google.inject.spi.Elements.getElements(Elements.java:103) at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:136) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) at com.google.inject.Guice.createInjector(Guice.java:96) at com.google.inject.Guice.createInjector(Guice.java:73) at hudson.ExtensionFinder$GuiceFinder.(ExtensionFinder.java:282) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at
[JIRA] (JENKINS-37316) After Jenkins restart, concurrent builds only work after clicking 'save' on each job.
Title: Message Title Igor Hansen created an issue Jenkins / JENKINS-37316 After Jenkins restart, concurrent builds only work after clicking 'save' on each job. Issue Type: Bug Assignee: Oleg Nenashev Components: throttle-concurrent-builds-plugin Created: 2016/Aug/10 5:07 PM Environment: Jenkins 1.651.3, Throttle Concurrent Builds Plug-in 1.9.0 Labels: plugin Priority: Major Reporter: Igor Hansen When using the "Prevent multiple jobs with identical parameters from running concurrently" feature, concurrent jobs are only allowed after going into each job's configure page, then clicking save on them. Restarting jenkins reverts back to the behavior of not allowing concurrent jobs, and once again going back into each job's configuration page and clicking save re-enables concurrent jobs. The settings on the jobs are: ghprbPullAuthorLogin (string parameter) ghprbSourceBranch (string parameter) ... lots of other parameters Throttle concurrent builds (checked) Throttle this project alone Maximum total concurrent builds: 10 Maximum concurrent builds per node: 10 Prevent multiple jobs with identical parameters from running concurrently (checked) List of parameters to check: ghprbPullAuthorLogin, ghprbSourceBranch This functionality is really critical for us, and this bug makes this plugin barely usable.
[JIRA] (JENKINS-37315) Make JNLP3 opt-in for all
Title: Message Title stephenconnolly created an issue Jenkins / JENKINS-37315 Make JNLP3 opt-in for all Issue Type: Bug Assignee: stephenconnolly Components: core Created: 2016/Aug/10 4:37 PM Labels: lts-candidate Priority: Blocker Reporter: stephenconnolly Too many encoding issues with JNLP3 protocol. We should stop A/B testing it for HEAD and LTS Add Comment
[JIRA] (JENKINS-37314) Pipeline view do not show Pipeline Job
Title: Message Title Frédéric Meyrou created an issue Jenkins / JENKINS-37314 Pipeline view do not show Pipeline Job Issue Type: Bug Assignee: Unassigned Components: pipeline-view-plugin Created: 2016/Aug/10 4:31 PM Environment: Latest LTS V2.7.2 Windows 2012R2 Labels: pipeline Priority: Minor Reporter: Frédéric Meyrou Hi, I'm new to pipelines. When I create a pipeline view, I can't add a Pipeline Job in the "Select Initial Job" field. It only show-up normal Jobs. Is this normal behaviour? Tks for helping, ./Frederic Add Comment
[JIRA] (JENKINS-37313) "Test BlazeMeter API Key" results in NullPointerException when using proxy
Title: Message Title
stephan stachurski updated an issue
Jenkins / JENKINS-37313
"Test BlazeMeter API Key" results in NullPointerException when using proxy
Change By:
stephan stachurski
This is using Jenkins ver. 1.646, and BlazeMeter plugin 2.5.In my jenkins proxy configuration, I can set that and successfully reach http/https://a.blazemeter.com using "Validate Proxy". I get Although it looks like the same NullPointerException whether or not {{a.blazemeter.com}} proxy is in the "No Proxy Host" list.This was in the logs:{code}Aug 10 configured correctly , 2016 11:11:35 AM WARNING org.apache.commons.httpclient.HttpMethodBase processCookieHeadersCookie rejected: "$Version=0; SESSb102712a80d2d43dc6b4d9215fecd243=f6hrd73tfsn5dr2qe0upg6fge4; $Path=/; $Domain=. when adding a . blazemeter .com". Illegal domain attribute ".a.blazemeter.com". Domain of origin: "a.blazemeter.com"Aug 10 API key credential , 2016 11:11:35 AM WARNING org.apache.commons.httpclient.HttpMethodBase processCookieHeadersCookie rejected: " $Version=0; SESSb102712a80d2d43dc6b4d9215fecd243=6arfhjufqe71gps0d89o07hu35; $Path=/; $Domain=.a.blazemeter.com Test Blazemeter API Key " . Illegal domain attribute ". results in a NullPointerException . blazemeter.com". Domain of origin: "a.blazemeter.com" {code} Here's the stack trace:{code}javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:38) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:102) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at
[JIRA] (JENKINS-37313) "Test BlazeMeter API Key" results in NullPointerException when using proxy
Title: Message Title
stephan stachurski updated an issue
Jenkins / JENKINS-37313
"Test BlazeMeter API Key" results in NullPointerException when using proxy
Change By:
stephan stachurski
This is using Jenkins ver. 1.646, and BlazeMeter plugin 2.5.In my jenkins proxy configuration, I can set that and successfully reach http/https://a.blazemeter.com using "Validate Proxy".I get the same NullPointerException whether or not {{a.blazemeter.com}} is in the "No Proxy Host" list. This was in the logs:{code}Aug 10, 2016 11:11:35 AM WARNING org.apache.commons.httpclient.HttpMethodBase processCookieHeadersCookie rejected: "$Version=0; SESSb102712a80d2d43dc6b4d9215fecd243=f6hrd73tfsn5dr2qe0upg6fge4; $Path=/; $Domain=.a.blazemeter.com". Illegal domain attribute ".a.blazemeter.com". Domain of origin: "a.blazemeter.com"Aug 10, 2016 11:11:35 AM WARNING org.apache.commons.httpclient.HttpMethodBase processCookieHeadersCookie rejected: "$Version=0; SESSb102712a80d2d43dc6b4d9215fecd243=6arfhjufqe71gps0d89o07hu35; $Path=/; $Domain=.a.blazemeter.com". Illegal domain attribute ".a.blazemeter.com". Domain of origin: "a.blazemeter.com"{code} Here's the stack trace:{code}javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:38) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:102) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at
[JIRA] (JENKINS-37313) "Test BlazeMeter API Key" results in NullPointerException when using proxy
Title: Message Title stephan stachurski created an issue Jenkins / JENKINS-37313 "Test BlazeMeter API Key" results in NullPointerException when using proxy Issue Type: Bug Assignee: Unassigned Components: blazemeterjenkinsplugin Created: 2016/Aug/10 3:53 PM Priority: Minor Reporter: stephan stachurski This is using Jenkins ver. 1.646, and BlazeMeter plugin 2.5. In my jenkins proxy configuration, I can set that and successfully reach http/https://a.blazemeter.com using "Validate Proxy". I get the same NullPointerException whether or not a.blazemeter.com is in the "No Proxy Host" list. Here's the stack trace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:38) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at
[JIRA] (JENKINS-37263) Jenkins checkout the wrong commit when used with the local branch extension on a branch with a / (slash)
Title: Message Title
Quentin Dufour updated an issue
Jenkins / JENKINS-37263
Jenkins checkout the wrong commit when used with the local branch extension on a branch with a / (slash)
Change By:
Quentin Dufour
h2. Description of the problemI've a multibranch pipeline project configured with the local branch extension and many branch following the git flow model (features/). When I push a commit on the feature branch, this commit is detected by Jenkins, and pulled by the master to read the Jenkinsfile. The first time it works, but after that, the local branch is selected instead of the remote branch, amd the new commits are not fetch. The bug only occurs on branches with a slash in their names.h2. InvestigationI've connected my debugger to my Jenkins installation. !jenkins-local-branch-bug-1.PNG|thumbnail! It appears that Jenkins has detected 2 branches matching the name. One local and one remote. The local one is created by the local branch git extension.I can't explicitly specify to Jenkins to use the remote one because I use the pipeline plugin, and this checkout is made automatically to retrieve the Jenkinsfile. So, the git implementation takes the first one, which is generally the local branch which is not yet updated...{code:java}Revision marked = candidates.iterator().next();{code}h2. Logs{noformat}16:10:31 Multiple candidate revisions16:10:31 Checking out Revision 604398f062b459c797f31d6c13b568dd7612362d (features/my-feature-branch)16:10:31 > git.exe config core.sparsecheckout # timeout=3016:10:31 > git.exe checkout -f 604398f062b459c797f31d6c13b568dd7612362d # timeout=12016:10:32 > git.exe branch -a -v --no-abbrev # timeout=3016:10:32 > git.exe branch -D features/my-feature-branch # timeout=3016:10:32 > git.exe checkout -b features/my-feature-branch 604398f062b459c797f31d6c13b568dd7612362d # timeout=12016:10:32 > git.exe rev-list 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d # timeout=30{noformat}h2. How to fix itPossibilities I see : * Update the workflow-multibranch-plugin to checkout on origin (prefix with refs/remotes/origin/) * Update the git-plugin to order the list, and prioritize remote branchesPersonally, I think the first one is safer, but I've not yet played with this plugin.h2. How to reproduce# Create a new repository and initialize it (on github, with a README.md for example)# Clone it on your computer: {noformat}git clone https://lausivoiduts.visualstudio.com/QuarahMC/_git/JENKINS-37263 ; cd JENKINS-37263{noformat}# Create a new branch: {noformat} git checkout -b features/this-bug {noformat} # Add something in the Jenkinsfile: {noformat} echo "echo 'first commit' " > Jenkinsfile {noformat} # Commit and push it: {noformat} git add Jenkinfile ; git commit -m "first commit" ;git push --set-upstream origin features/this-bug {noformat} # Add a new Multibranch Pipeline Project in Jenkins, add as Source your git repository.Click on "Add Behaviour", select "Checkout to a local branch".Set its value to "**" (without the quotes).Validate it.#
[JIRA] (JENKINS-34774) ClosedChannelException in log (excessive)
Title: Message Title David Feldsine commented on JENKINS-34774 Re: ClosedChannelException in log (excessive) I agree with Russ, from a Jenkins perspective the issue is that there does not appear to be any way to determine the destination for this failure. I have changed the debug level to 9; however this does not appear to have any impact on the contents of the Jenkins log. Until I can figure out the destination (plugin) I am at a loss. Once I am able to determine the plugin, I can open a ticket with them for why I am getting 300,000+ of these per day. They are doing retries on multiple failures every second and they never give up. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37263) Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash)
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37263 Jenkins checkout the wrong commit when used with the local branch behaviour on a branch with a / (slash) Change By: Quentin Dufour Summary: Jenkins checkout the wrong commit when used with the local branch extension behaviour on a branch with a / (slash) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37263) Jenkins checkout the wrong commit when used with the local branch extension on a branch with a / (slash)
Title: Message Title
Quentin Dufour updated an issue
Jenkins / JENKINS-37263
Jenkins checkout the wrong commit when used with the local branch extension on a branch with a / (slash)
Change By:
Quentin Dufour
h2. Description of the problemI've a multibranch pipeline project configured with the local branch extension and many branch following the git flow model (features/). When I push a commit on the feature branch, this commit is detected by Jenkins, and pulled by the master to read the Jenkinsfile. The first time it works, but after that, the local branch is selected instead of the remote branch, amd the new commits are not fetch. The bug only occurs on branches with a slash in their names.h2. InvestigationI've connected my debugger to my Jenkins installation. !jenkins-local-branch-bug-1.PNG|thumbnail! It appears that Jenkins has detected 2 branches matching the name. One local and one remote. The local one is created by the local branch git extension.I can't explicitly specify to Jenkins to use the remote one because I use the pipeline plugin, and this checkout is made automatically to retrieve the Jenkinsfile. So, the git implementation takes the first one, which is generally the local branch which is not yet updated...{code:java}Revision marked = candidates.iterator().next();{code}h2. Logs{noformat}16:10:31 Multiple candidate revisions16:10:31 Checking out Revision 604398f062b459c797f31d6c13b568dd7612362d (features/my-feature-branch)16:10:31 > git.exe config core.sparsecheckout # timeout=3016:10:31 > git.exe checkout -f 604398f062b459c797f31d6c13b568dd7612362d # timeout=12016:10:32 > git.exe branch -a -v --no-abbrev # timeout=3016:10:32 > git.exe branch -D features/my-feature-branch # timeout=3016:10:32 > git.exe checkout -b features/my-feature-branch 604398f062b459c797f31d6c13b568dd7612362d # timeout=12016:10:32 > git.exe rev-list 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d # timeout=30{noformat}h2. How to fix itPossibilities I see : * Update the workflow-multibranch-plugin to checkout on origin (prefix with refs/remotes/origin/) * Update the git-plugin to order the list, and prioritize remote branchesPersonally, I think the first one is safer, but I've not yet played with this plugin.h2. How to reproduce# Create a new repository and initialize it (on github, with a README.md for example)# Clone it on your computer: {noformat} git clone https://lausivoiduts.visualstudio.com/QuarahMC/_git/JENKINS-37263 ; cd JENKINS-37263 {noformat} # Create a new branch: git checkout -b features/this-bug# Add something in the Jenkinsfile: echo "echo 'first commit' " > Jenkinsfile# Commit and push it: git add Jenkinfile ; git commit -m "first commit" ; git push --set-upstream origin features/this-bug# Add a new Multibranch Pipeline Project in Jenkins, add as Source your git repository. Click on "Add Behaviour", select "Checkout to a local branch". Set its value to "**" (without the quotes). Validate it.# Check that the branch was built, and the message "first commit" appears in the log# Modify
[JIRA] (JENKINS-37263) Jenkins checkout the wrong commit when used with the local branch extension on a branch with a / (slash)
Title: Message Title
Quentin Dufour updated an issue
Jenkins / JENKINS-37263
Jenkins checkout the wrong commit when used with the local branch extension on a branch with a / (slash)
Change By:
Quentin Dufour
h2. Description of the problemI've a multibranch pipeline project configured with the local branch extension and many branch following the git flow model (features/). When I push a commit on the feature branch, this commit is detected by Jenkins, and pulled by the master to read the Jenkinsfile. The first time it works, but after that, the local branch is selected instead of the remote branch, amd the new commits are not fetch. The bug only occurs on branches with a slash in their names.h2. InvestigationI've connected my debugger to my Jenkins installation. !jenkins-local-branch-bug-1.PNG|thumbnail! It appears that Jenkins has detected 2 branches matching the name. One local and one remote. The local one is created by the local branch git extension.I can't explicitly specify to Jenkins to use the remote one because I use the pipeline plugin, and this checkout is made automatically to retrieve the Jenkinsfile. So, the git implementation takes the first one, which is generally the local branch which is not yet updated...{code:java}Revision marked = candidates.iterator().next();{code}h2. Logs{noformat}16:10:31 Multiple candidate revisions16:10:31 Checking out Revision 604398f062b459c797f31d6c13b568dd7612362d (features/my-feature-branch)16:10:31 > git.exe config core.sparsecheckout # timeout=3016:10:31 > git.exe checkout -f 604398f062b459c797f31d6c13b568dd7612362d # timeout=12016:10:32 > git.exe branch -a -v --no-abbrev # timeout=3016:10:32 > git.exe branch -D features/my-feature-branch # timeout=3016:10:32 > git.exe checkout -b features/my-feature-branch 604398f062b459c797f31d6c13b568dd7612362d # timeout=12016:10:32 > git.exe rev-list 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d # timeout=30{noformat}h2. How to fix itPossibilities I see : * Update the workflow-multibranch-plugin to checkout on origin (prefix with refs/remotes/origin/) * Update the git-plugin to order the list, and prioritize remote branchesPersonally, I think the first one is safer, but I've not yet played with this plugin.h2. How to reproduce I # Create a new repository and initialize it (on github, with a README.md for example)# Clone it on your computer: git clone https://lausivoiduts.visualstudio.com/QuarahMC/_git/JENKINS-37263 ; cd JENKINS-37263# Create a new branch: git checkout -b features/this-bug# Add something in the Jenkinsfile: echo "echo ' first commit' " > Jenkinsfile# Commit and push it: git add Jenkinfile ; git commit - m working "first commit" ; git push --set-upstream origin features/this-bug# Add a new Multibranch Pipeline Project in Jenkins, add as Source your git repository. Click on an easy "Add Behaviour", select "Checkout to reproduce example a local branch" . I Set its value to "**" (without the quotes). Validate it.# Check that the branch was built, and the message "first commit"
[JIRA] (JENKINS-37263) Jenkins checkout the wrong commit when used with the local branch extension on a branch with a /
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37263 Jenkins checkout the wrong commit when used with the local branch extension on a branch with a / Change By: Quentin Dufour Summary: Jenkins checkout the wrong commit when used with the local branch extension on a branch with a / Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37263) Jenkins checkout the wrong commit when used with the local branch extension on a branch with a / (slash)
Title: Message Title
Quentin Dufour updated an issue
Jenkins / JENKINS-37263
Jenkins checkout the wrong commit when used with the local branch extension on a branch with a / (slash)
Change By:
Quentin Dufour
h2. Description of the problemI've a multibranch pipeline project configured with the local branch extension and many branch following the git flow model (features/) . Sometimes, when When I push a commit (ex: b) on the feature branch , this commit is detected by Jenkins, and pull pulled by the master to read the Jenkinsfile. After The first time it works, but after that, the slave has to pull local branch is selected instead of the repository (using checkout scm) remote branch , but sometimes it checkout to amd the wrong commit (previous one, let's say a instead of b) new commits are not fetch . The bug only occurs on branches with a slash in their names. h2. InvestigationI've connected my debugger to my Jenkins installation. !jenkins-local-branch-bug-1.PNG|thumbnail! It appears that Jenkins has detected 2 branches matching the name. One local and one remote. The local one is created by the local branch git extension.I can't explicitly specify to Jenkins to use the remote one because I use the pipeline plugin, and this checkout is made automatically to retrieve the Jenkinsfile. So, the git implementation takes the first one, which is generally the local branch which is not yet updated...{code:java}Revision marked = candidates.iterator().next();{code}h2. Logs{noformat}16:10:31 Multiple candidate revisions16:10:31 Checking out Revision 604398f062b459c797f31d6c13b568dd7612362d (features/my-feature-branch)16:10:31 > git.exe config core.sparsecheckout # timeout=3016:10:31 > git.exe checkout -f 604398f062b459c797f31d6c13b568dd7612362d # timeout=12016:10:32 > git.exe branch -a -v --no-abbrev # timeout=3016:10:32 > git.exe branch -D features/my-feature-branch # timeout=3016:10:32 > git.exe checkout -b features/my-feature-branch 604398f062b459c797f31d6c13b568dd7612362d # timeout=12016:10:32 > git.exe rev-list 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d # timeout=30{noformat}h2. How to fix itPossibilities I see : * Update the workflow-multibranch-plugin to checkout on origin (prefix with refs/remotes/origin/) * Update the git-plugin to order the list, and prioritize remote branchesPersonally, I think the first one is safer, but I've not yet played with this plugin.h2. How to reproduceI'm working on an easy to reproduce example. I'll update this post when I've found it.
[JIRA] (JENKINS-37263) Jenkins checkout the wrong commit when used with the local branch extension on a branch with a / (slash)
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37263 Jenkins checkout the wrong commit when used with the local branch extension on a branch with a / (slash) Change By: Quentin Dufour Summary: Jenkins checkout the wrong commit when used with the local branch extension on a branch with a / (slash) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36502) compatibility with snippet generator
Title: Message Title Daniel Spilker commented on JENKINS-36502 Re: compatibility with snippet generator New PR: https://github.com/jenkinsci/job-dsl-plugin/pull/893 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37263) Jenkins checkout the wrong commit when used with the local branch extension
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37263 Jenkins checkout the wrong commit when used with the local branch extension Change By: Quentin Dufour Summary: Jenkins checkout to the wrong commit when used with the local branch extension Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37263) checkout to the wrong commit when used with local branch
Title: Message Title
Quentin Dufour updated an issue
Jenkins / JENKINS-37263
checkout to the wrong commit when used with local branch
Change By:
Quentin Dufour
h2. Description of the problemI've a multibranch pipeline project configured with the local branch extension . Sometimes, when I push a commit (ex: b), this commit is detected by Jenkins, and pull by the master to read the Jenkinsfile. After that, the slave has to pull the repository (using checkout scm), but sometimes it checkout to the wrong commit (previous one, let's say a instead of b).h2. InvestigationI've connected my debugger to my Jenkins installation. !jenkins-local-branch-bug-1.PNG|thumbnail! It appears that Jenkins has detected 2 branches matching the name. One local and one remote. The local one is created by the local branch git extension. I can't explicitly specify to Jenkins to use the re remote one because I use the pipeline plugin, and this checkout is made automatically to retrieve the Jenkinsfile. So, the git implementation takes the first one, which is generally the local branch which is not yet updated... {code:java}Revision marked = candidates.iterator().next();{code} h2. Logs{noformat}16:10:31 Multiple candidate revisions16:10:31 Checking out Revision 604398f062b459c797f31d6c13b568dd7612362d (features/my-feature-branch)16:10:31 > git.exe config core.sparsecheckout # timeout=3016:10:31 > git.exe checkout -f 604398f062b459c797f31d6c13b568dd7612362d # timeout=12016:10:32 > git.exe branch -a -v --no-abbrev # timeout=3016:10:32 > git.exe branch -D features/my-feature-branch # timeout=3016:10:32 > git.exe checkout -b features/my-feature-branch 604398f062b459c797f31d6c13b568dd7612362d # timeout=12016:10:32 > git.exe rev-list 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d # timeout=30{noformat} h2. How to reproduce fix it Possibilities I see : * Update the workflow - multibranch - Not plugin to checkout on origin (prefix with refs/remotes/origin/) * Update the git-plugin to order the list, and prioritize remote branchesPersonally, I think the first one is safer, but I've not yet found a way played with this plugin.h2. How to easily reproduce I'm working on an easy to reproduce example. I'll update this post when I've found it -- .
Add
[JIRA] (JENKINS-37312) BlueOcean "Failed to write numberOfFailingBranches" exception
Title: Message Title Jonathan del Strother updated an issue Jenkins / JENKINS-37312 BlueOcean "Failed to write numberOfFailingBranches" exception Change By: Jonathan del Strother I created a multibranch pipeline job. Now, when I visit /blue/pipelines, the page says "No pipelines found". The _javascript_ console shows a failing request to /blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject, which returns the following error: ``` java.io.IOException: Failed to write numberOfFailingBranches at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151) at org.kohsuke.stapler.export.Property.writeTo(Property.java:126) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeTo(Model.java:198) at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:273) at hudson.model.Api.doJson(Api.java:211) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:55) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69) at org.kohsuke.stapler.Function.renderResponse(Function.java:119) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:102) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:249) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at
[JIRA] (JENKINS-37312) BlueOcean "Failed to write numberOfFailingBranches" exception
Title: Message Title Jonathan del Strother created an issue Jenkins / JENKINS-37312 BlueOcean "Failed to write numberOfFailingBranches" exception Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Aug/10 2:54 PM Priority: Critical Reporter: Jonathan del Strother I created a multibranch pipeline job. Now, when I visit /blue/pipelines, the page says "No pipelines found". The _javascript_ console shows a failing request to /blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject, which returns the following error: ``` java.io.IOException: Failed to write numberOfFailingBranches at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151) at org.kohsuke.stapler.export.Property.writeTo(Property.java:126) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeTo(Model.java:198) at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:273) at hudson.model.Api.doJson(Api.java:211) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:55) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69) at org.kohsuke.stapler.Function.renderResponse(Function.java:119) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:102) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at
[JIRA] (JENKINS-37263) checkout to the wrong commit when used with local branch
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37263 checkout to the wrong commit when used with local branch Change By: Quentin Dufour Component/s: workflow-multibranch-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37263) checkout to the wrong commit when used with local branch
Title: Message Title
Quentin Dufour updated an issue
Jenkins / JENKINS-37263
checkout to the wrong commit when used with local branch
Change By:
Quentin Dufour
h2. Description of the problemI've a multibranch pipeline project. Sometimes, when I push a commit (ex: b), this commit is detected by Jenkins, and pull by the master to read the Jenkinsfile. After that, the slave has to pull the repository (using checkout scm), but sometimes it checkout to the wrong commit (previous one, let's say a instead of b).h2. Jenkinsfile Investigation {code:java}node( I ' build') { checkout scm}{code} h2. Logs{noformat}Started by user anonymousSetting origin to https:// ve connected my -server.com/repo.gitFetching origin... > git.exe rev-parse --is-inside-work-tree # timeout=30Fetching changes from the remote Git repository > git.exe config remote.origin.url https://my-server.com/repo.git # timeout=30Cleaning workspace > git.exe rev-parse --verify HEAD # timeout=30Resetting working tree > git.exe reset --hard # timeout=30 > git.exe clean -fdx # timeout=30Fetching upstream changes from https://my-server.com/repo.git > git.exe --version # timeout=30using .gitcredentials debugger to set credentials > git.exe config --local credential.username MyUsername # timeout=30 > git.exe config --local credential.helper store --file=\"C:\Users\Someone\AppData\Local\Temp\git3518615989109492530.credentials\" # timeout=30 > git.exe -c core.askpass=true fetch --tags --progress https:// my -server Jenkins installation . com/repo.git +refs/heads/*:refs/remotes/origin/* # timeout=120 > git.exe config !jenkins - - local - -remove-section credential # timeout=30 > git.exe rev-parse "features/my-feature- branch ^{commit}" # timeout=30 > git.exe rev - parse "refs/remotes/origin/features/my bug - feature-branch^{commit}" # timeout=30Checking out Revision 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d (features/my-feature-branch) > git 1 . exe config core.sparsecheckout # timeout=30 PNG|thumbnail!> git.exe checkout -f 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d # timeout=120 > git.exe branch -a -v --no-abbrev # timeout=30 > git.exe branch -D features/my-feature-branch # timeout=30 > git.exe checkout -b features/my-feature-branch 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d # timeout=120 > git.exe rev-list 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d # timeout=30[Pipeline] timestamps[Pipeline] {[Pipeline] stage (Commit)16:10:21 Entering stage Commit16:10:21 Proceeding[Pipeline] node16:10:21 Running on commit02 in D:\agent\workspace\b\076b57f2[Pipeline] {[Pipeline] ws16:10:21 Running in D:\agent\build[Pipeline] {[Pipeline] checkout16:10:27 > git.exe rev-parse --is-inside-work-tree # timeout=3016:10:28 Fetching changes from It appears that Jenkins has detected 2 branches matching the remote Git repository16:10:28 > git name . exe config One local and one remote. origin.url https://my-server.com/repo.git # timeout=30 16:10:28 Cleaning workspace16:10:28 > git.exe rev-parse --verify HEAD # timeout=3016:10:28 Resetting
[JIRA] (JENKINS-37263) checkout to the wrong commit when used with local branch
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37263 checkout to the wrong commit when used with local branch Change By: Quentin Dufour Attachment: jenkins-local-branch-bug-1.PNG Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37263) checkout to the wrong commit when used with local branch
Title: Message Title
Quentin Dufour updated an issue
Jenkins / JENKINS-37263
checkout to the wrong commit when used with local branch
Change By:
Quentin Dufour
h2. Description of the problemI've a multibranch pipeline project. Sometimes, when I push a commit (ex: b), this commit is detected by Jenkins, and pull by the master to read the Jenkinsfile. After that, the slave has to pull the repository (using checkout scm), but sometimes it checkout to the wrong commit (previous one, let's say a instead of b).h2. Jenkinsfile{code:java}node('build') { checkout scm}{code} h2. Logs{noformat}Started by user anonymousSetting origin to https://my-server.com/repo.gitFetching origin... > git.exe rev-parse --is-inside-work-tree # timeout=30Fetching changes from the remote Git repository > git.exe config remote.origin.url https://my-server.com/repo.git # timeout=30Cleaning workspace > git.exe rev-parse --verify HEAD # timeout=30Resetting working tree > git.exe reset --hard # timeout=30 > git.exe clean -fdx # timeout=30Fetching upstream changes from https://my-server.com/repo.git > git.exe --version # timeout=30using .gitcredentials to set credentials > git.exe config --local credential.username MyUsername # timeout=30 > git.exe config --local credential.helper store --file=\"C:\Users\Someone\AppData\Local\Temp\git3518615989109492530.credentials\" # timeout=30 > git.exe -c core.askpass=true fetch --tags --progress https://my-server.com/repo.git +refs/heads/*:refs/remotes/origin/* # timeout=120 > git.exe config --local --remove-section credential # timeout=30 > git.exe rev-parse "features/my-feature-branch^{commit}" # timeout=30 > git.exe rev-parse "refs/remotes/origin/features/my-feature-branch^{commit}" # timeout=30Checking out Revision 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d (features/my-feature-branch) > git.exe config core.sparsecheckout # timeout=30 > git.exe checkout -f 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d # timeout=120 > git.exe branch -a -v --no-abbrev # timeout=30 > git.exe branch -D features/my-feature-branch # timeout=30 > git.exe checkout -b features/my-feature-branch 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d # timeout=120 > git.exe rev-list 0fa6b0371aa1e77a35acdc9f82bb68bb2c32fb2d # timeout=30[Pipeline] timestamps[Pipeline] {[Pipeline] stage (Commit)16:10:21 Entering stage Commit16:10:21 Proceeding[Pipeline] node16:10:21 Running on commit02 in D:\agent\workspace\b\076b57f2[Pipeline] {[Pipeline] ws16:10:21 Running in D:\agent\build[Pipeline] {[Pipeline] checkout16:10:27 > git.exe rev-parse --is-inside-work-tree # timeout=3016:10:28 Fetching changes from the remote Git repository16:10:28 > git.exe config remote.origin.url https://my-server.com/repo.git # timeout=3016:10:28 Cleaning workspace16:10:28 > git.exe rev-parse --verify HEAD # timeout=3016:10:28 Resetting working tree16:10:28 > git.exe reset --hard # timeout=3016:10:28 > git.exe clean -fdx # timeout=3016:10:28 Fetching upstream changes from https://my-server.com/repo.git16:10:28 > git.exe --version #
[JIRA] (JENKINS-37263) checkout to the wrong commit when used with local branch
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37263 checkout to the wrong commit when used with local branch Change By: Quentin Dufour Labels: git multibranch Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37263) checkout to the wrong commit when used with local branch
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37263 checkout to the wrong commit when used with local branch Change By: Quentin Dufour Component/s: git-plugin Component/s: workflow-multibranch-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
