• Type: Improvement
• Resolution: Duplicate
• Priority: Major
• Component/s: subversion-plugin
• Labels:

  • multibranch
  • pipeline

[JENKINS-42957] Optimize Jenkinsfile loading instead of checking out all code on master

Jingliang Fu created issue - 2017-03-21 06:51

Jingliang Fu made changes - 2017-03-21 07:46

Description

Original: Currently, creating a pipeline and select "Pipeline script from SCM" and subversion as the code repository is subversion and we store our Jenkinsfile on svn. We may like to load Jenkinsfile only instead of checking all the repository (more than 15G) on master, the real "checkout" will be on master which is defined in Jenkinsfile. Not sure if there is any workaround, we could only store Jenkinsfile on svn and paste on Jenksin web UI now, too sad.   Thanks, Jingliang

New: Currently, creating a pipeline, select "Pipeline script from SCM" and subversion as the code repository. We may like to load Jenkinsfile only instead of check out all the svn repository (more than 15G) on master, the real "checkout" will be on slave node which is defined in Jenkinsfile. Not sure if there is any workaround, we could only store Jenkinsfile on svn and paste on Jenksin web UI now, too sad.   Thanks, Jingliang

Jingliang Fu made changes - 2017-03-21 07:47

Description

Original: Currently, creating a pipeline, select "Pipeline script from SCM" and subversion as the code repository. We may like to load Jenkinsfile only instead of check out all the svn repository (more than 15G) on master, the real "checkout" will be on slave node which is defined in Jenkinsfile. Not sure if there is any workaround, we could only store Jenkinsfile on svn and paste on Jenksin web UI now, too sad.   Thanks, Jingliang

New: Currently, creating a pipeline, select "Pipeline script from SCM" and subversion as the code repository. We may like to load Jenkinsfile only instead of checking out all the svn repository (more than 15G) on master, the real "checkout" will be on slave node which is defined in Jenkinsfile. Not sure if there is any workaround, we could only store Jenkinsfile on svn and paste on Jenksin web UI now, too sad.   Thanks, Jingliang

Jingliang Fu made changes - 2017-03-21 07:52

Description

Original: Currently, creating a pipeline, select "Pipeline script from SCM" and subversion as the code repository. We may like to load Jenkinsfile only instead of checking out all the svn repository (more than 15G) on master, the real "checkout" will be on slave node which is defined in Jenkinsfile. Not sure if there is any workaround, we could only store Jenkinsfile on svn and paste on Jenksin web UI now, too sad.   Thanks, Jingliang

New: Currently, create a pipeline, select "Pipeline script from SCM" and subversion as the code repository. We may like to load Jenkinsfile only instead of checking out all the svn repository (more than 15G) on master, the real "checkout" will be on slave node which is defined in Jenkinsfile. Not sure if there is any workaround, we could only store Jenkinsfile on svn and paste it on Jenkins web UI now, too sad :(   Thanks, Jingliang

Jingliang Fu made changes - 2017-03-21 07:52

Description

Original: Currently, create a pipeline, select "Pipeline script from SCM" and subversion as the code repository. We may like to load Jenkinsfile only instead of checking out all the svn repository (more than 15G) on master, the real "checkout" will be on slave node which is defined in Jenkinsfile. Not sure if there is any workaround, we could only store Jenkinsfile on svn and paste it on Jenkins web UI now, too sad :(   Thanks, Jingliang

New: Currently, create a pipeline, select "Pipeline script from SCM" and subversion as the code repository. We may like to load Jenkinsfile only instead of checking out all the svn repository (more than 15G) on master, the real "checkout" will be on slave node which is defined in Jenkinsfile. Not sure if there is any workaround? we could only store Jenkinsfile on svn and paste it on Jenkins web UI now, too sad :(   Thanks, Jingliang

Jingliang Fu made changes - 2017-03-21 07:53

Description

Original: Currently, create a pipeline, select "Pipeline script from SCM" and subversion as the code repository. We may like to load Jenkinsfile only instead of checking out all the svn repository (more than 15G) on master, the real "checkout" will be on slave node which is defined in Jenkinsfile. Not sure if there is any workaround? we could only store Jenkinsfile on svn and paste it on Jenkins web UI now, too sad :(   Thanks, Jingliang

New: Currently, create a pipeline, select "Pipeline script from SCM" and subversion as the code repository. We may like to load Jenkinsfile directly only instead of checking out all the svn repository (more than 15G) on master, the real "checkout" will be on slave node which is defined in Jenkinsfile. Not sure if there is any workaround? we could only store Jenkinsfile on svn and paste it on Jenkins web UI now, too sad :(   Thanks, Jingliang

Jingliang Fu made changes - 2017-03-21 07:53

Summary

Original: Optimize Jenkinsfile loading instead of check out all code on master

New: Optimize Jenkinsfile loading instead of checking out all code on master

Jesse Glick made changes - 2017-06-16 15:16

Link

New: This issue depends on JENKINS-33273 [ JENKINS-33273 ]

Jesse Glick made changes - 2017-06-16 15:16

Labels

New: multibranch pipeline

Joe Smith made changes - 2018-09-06 20:12

Link

New: This issue duplicates JENKINS-48420 [ JENKINS-48420 ]

Jesse Glick made changes - 2019-12-18 14:46

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]