[JIRA] (JENKINS-39750) scm should allow configuration in the Jenkinsfile

[docw...@gerf.org (JIRA)]

Title: Message Title

Christian Höltje created an issue   Jenkins / JENKINS-39750 scm should allow configuration in the Jenkinsfile Issue Type: New Feature Assignee: Mark Waite Components: git-plugin, github-branch-source-plugin Created: 2016/Nov/15 5:17 PM Labels: pipeline Priority: Major Reporter: Christian Höltje The GitHub Organization Folder plugin scans an Organization in GitHub and creates jobs for each repository's branches and PRs. Because it is automating the creation of so many jobs, it is unreasonable to pre-configure everything needed for checkout scm to work for all cases. I propose that we add an easy mechanism to configure the scm object in Jenkinsfile; allowing adding extensions like shallow clone, clean before/after checkout, submodules. In JENKINS-37658 Jesse Glick said this required an RFE. Using jobDSL isn't useful because all the behavior of GitHub Org Folders cannot be replicated (at least not without lots of glue). A workaround is do to something like this: checkout( [ $class: 'GitSCM', userRemoteConfigs: [[credentialsId: 'github-oauth-userpass', url: 'https://github.com/myorg/myrepository']], branches: [[name: '*/$BRANCH_NAME']], extensions: [ [$class: 'AuthorInChangelog'], [$class: 'CheckoutOption', timeout: 10], [$class: 'CleanBeforeCheckout'], [$class: 'CloneOption', depth: 3, honorRefspec: true, noTags: true, reference: '', shallow: true, timeout: 3] ] ] ) This is non-ideal because the user has to know the name of the proper credentials and because they have to hardcode the github repository URL. 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.