[JIRA] (JENKINS-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Eli White commented on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection When you say pipeline libraries, do you mean repos that contain groovy scripts for use in pipeline? Repos that use pipeline to run their tests? Or something else? It would not seem like a reasonable assumption that repos that use pipeline to run their tests would be small repositories. Just making sure we are thinking the same thing here. 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 Eli White commented on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection If these checkouts on the build slaves could be done by doing a shallow clone with a specific refspec then the steps would take about 15 seconds down from 20 minutes. I'd be curious to know if that would work for others' use cases as well. 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-38362) Poll on a full clone on master, shallow clone using refspec on slaves
Title: Message Title Eli White commented on JENKINS-38362 Re: Poll on a full clone on master, shallow clone using refspec on slaves Thanks. We've been through those slides (and other documents on the web) that give ideas of how to speed this process up. The limited refspec approach doesn't work for us because we want to build everything except for master. Thus our refspec has to be a wildcard. The limited folders approach doesn't work for us because our repo isn't a mono repo. We need the entirety of the working directory I'm not super familiar with the reference repo approach, but I have some thoughts based on what I've read. We currently run our git server and our jenkins nodes on aws in the same region. We dynamically spin up our slaves and thus don't have an existing spot on disk for the reference repo to live local to the machine. A proxy cache doesn't really help us because it would still be a network access to another machine on AWS which we are already doing hitting our normal git server. Ideally we only have one full copy of the repo that can be used for figuring out what to build. The dynamically spun up slaves can then do a shallow clone with a refspec that contains a single branch. A shallow clone with a single refspec takes about 15 seconds for us. A shallow clone with all refspecs takes about 18 minutes. This plugin has the power to make builds way way faster. Especially when used in conjunction with the pipeline plugin which currently does 3 checkouts for every run 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
[JIRA] (JENKINS-38362) Poll on a full clone on master, shallow clone using refspec on slaves
Title: Message Title Eli White created an issue Jenkins / JENKINS-38362 Poll on a full clone on master, shallow clone using refspec on slaves Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin, git-plugin Created: 2016/Sep/20 1:25 AM Priority: Minor Reporter: Eli White We have a large git repo with lots of history and lots of branches. As of https://issues.jenkins-ci.org/browse/JENKINS-31393, we can now specify a refspec and have the initial fetch respect it. We have two jobs for each repo. One that builds master, and one that builds everything except master. Specifying a refspec works for our master job, but won't for the feature branches job since it needs to be able to fetch more than just the specified refspec. However, a shallow clone of all branches is too expensive and takes about 18 minutes to complete from inside the datacenter that contains our git repo. It seems like the ideal is for the master to have a full clone of our repo to be able to do polling and figure out what branch / revision to build, and then for it to tell a slave what revision to do a shallow checkout using a full refspec so it only checks out that one branch. Add Comment
[JIRA] (JENKINS-34140) Allow to specify node for load from SCM (Jenkinsfile)
Title: Message Title Eli White commented on JENKINS-34140 Re: Allow to specify node for load from SCM (Jenkinsfile) This seems similar to https://issues.jenkins-ci.org/browse/JENKINS-35710 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-35710) Option to not run pipeline flyweight executors on master
Title: Message Title Eli White updated an issue Jenkins / JENKINS-35710 Option to not run pipeline flyweight executors on master Change By: Eli White 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-35710) Option to not run pipeline flyweight executors on master
Title: Message Title Eli White created an issue Jenkins / JENKINS-35710 Option to not run pipeline flyweight executors on master Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Jun/15 12:14 AM Environment: Jenkins: 2.1 git-client-plugin: 1.19.6 Pipeline: SCM Step: 2.1 Priority: Minor Reporter: Eli White We don't want to run any user defined code on our master in order to make behavioral guarantees about the node. See the google groups discussion for more information: https://groups.google.com/forum/#!topic/jenkinsci-users/FRfL4RHAYnk We'd like to be able to set a specific label that can be used for running the flyweight executors Add Comment
[JIRA] (JENKINS-35686) Make multibranch jobs share workspace
Title: Message Title Eli White updated an issue Jenkins / JENKINS-35686 Make multibranch jobs share workspace Change By: Eli White Environment: Jenkins: 2.1 git-client-plugin: 1.19.6 Pipeline: SCM Step: 2.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-35686) Make multibranch pipeline jobs share workspace
Title: Message Title Eli White updated an issue Jenkins / JENKINS-35686 Make multibranch pipeline jobs share workspace Change By: Eli White Summary: Make multibranch pipeline jobs share workspace 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-35686) Make multibranch jobs share workspace
Title: Message Title Eli White created an issue Jenkins / JENKINS-35686 Make multibranch jobs share workspace Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Jun/14 12:28 AM Priority: Minor Reporter: Eli White We have a large repo (3+ gigs) and when using multibranch pipeline jobs, each branch gets its own workspace and is cloned fresh. We would like to have each of these branches share the same workspace (or @2, @3, etc if it is in use). Add Comment
[JIRA] [git-client-plugin] (JENKINS-35684) No option to set clone timeout for multi branch pipeline
Title: Message Title Eli White updated an issue Jenkins / JENKINS-35684 No option to set clone timeout for multi branch pipeline Change By: Eli White Labels: git-plugin workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-35684) No option to set clone timeout for multi branch pipeline
Title: Message Title Eli White created an issue Jenkins / JENKINS-35684 No option to set clone timeout for multi branch pipeline Issue Type: Bug Assignee: Mark Waite Attachments: Screen Shot 2016-06-13 at 3.21.17 PM.png Components: git-client-plugin, workflow-multibranch-plugin Created: 2016/Jun/13 10:25 PM Environment: Jenkins: 2.1 git-client-plugin: 1.19.6 Pipeline: SCM Step: 2.1 Priority: Minor Reporter: Eli White With my single branch pipeline builds and freestyle builds, I'm able to set clone and checkout timeouts on my SCM source. With a multi branch pipeline job, that option isn't available. See the screenshot for more info
