[JIRA] (JENKINS-11889) Suspended slave do not start accepting tasks when policy changed
Title: Message Title Petr Barton commented on JENKINS-11889 Re: Suspended slave do not start accepting tasks when policy changed This issue is also in Jenkins ver. 2.32.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-11889) Suspended slave do not start accepting tasks when policy changed
Title: Message Title Petr Barton edited a comment on JENKINS-11889 Re: Suspended slave do not start accepting tasks when policy changed This issue is also in _Jenkins ver. 2.32. 1_ 1 LTS_ 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-38484) Using test stability publisher in a Pipeline build will hang
Title: Message Title Sean Flanigan assigned an issue to Unassigned Jenkins / JENKINS-38484 Using test stability publisher in a Pipeline build will hang Change By: Sean Flanigan Assignee: Sean Flanigan 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-41418) Permission denied while accessing workspace
Title: Message Title
Manjunath Kumatagi edited a comment on JENKINS-41418
Re: Permission denied while accessing workspace
Removed the secret volume and ran the job, hitting with the problem mentioned in the description, "Build a Maven project" stage is failing. Here is the complete build console output:{code:java}Started by user admin > git rev-parse --is-inside-work-tree # timeout=10Setting origin to g...@github.ibm.com:mkumatag/test-kube-pipeline.git > git config remote.origin.url g...@github.ibm.com:mkumatag/test-kube-pipeline.git # timeout=10Fetching origin...Fetching upstream changes from origin > git --version # timeout=10using GIT_SSH to set credentials > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*Seen branch in repository origin/masterSeen 1 remote branch > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url g...@github.ibm.com:mkumatag/test-kube-pipeline.git # timeout=10Fetching upstream changes from g...@github.ibm.com:mkumatag/test-kube-pipeline.git > git --version # timeout=10using GIT_SSH to set credentials > git fetch --tags --progress g...@github.ibm.com:mkumatag/test-kube-pipeline.git +refs/heads/*:refs/remotes/origin/*Checking out Revision 916212bda350d9ea81c1419c2501f5177e396a8b (master) > git config core.sparsecheckout # timeout=10 > git checkout -f 916212bda350d9ea81c1419c2501f5177e396a8b > git rev-list 916212bda350d9ea81c1419c2501f5177e396a8b # timeout=10[Pipeline] podTemplate[Pipeline] {[Pipeline] nodeRunning on kubernetes-3f499c55e0fb4feea46c66e78e82ded3-70682873cd6d3 in /home/jenkins/workspace/test-kube-pipeline_master-IUIW3TJVYLQLCZOGWHIM6BOJZ3VXUBKJ2C2L4YNTBE4GL52NRMEA[Pipeline] {[Pipeline] stage (Get a Maven project)Using the ‘stage’ step without a block argument is deprecatedEntering stage Get a Maven projectProceeding[Pipeline] gitCloning the remote Git repositoryCloning repository https://github.com/jenkinsci/kubernetes-plugin.git > git init /home/jenkins/workspace/test-kube-pipeline_master-IUIW3TJVYLQLCZOGWHIM6BOJZ3VXUBKJ2C2L4YNTBE4GL52NRMEA # timeout=10Fetching upstream changes from https://github.com/jenkinsci/kubernetes-plugin.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/jenkinsci/kubernetes-plugin.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://github.com/jenkinsci/kubernetes-plugin.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/jenkinsci/kubernetes-plugin.git # timeout=10Fetching upstream changes from https://github.com/jenkinsci/kubernetes-plugin.git > git fetch --tags --progress https://github.com/jenkinsci/kubernetes-plugin.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10Checking out Revision 8078e125c4e2241814ce70a129b8fb7ab4abe81a (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 8078e125c4e2241814ce70a129b8fb7ab4abe81a > git branch -a -v --no-abbrev # timeout=10 > git checkout -b master 8078e125c4e2241814ce70a129b8fb7ab4abe81a > git rev-list 8078e125c4e2241814ce70a129b8fb7ab4abe81a # timeout=10[Pipeline] container[Pipeline] {[Pipeline] stage (Build a Maven project)Using the ‘stage’ step without a block argument is deprecatedEntering stage Build a Maven projectProceeding[Pipeline] sh[test-kube-pipeline_master-IUIW3TJVYLQLCZOGWHIM6BOJZ3VXUBKJ2C2L4YNTBE4GL52NRMEA] Running shell scriptExecuting shell script inside container [maven] of pod
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title
Manjunath Kumatagi commented on JENKINS-41418
Re: Permission denied while accessing workspace
Removed the secret volume and ran the job, hitting with the problem mentioned in the description, "Build a Maven project" stage is failing. Here is the complete build console output:
Started by user admin
> git rev-parse --is-inside-work-tree # timeout=10
Setting origin to g...@github.ibm.com:mkumatag/test-kube-pipeline.git
> git config remote.origin.url g...@github.ibm.com:mkumatag/test-kube-pipeline.git # timeout=10
Fetching origin...
Fetching upstream changes from origin
> git --version # timeout=10
using GIT_SSH to set credentials
> git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
Seen branch in repository origin/master
Seen 1 remote branch
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@github.ibm.com:mkumatag/test-kube-pipeline.git # timeout=10
Fetching upstream changes from g...@github.ibm.com:mkumatag/test-kube-pipeline.git
> git --version # timeout=10
using GIT_SSH to set credentials
> git fetch --tags --progress g...@github.ibm.com:mkumatag/test-kube-pipeline.git +refs/heads/*:refs/remotes/origin/*
Checking out Revision 916212bda350d9ea81c1419c2501f5177e396a8b (master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 916212bda350d9ea81c1419c2501f5177e396a8b
> git rev-list 916212bda350d9ea81c1419c2501f5177e396a8b # timeout=10
[Pipeline] podTemplate
[Pipeline] {
[Pipeline] node
Running on kubernetes-3f499c55e0fb4feea46c66e78e82ded3-70682873cd6d3 in /home/jenkins/workspace/test-kube-pipeline_master-IUIW3TJVYLQLCZOGWHIM6BOJZ3VXUBKJ2C2L4YNTBE4GL52NRMEA
[Pipeline] {
[Pipeline] stage (Get a Maven project)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Get a Maven project
Proceeding
[Pipeline] git
Cloning the remote Git repository
Cloning repository https://github.com/jenkinsci/kubernetes-plugin.git
> git init /home/jenkins/workspace/test-kube-pipeline_master-IUIW3TJVYLQLCZOGWHIM6BOJZ3VXUBKJ2C2L4YNTBE4GL52NRMEA # timeout=10
Fetching upstream changes from https://github.com/jenkinsci/kubernetes-plugin.git
> git --version # timeout=10
> git fetch --tags --progress https://github.com/jenkinsci/kubernetes-plugin.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url https://github.com/jenkinsci/kubernetes-plugin.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://github.com/jenkinsci/kubernetes-plugin.git # timeout=10
Fetching upstream changes from https://github.com/jenkinsci/kubernetes-plugin.git
> git fetch --tags --progress https://github.com/jenkinsci/kubernetes-plugin.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 8078e125c4e2241814ce70a129b8fb7ab4abe81a (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 8078e125c4e2241814ce70a129b8fb7ab4abe81a
> git branch -a -v --no-abbrev # timeout=10
> git checkout -b master 8078e125c4e2241814ce70a129b8fb7ab4abe81a
> git rev-list 8078e125c4e2241814ce70a129b8fb7ab4abe81a # timeout=10
[Pipeline] container
[Pipeline] {
[Pipeline] stage (Build a Maven project)
Using the ‘stage’ step without a block argument is
[JIRA] (JENKINS-41029) Promotions aren't copies when job generated with DSL
Title: Message Title Elad Shmitanka commented on JENKINS-41029 Re: Promotions aren't copies when job generated with DSL Seems that the issue is with the construction of the JobPropertyImpl in the jobDsl contect, the class is initiated and a call is made to setOwner which, in turn, runs loadChildren . Problem is, in this context, the root dir, is now the NEW job, not the old one, so, the class isn't initiated properly and thus, later, the List of processes is left empty. I think, that also, part of the problem, is that in no entry point between the jobDsl plugin code, to the promotion one, I have see any reference that passes the name of the template job, which makes it impossibly to load it from the right context. Solution would be either: pass dslItem on javaposse/jobdsl/plugin/JenkinsJobManagement.class:492 (or anywhere else before so, like, in the initialisation if the JobPropertyImpl Change the Promotion plugin to NOT use subfolders and have all the context in the original XML of the job
[JIRA] (JENKINS-41613) Escape key shortcut for closing result modal
Title: Message Title James Dumay commented on JENKINS-41613 Re: Escape key shortcut for closing result modal If you say 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-41613) Escape key shortcut for closing result modal
Title: Message Title James Dumay resolved as Fixed Jenkins / JENKINS-41613 Escape key shortcut for closing result modal Change By: James Dumay 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 unsubscribe from this group and stop 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-41615) Problem while checking for updates in Jenkins
Title: Message Title Gaurav Lele created an issue Jenkins / JENKINS-41615 Problem while checking for updates in Jenkins Issue Type: Bug Assignee: Gaurav Lele Components: jenkinslint-plugin Created: 2017/Feb/01 5:48 AM Environment: Jenkins 2.42, Ubuntu 14.04, JDK 1.8., JRE 1.8.1 Priority: Minor Reporter: Gaurav Lele I am trying to update my installed plugin in Jenkins, but i keep getting this error. Need a solution. Thank you java.io.IOException: Could not find JSON in http://updates.jenkins-ci.org/download/plugins/workflow-aggregator/?id=default=2.42 at hudson.model.DownloadService.loadJSON(DownloadService.java:178) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:190) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1628) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:108) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Stefan Walter commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials I would like to test this for you, because this is causing big issues for us. How can I install the snapshot? 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-41613) Escape key shortcut for closing result modal
Title: Message Title Josh McDonald commented on JENKINS-41613 Re: Escape key shortcut for closing result modal This is already implemented. 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-41610) Add a pull request template and contributing.md to pipeline-model-definition-plugin.git
Title: Message Title
dan tran updated an issue
Jenkins / JENKINS-41610
Add a pull request template and contributing.md to pipeline-model-definition-plugin.git
Change By:
dan tran
Comment:
in short, option to integrate with dir() {}details discussion is at https://groups.google.com/forum/#!topic/jenkinsci-users/GWZESWRCRw4
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-41610) Add a pull request template and contributing.md to pipeline-model-definition-plugin.git
Title: Message Title
dan tran commented on JENKINS-41610
Re: Add a pull request template and contributing.md to pipeline-model-definition-plugin.git
in short, option to integrate with dir() {} details discussion is at https://groups.google.com/forum/#!topic/jenkinsci-users/GWZESWRCRw4
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-41614) Ability to run DP under a current workspace's subfolder
Title: Message Title
dan tran updated an issue
Jenkins / JENKINS-41614
Ability to run DP under a current workspace's subfolder
Change By:
dan tran
in short, option to integrate with dir() {}details discussion is at https://groups.google.com/forum/#!topic/jenkinsci-users/GWZESWRCRw4
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-41614) Ability to run DP under a current workspace's subfolder
Title: Message Title dan tran created an issue Jenkins / JENKINS-41614 Ability to run DP under a current workspace's subfolder Issue Type: New Feature Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2017/Feb/01 5:34 AM Priority: Minor Reporter: dan tran Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed
[JIRA] (JENKINS-41334) Support parallel execution of stages in Declarative
Title: Message Title James Dumay commented on JENKINS-41334 Re: Support parallel execution of stages in Declarative Andrew Bayer BTW I have not forgotten about this. Will come back to it when I come up for air... 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-39864) Page should include build number and branch name
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39864 Page should include build number and branch name Change By: James Dumay Summary: Page < title > should include build number and branch name 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-39864) Page title should include build number and branch name
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39864
Page title should include build number and branch name
Change By:
James Dumay
*Scope** Update the {{}} of the page* Never show "undefined / undefined"** "Loading..." is good enough* Update the title text so that** Jenkins / path / to / Pipeline / master / #1234** Jenkins / path / to / Pipeline / PR-321 / #1234
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-39864) Page title should include build number and branch name
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39864 Page title should include build number and branch name Change By: James Dumay Now:Jenkins / (projectname) *Scope** Never show "undefined / undefined"** "Loading..." is good enough* Update the title text so that** Jenkins / (projectname) path / to / Pipeline / master / #1234** Jenkins / (projectname) path / to / Pipeline / PR-321 / #1234 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-41613) Escape key shortcut for closing result modal
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41613 Escape key shortcut for closing result modal Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/01 5:18 AM Priority: Minor Reporter: James Dumay Hitting escape key should close the result modal Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41408) Open Blue Ocean button is not working when jenkins home url is different
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41408 Open Blue Ocean button is not working when jenkins home url is different Change By: James Dumay Sprint: pannonian 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-41542) Run details changes
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41542 Run details changes Change By: Brody Maclean Need to make it look like the zeplin https://zpl.io/2ka0Kn* Font weight is incorrect for "Branch" and "Commit"** Lacks correct spacing as per mockup* Spacing between the Job name and run number is incorrect* Spacing / alignment between Branch/Commit labels & span* Spacing between icons & spans* Alignment of "branch" row and "commit" row * Always have to show “Commit: foo", either "Commit: ce87d64" or "Commit: N/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-41613) Escape key shortcut for closing result modal
Title: Message Title James Dumay assigned an issue to Josh McDonald Jenkins / JENKINS-41613 Escape key shortcut for closing result modal Change By: James Dumay Priority: Minor Major Assignee: Josh McDonald 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-41408) Open Blue Ocean button is not working when jenkins home url is different
Title: Message Title James Dumay resolved as Not A Defect Jenkins / JENKINS-41408 Open Blue Ocean button is not working when jenkins home url is different Change By: James Dumay Status: In Progress Resolved Resolution: Not A Defect 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-41542) Run details changes
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41542 Run details changes Change By: Brody Maclean Attachment: Pasted_Image_1_2_17__3_46_pm.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-41542) Run details changes
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41542 Run details changes Change By: Brody Maclean Need to make it look like the zeplin https://zpl.io/2ka0Kn* Font weight is incorrect for "Branch" and "Commit"** Lacks correct spacing as per mockup* Spacing between the Job name and run number is incorrect* Spacing / alignment between Branch/Commit labels & span * Spacing between icons & spans* Alignment of "branch" row and "commit" row 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-41542) Run details changes
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41542 Run details changes Change By: Brody Maclean Need to make it look like the zeplin https://zpl.io/2ka0Kn* Font weight is incorrect for "Branch" and "Commit"** Lacks correct spacing as per mockup* Spacing between the Job name and run number is incorrect * Spacing between 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-36536) Trend graph on pipeline project page
Title: Message Title Martin Heinzerling edited a comment on JENKINS-36536 Re: Trend graph on pipeline project page [~lorebett], it is just integrated into master, but not released yet. I can't tell you the a release date. 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-41587) Multijob : Phase job blocks if MultiJob parent comes in the queue
Title: Message Title Gaurav Joshi updated an issue Jenkins / JENKINS-41587 Multijob : Phase job blocks if MultiJob parent comes in the queue Change By: Gaurav Joshi 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-36536) Trend graph on pipeline project page
Title: Message Title Martin Heinzerling commented on JENKINS-36536 Re: Trend graph on pipeline project page Lorenzo Bettini, it is just integrated into master, but not released yet. I can't tell you the release date. 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-41608) Older or Unreadable Data warning after taking scm-api plugin update
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-41608 Older or Unreadable Data warning after taking scm-api plugin update Change By: Karl Shultz Priority: Major Minor 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-41608) Older or Unreadable Data warning after taking scm-api plugin update
Title: Message Title Karl Shultz commented on JENKINS-41608 Re: Older or Unreadable Data warning after taking scm-api plugin update There aren't any functional problems apparent yet, even though I haven't removed this unreadable data. So I'm bumping down the Priority of this bug one level. 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-41608) Older or Unreadable Data warning after taking scm-api plugin update
Title: Message Title Karl Shultz commented on JENKINS-41608 Re: Older or Unreadable Data warning after taking scm-api plugin update Confirmed after a second attempt to recreate. 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-38484) Using test stability publisher in a Pipeline build will hang
Title: Message Title Sean Flanigan assigned an issue to Sean Flanigan Jenkins / JENKINS-38484 Using test stability publisher in a Pipeline build will hang Change By: Sean Flanigan Assignee: kutzi Sean Flanigan 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-33168) Junit plugin took 7 hours to complete recording test failures
Title: Message Title Sean Flanigan updated an issue Jenkins / JENKINS-33168 Junit plugin took 7 hours to complete recording test failures Change By: Sean Flanigan Component/s: test-stability-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-38850) Multijob runs one parameterized child job instead of running multiple child jobs with different parameters
Title: Message Title Victor Ott commented on JENKINS-38850 Re: Multijob runs one parameterized child job instead of running multiple child jobs with different parameters I've created a pull request, containing a test reproducing the issue: https://github.com/jenkinsci/tikal-multijob-plugin/pull/106 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-31779) javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report
Title: Message Title Sean Flanigan commented on JENKINS-31779 Re: javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report Seems like it might be a duplicate. 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-39864) Page title should include build number and branch name
Title: Message Title Michael Neale commented on JENKINS-39864 Re: Page title should include build number and branch name Is this page title as in or somewhere else at the top of the screen? If the former, I clearly need a bigger monitor to even see titles. 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-40131) "Re-run" button text needs to be translated
Title: Message Title Michael Neale assigned an issue to Michael Neale Jenkins / JENKINS-40131 "Re-run" button text needs to be translated Change By: Michael Neale Assignee: Thorsten Scherler Michael Neale 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-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Victor Ott updated an issue Jenkins / JENKINS-32167 ISVNAuthentication provider did not provide credentials Change By: Victor Ott Environment: Windows 7; Jenkins 1.617 with Subversion Plug-in 2.5.5Windows Server 2012 R2; Jenkins 2.19.3 with Subversion plugin 2.7.1 Linux x86_64, Jenkins 2.19.4 with Subversion Plugin 2.7.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-41612) Job DSL plugin does not function on Windows agents
Title: Message Title
Ben Hines created an issue
Jenkins / JENKINS-41612
Job DSL plugin does not function on Windows agents
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2017/Feb/01 1:09 AM
Priority:
Critical
Reporter:
Ben Hines
Latest version of the job dsl plugin fails on Windows, 100%. ERROR: invalid script name 'Z:\export\jenkins\workspace\test_generate_jenkins_jobs\dev\dev.dsl; script names may only contain letters, digits and underscores, but may not start with a digit The same exact job name works on Linux. The job-dsl plugin is presumably using the full pathname to the workspace to create the class which has a colon in it on windows. Our config looks like: {{ dsl/*.dsl false false false false false DELETE DELETE JENKINS_ROOT }}
Add Comment
[JIRA] (JENKINS-40285) global libraries test harness
Title: Message Title Mike Kobit commented on JENKINS-40285 Re: global libraries test harness I'd like to see some guidance on this, too. We use Bitbucket Branch Source Plugin almost exclusively, so anything geared towards testing libraries this way would be great. I opened a discussion on the forum about this previously, but didn't really get a hugely satisfactory answer. Being able to test these libraries would be an awesome addition. 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-41611) Pipeline Editor Node Designs
Title: Message Title Brody Maclean created an issue Jenkins / JENKINS-41611 Pipeline Editor Node Designs Issue Type: Story Assignee: Keith Zantow Components: blueocean-plugin Created: 2017/Feb/01 12:51 AM Priority: Minor Reporter: Brody Maclean UI & interaction design for nodes http://codepen.io/brody/pen/JEMGWz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title Travis King commented on JENKINS-41572 Re: ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Where do I find the config.xml? Usually I work with Linux systems, this is my first time working with a Windows system. To be honest, that's one reason I am not knowledgeable of what's going on. 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-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title Oleg Nenashev commented on JENKINS-41572 Re: ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins I need a config.xml file for the slave you're trying to connect. Just as a first step of triangulation 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-32839) "Result too large" error while applying configuration changes...
Title: Message Title Oleg Nenashev commented on JENKINS-32839 Re: "Result too large" error while applying configuration changes... Passing to the core for triangulation. BTW I doubt we can do anything without a screenshot of job 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-32839) "Result too large" error while applying configuration changes...
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-32839 "Result too large" error while applying configuration changes... Change By: Oleg Nenashev Component/s: core Component/s: _unsorted 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-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title Travis King commented on JENKINS-41572 Re: ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Can you be more specific as far as your configuration question? 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-37053) Jenkins Slave Agent Dies everyday at the same time
Title: Message Title Oleg Nenashev commented on JENKINS-37053 Re: Jenkins Slave Agent Dies everyday at the same time There is no data to diagnose the issue. Blindly closing it as a duplicate of JENKINS-28492, which is also a wide issue without clear scope 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-37053) Jenkins Slave Agent Dies everyday at the same time
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-37053 Jenkins Slave Agent Dies everyday at the same time Change By: Oleg Nenashev Component/s: remoting Component/s: _unsorted 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-37053) Jenkins Slave Agent Dies everyday at the same time
Title: Message Title Oleg Nenashev resolved as Duplicate Jenkins / JENKINS-37053 Jenkins Slave Agent Dies everyday at the same time Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate 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-38263) (SOAPUI- Jenkins Integration) Build just keeps on running...with no outcome
Title: Message Title Oleg Nenashev resolved as Not A Defect Jenkins / JENKINS-38263 (SOAPUI- Jenkins Integration) Build just keeps on running...with no outcome Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect 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-38263) (SOAPUI- Jenkins Integration) Build just keeps on running...with no outcome
Title: Message Title Oleg Nenashev commented on JENKINS-38263 Re: (SOAPUI- Jenkins Integration) Build just keeps on running...with no outcome It was not a Bug, hence it did not appear in my filters. The log explicitly says that Soap UI class was unable to load the logger class due to whatever reason. Maybe you try to include slf4j logger into log4j? I doubt it's something operational. Not a defect in Jenkins anyway. 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-37886) is it possible to send email notification from a pipeline
Title: Message Title Oleg Nenashev resolved as Not A Defect Jenkins / JENKINS-37886 is it possible to send email notification from a pipeline Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect 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-37886) is it possible to send email notification from a pipeline
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-37886 is it possible to send email notification from a pipeline Change By: Oleg Nenashev Component/s: pipeline Component/s: _unsorted 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-37886) is it possible to send email notification from a pipeline
Title: Message Title Oleg Nenashev commented on JENKINS-37886 Re: is it possible to send email notification from a pipeline Pipeline is not a pure Groovy. The context is being serialized to the disk on each step to make it survive over restarts. If it something really required for temporary needs, implement the code within a method with NonCPS annotation 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-40798) Cannot convert type LinkedHashSet to List
Title: Message Title Oleg Nenashev commented on JENKINS-40798 Re: Cannot convert type LinkedHashSet to List Ping 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-40592) Configuring SSH remote host for Mac slave isn't working
Title: Message Title Oleg Nenashev commented on JENKINS-40592 Re: Configuring SSH remote host for Mac slave isn't working Muhammad Zbeedat ping 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-41337) Jenkins Deploys all the projects irrespective of changed project
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-41337 Jenkins Deploys all the projects irrespective of changed project Change By: Oleg Nenashev Assignee: kdsweeney Oleg Nenashev 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-41337) Jenkins Deploys all the projects irrespective of changed project
Title: Message Title Oleg Nenashev commented on JENKINS-41337 Re: Jenkins Deploys all the projects irrespective of changed project Please provide your job configuration. Have you also noticed this text in help? https://github.com/jenkinsci/maven-plugin/blob/c10cfb4dc880964cf10d952ec4109fbe5a6eae56/src/main/webapp/incremental.html#L12-L13 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-41337) Jenkins Deploys all the projects irrespective of changed project
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-41337 Jenkins Deploys all the projects irrespective of changed project Change By: Oleg Nenashev Component/s: maven-plugin Component/s: subversion-plugin Component/s: _unsorted 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-41610) Add a pull request template and contributing.md to pipeline-model-definition-plugin.git
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-41610 Add a pull request template and contributing.md to pipeline-model-definition-plugin.git Issue Type: Task Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2017/Jan/31 11:56 PM Priority: Minor Reporter: Andrew Bayer Going forward, we should have a CONTRIBUTING.md and a PULL_REQUEST_TEMPLATE.md so that, well, contributors know what we're looking for and expecting in a PR. For example, I want to make sure every PR either has a link to a corresponding jenkins.io docs PR or an explanation of why a docs change isn't needed. Add Comment
[JIRA] (JENKINS-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title Oleg Nenashev commented on JENKINS-41572 Re: ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Please provide your Windows slave configuration. Likely your slave just cannot connect to the host/port 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-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-41572 ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Change By: Oleg Nenashev Issue Type: Task Bug 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-41572) ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-41572 ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Change By: Oleg Nenashev Component/s: windows-slaves-plugin Component/s: _unsorted 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-41609) Dockerfile reuseNode should default argument to true
Title: Message Title Andrew Bayer commented on JENKINS-41609 Re: Dockerfile reuseNode should default argument to true Yup. 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-41609) Dockerfile reuseNode should default argument to true
Title: Message Title Liam Newman commented on JENKINS-41609 Re: Dockerfile reuseNode should default argument to true So, that would take us back to JENKINS-40721. 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-27299) Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility
Title: Message Title Richard Lee commented on JENKINS-27299 Re: Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility Is this being actively worked on? There are a lot of votes for it, and it's really inconvenient that pipeline builds can't straightforwardly be temporarily disabled. 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-41609) Dockerfile reuseNode should default argument to true
Title: Message Title Andrew Bayer commented on JENKINS-41609 Re: Dockerfile reuseNode should default argument to true Yes, those are functionally equivalent. It's the no-args thing that makes things wonky. In general, anywhere where I can control the syntax entirely (i.e., not things containing steps, job properties, etc that have their syntax defined outside of Declarative), we go with "key value"-ish syntax. That doesn't work with a no-arg approach, and "key" doesn't work as a method without the parentheses. 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-41609) Dockerfile reuseNode should default argument to true
Title: Message Title Liam Newman commented on JENKINS-41609 Re: Dockerfile reuseNode should default argument to true Andrew Bayer In groovy: something else is functionally something(else), right? 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-41609) Dockerfile reuseNode should default argument to true
Title: Message Title Liam Newman commented on JENKINS-41609 Re: Dockerfile reuseNode should default argument to true Would this break the existing behavior? 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-41609) Dockerfile reuseNode should default argument to true
Title: Message Title Andrew Bayer commented on JENKINS-41609 Re: Dockerfile reuseNode should default argument to true ...though I'm gonna WONTFIX this too, because reuseNode() would be syntactically different than everything else in agent - it's always foo bar. 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-41609) Dockerfile reuseNode should default argument to true
Title: Message Title Andrew Bayer resolved as Not A Defect Nope, sorry. We already had this discussion when we added reuseNode - retaining existing behavior is more important. Jenkins / JENKINS-41609 Dockerfile reuseNode should default argument to true Change By: Andrew Bayer Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-41609) Dockerfile reuseNode should default argument to true
Title: Message Title Andrew Bayer reopened an issue whoops, misunderstood Jenkins / JENKINS-41609 Dockerfile reuseNode should default argument to true Change By: Andrew Bayer Resolution: Not A Defect Status: Resolved Reopened 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-41609) Dockerfile reuseNode should default argument to true
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-41609
Dockerfile reuseNode should default argument to true
Change By:
Liam Newman
Comment:
See JENKINS-41391. Same idea. {code}dockerfile {reuseNode()}{code}
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-41609) Dockerfile reuseNode should default argument to true
Title: Message Title
Liam Newman commented on JENKINS-41609
Re: Dockerfile reuseNode should default argument to true
See JENKINS-41391. Same idea.
dockerfile {
reuseNode()
}
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-41609) Dockerfile reuseNode should default argument to true
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-41609
Dockerfile reuseNode should default argument to true
Change By:
Liam Newman
See JENKINS-41391. Same idea. {code}dockerfile {reuseNode()}{code}
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-41609) Dockerfile reuseNode should default argument to true
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-41609 Dockerfile reuseNode should default argument to true Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2017/Jan/31 10:40 PM Priority: Minor Reporter: Liam Newman Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to
[JIRA] (JENKINS-41607) Declarative: agent dockerfile fails when agent inside stage
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-41607
Declarative: agent dockerfile fails when agent inside stage
Change By:
Liam Newman
In a project with a {{Dockerfile}}, This pipeline succeeds:{code:language=groovy}pipeline {agent {dockerfile true}stages {stage ('Build') {steps {sh 'echo "hello"'}}}}{code}This pipeline fails:{code:language=groovy}pipeline {agent anystages {stage ('Build') {agent {dockerfile true}steps {sh 'echo "hello"'}}}}{code}The reason this happens is that the agent inside a stage step does not do checkout scm automatically. This is very confusing behavior. Agent initialization should be consistent whether at top or inside a stage. The following also works, because of {{reuseNode true}}, but dockerfile would never work without that when inside a state (due to JENKINS-41605). {code:language=groovy}pipeline {agent anystages {stage ('Build') {agent {dockerfile {reuseNode true}}steps {sh 'echo "hello"'}}}}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41608) Older or Unreadable Data warning after taking scm-api plugin update
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-41608 Older or Unreadable Data warning after taking scm-api plugin update /var/log/jenkins/jenkins.log, and the job folder itself, are now attached. Change By: Karl Shultz Attachment: jenkins.log Attachment: 1--kshultzCB--org--folder.tar.gz 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
[JIRA] (JENKINS-41607) Declarative: agent dockerfile fails when agent inside stage
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-41607 Declarative: agent dockerfile fails when agent inside stage Change By: Liam Newman Summary: Declarative: agent dockerfile fails when agent inside stage with top-level agent none 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-41607) Declarative: agent dockerfile fails when agent inside stage
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-41607
Declarative: agent dockerfile fails when agent inside stage
Change By:
Liam Newman
In a project with a {{Dockerfile}}, This pipeline succeeds:{code:language=groovy}pipeline {agent {dockerfile true}stages {stage ('Build') {steps {sh 'echo "hello"'}}}}{code}This pipeline fails:{code:language=groovy}pipeline {agent none any stages {stage ('Build') {agent {dockerfile true}steps {sh 'echo "hello"'}}}}{code}The reason this happens is that the agent inside a stage step does not do checkout scm automatically. This is very confusing behavior. Agent initialization should be consistent whether at top or inside a stage.
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
[JIRA] (JENKINS-41608) Older or Unreadable Data warning after taking scm-api plugin update
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-41608 Older or Unreadable Data warning after taking scm-api plugin update Change By: Karl Shultz Attachment: support_2017-01-31_22.16.10.zip 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-41607) Declarative: agent dockerfile fails when agent inside stage with top-level agent none
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-41607 Declarative: agent dockerfile fails when agent inside stage with top-level agent none Change By: Andrew Bayer Summary: Declarative: agent dockerfile fails when agent inside stagewith top-level agent none 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-41605) Declarative: agent inside stage does not do automatic checkout scm
Title: Message Title R. Tyler Croy commented on JENKINS-41605 Re: Declarative: agent inside stage does not do automatic checkout scm Andrew Bayer, why would you still advocate for it? It's wholly inconsistent behavior between stage-level and pipeline-level agent directives. 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-41607) Declarative: agent dockerfile fails when agent inside stage
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-41607
Declarative: agent dockerfile fails when agent inside stage
Change By:
Liam Newman
In a project with a {{Dockerfile}}, This pipeline succeeds:{code:language=groovy}pipeline {agent {dockerfile true}stages {stage ('Build') {steps {sh 'echo "hello"'}}}}{code}This pipeline fails:{code:language=groovy}pipeline {agent nonestages {stage ('Build') {agent {dockerfile true}steps {sh 'echo "hello"'}}}}{code}The reason this happens is that the agent inside a stage step does not do checkout scm automatically. This is very confusing behavior. Agent initialization should be consistent whether at top or inside a stage.
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
[JIRA] (JENKINS-41608) Older or Unreadable Data warning after taking scm-api plugin update
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-41608 Older or Unreadable Data warning after taking scm-api plugin update Issue Type: Bug Assignee: Unassigned Attachments: image-2017-01-31-17-14-15-027.png Components: scm-api-plugin Created: 2017/Jan/31 10:14 PM Priority: Major Reporter: Karl Shultz Summary: After taking the supplied zip of scm-api plugins, and applying it over top of a previously known good Jenkins 2.42 instance, the warning "You have data stored in an older format and/or unreadable data" appears. Steps to reproduce: Set up Jenkins with a handful of Bitbucket and GitHub multibranch and organization jobs. Stop the Jenkins service entirely. Unzip the supplied scm-2.0.x-plugins.zip file on top of the /var/llib/jenkins/plugins directory Restart the Jenkins instance Sign on again Results: I will upload logs and everything else soon after getting this filed.
[JIRA] (JENKINS-41607) Declarative: agent dockerfile fails when agent inside stage
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-41607 Declarative: agent dockerfile fails when agent inside stage Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2017/Jan/31 10:11 PM Priority: Major Reporter: Liam Newman Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are
[JIRA] (JENKINS-40771) Pipeline causes job to hang infinitely on Jenkins restart
Title: Message Title
Hoshang Sadiq commented on JENKINS-40771
Re: Pipeline causes job to hang infinitely on Jenkins restart
Having a similar issue, in my case I'm backing up the jobs directory and restoring it before starting Jenkins:
[Pipeline] {
[Pipeline] sh
[jenkins-backup] Running shell script
+ mktemp jenkins-jobs-XXX.tar.gz
[Pipeline] stage
[Pipeline] { (Backup build history)
[Pipeline] sh
Resuming build at Tue Jan 31 16:40:33 GMT 2017 after Jenkins restart
Waiting to resume Unknown Pipeline node step: ???
[jenkins-backup] Running shell script
Ready to run at Tue Jan 31 16:40:36 GMT 2017
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-41605) Declarative: agent inside stage does not do automatic checkout scm
Title: Message Title Andrew Bayer commented on JENKINS-41605 Re: Declarative: agent inside stage does not do automatic checkout scm The reasoning behind automatic checkout only happening at the top level was a conscious decision - and frankly, one I'd still advocate for. But it may make sense to have a per-stage option for "do a fresh checkout of SCM in this stage" - independent of the agent configuration. There've been some other things that have come up that may make sense as part of a stage-level options section. 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-41606) Master SEGV caused by com.trilead.ssh2.crypto w/ java-1.8.0_102-b14
Title: Message Title
Patrick Facheris updated an issue
Jenkins / JENKINS-41606
Master SEGV caused by com.trilead.ssh2.crypto w/ java-1.8.0_102-b14
Change By:
Patrick Facheris
I've been experiencing crashes of the Jenkins master approximately once a month for the last several months. In every case, a core dump is generated that references "com.trilead.ssh2.crypto" and a similar message (dumps attached). I've been unable to reproduce with a simple installation as I'm struggling to track down any single activity that could be the cause. Let me know if a list of installed plugins would be helpful.{code}## A fatal error has been detected by the Java Runtime Environment:## SIGSEGV (0xb) at pc=0x7f02d76c7bf1, pid=19717, tid=0x7f0235a59700## JRE version: Java(TM) SE Runtime Environment (8.0_102-b14) (build 1.8.0_102-b14)# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.102-b14 mixed mode linux-amd64 compressed oops)# Problematic frame:# J 13231 C2 com.trilead.ssh2.crypto.digest.MD5.transform([BI)V (1563 bytes) @ 0x7f02d76c7bf1 [0x7f02d76c6e60+0xd91]## Core dump written. Default location: //core or core.19717## If you would like to submit a bug report, please visit:# http://bugreport.java.com/bugreport/crash.jsp#{code} {code:java}// Some comments herepublic String getFoo(){return foo;}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41606) Master SEGV caused by com.trilead.ssh2.crypto w/ java-1.8.0_102-b14
Title: Message Title Patrick Facheris created an issue Jenkins / JENKINS-41606 Master SEGV caused by com.trilead.ssh2.crypto w/ java-1.8.0_102-b14 Issue Type: Bug Assignee: Unassigned Attachments: hs_err_pid12575.log, hs_err_pid19717.log, hs_err_pid25060.log, hs_err_pid30561.log Components: core Created: 2017/Jan/31 9:52 PM Environment: Jenkins 2.7.4 installed via RPM Oracle JDK 1.8.0_102-b14 CentOS release 6.5 (Final) VM Priority: Major Reporter: Patrick Facheris I've been experiencing crashes of the Jenkins master approximately once a month for the last several months. In every case, a core dump is generated that references "com.trilead.ssh2.crypto" and a similar message (dumps attached). I've been unable to reproduce with a simple installation as I'm struggling to track down any single activity that could be the cause. Let me know if a list of installed plugins would be helpful. # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f02d76c7bf1, pid=19717, tid=0x7f0235a59700 # # JRE version: Java(TM) SE Runtime Environment (8.0_102-b14) (build 1.8.0_102-b14) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.102-b14 mixed mode linux-amd64 compressed oops) # Problematic frame: # J 13231 C2 com.trilead.ssh2.crypto.digest.MD5.transform([BI)V (1563 bytes) @ 0x7f02d76c7bf1 [0x7f02d76c6e60+0xd91] # # Core dump written. Default
[JIRA] (JENKINS-41605) Declarative: agent inside stage does not do automatic checkout scm
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-41605
Declarative: agent inside stage does not do automatic checkout scm
Change By:
Liam Newman
This pipeline succeeds:{code:language=groovy}pipeline {agent anystages {stage ('Build') {steps {sh 'cat Jenkinsfile'}}}}{code}This pipeline fails:{code:language=groovy}pipeline {agent anystages {stage ('Build') {agent anysteps {sh 'cat Jenkinsfile'}}}}{code}The reason this happens is that the agent inside a stage step does not do checkout scm automatically. This is very confusing behavior. Agent initialization should be consistent whether at top or inside a stage. I would expect to do something like this to make an agent in a stage not do checkout:{code:language=groovy}pipeline {agent anyoptions {skipDefaultCheckout()}stages {stage ('Build') {agent anyoptions {skipDefaultCheckout()}steps {sh 'cat Jenkinsfile'}}}}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38752) The job link in the detail view for multibranch should link to a filtered activity list of appropriate branch
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38752 The job link in the detail view for multibranch should link to a filtered activity list of appropriate branch Change By: James Dumay Sprint: pannonian release candidate 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-38752) The job link in the detail view for multibranch should link to a filtered activity list of appropriate branch
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-38752
The job link in the detail view for multibranch should link to a filtered activity list of appropriate branch
Change By:
James Dumay
* In scope ** Clicking on the branch name in the header (bread crumb or "Branch: FOO") should take you to the activity tab filtered by the branch.*Original request* As pointed out by tyler, the link in the header for multibranch currently points to nothing sensible. The branch name is hyper linked, but it is linked to the overall pipelines activity tab, which is NOT specific to branch. It should be linked to the activity tab, as it is, but with a filter applied to only show the activity history for that branch or pull request (filtering is not yet available on that tab) Spake Tyler: On a PR build such as [this one|https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-2577/2/pipeline] the header breadcrumb navigation contains:{code}Jenkins / Core / PR-2577 #2{code}A click on "PR-2577" I would expect to take me to an overview page for that pull request but instead it takes me to [the overall repository "Activity" view|https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/activity]IMO either this link should take me to some place relevant to that pull request or not be linked at all.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38752) The job link in the detail view for multibranch should link to a filtered activity list of appropriate branch
Title: Message Title James Dumay assigned an issue to Ivan Meredith Jenkins / JENKINS-38752 The job link in the detail view for multibranch should link to a filtered activity list of appropriate branch Change By: James Dumay Assignee: James Dumay Ivan Meredith 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-41175) BlueOcean display URL is not working
Title: Message Title James Dumay resolved as Cannot Reproduce If you can't see this working with the latest plugins after a restart, please reopen this ticket and we will take a look again. I had another user mention that this was working for them with the latest set of plugin upgrades. Jenkins / JENKINS-41175 BlueOcean display URL is not working Change By: James Dumay Status: In Progress Resolved Resolution: Cannot Reproduce 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.
[JIRA] (JENKINS-41459) Loading never finishes on blue ocean dashboard when clicked show more button.
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41459 Loading never finishes on blue ocean dashboard when clicked show more button. Change By: James Dumay Component/s: blueocean-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-41459) Loading never finishes on blue ocean dashboard when clicked show more button.
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41459 Loading never finishes on blue ocean dashboard when clicked show more button. Change By: James Dumay Component/s: p4-plugin Component/s: blueocean-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-41605) Declarative: agent inside stage does not do automatic checkout scm
Title: Message Title
Liam Newman created an issue
Jenkins / JENKINS-41605
Declarative: agent inside stage does not do automatic checkout scm
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Jan/31 9:17 PM
Priority:
Major
Reporter:
Liam Newman
This pipeline succeeds:
pipeline {
agent any
stages {
stage ('Build') {
steps {
sh 'cat Jenkinsfile'
}
}
}
}
This pipeline fails:
pipeline {
agent any
stages {
stage ('Build') {
agent any
steps {
sh 'cat Jenkinsfile'
}
}
}
}
The reason this happens is that the agent inside a stage step does not do checkout scm automatically. This is very confusing behavior. Agent initialization should be consistent whether at top or inside a stage.
