Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-45999

Provide light weight checkout functionality for perforce in pipeline jobs

XMLWordPrintable

      Provide a light weight check out functionality for perforce so that when initializing the job or running it will not check out whole code repo to master. When we hold a huge code base it take too much time to trigger the build jobs as it has to chekcout the whole repo on to master and configure from jenkinsfile and then it starts it's build process.

       

      Must work for streams.

          [JENKINS-45999] Provide light weight checkout functionality for perforce in pipeline jobs

          karthik paidi created issue -
          karthik paidi made changes -
          Summary Original: Provide light weight checkout functionality for perforce New: Provide light weight checkout functionality for perforce in pipeline jobs

          Rob Petti added a comment -

          Karthik, perforce-plugin does not support pipeline at all. Are you sure you filed this against the correct plugin?

          Rob Petti added a comment - Karthik, perforce-plugin does not support pipeline at all. Are you sure you filed this against the correct plugin?

          karthik paidi added a comment -

          rpetti yes rob we are using perforce and all of our pipeline jobs are configure with that 

          karthik paidi added a comment - rpetti yes rob we are using perforce and all of our pipeline jobs are configure with that 

          Rob Petti added a comment -

          Karthik, the perforce-plugin is deprecated and does not support pipeline, so I cannot imagine how you are even using it. Are you absolutely sure you are using perforce-plugin and not p4-plugin? If you are, then I'll just close this ticket, because there's no way this will be implemented in perforce-plugin.

          Rob Petti added a comment - Karthik, the perforce-plugin is deprecated and does not support pipeline, so I cannot imagine how you are even using it. Are you absolutely sure you are using  perforce-plugin and not  p4-plugin ? If you are, then I'll just close this ticket, because there's no way this will be implemented in perforce-plugin.

          karthik paidi added a comment - - edited

          rpetti sorry it's P4-plugin 

          karthik paidi added a comment - - edited rpetti sorry it's P4-plugin 
          karthik paidi made changes -
          Labels Original: perforce pipeline New: p4-plugin pipeline
          Rob Petti made changes -
          Component/s New: p4-plugin [ 19224 ]
          Component/s Original: perforce-plugin [ 15506 ]
          Rob Petti made changes -
          Assignee Original: Rob Petti [ rpetti ]

          Paul Allen added a comment -

          Thank you Rob for forwarding this on.

          In the Job definition create a workspace view (or virtual stream) to map just the Jenkinsfile (plus any scripts/libs). Use a different name, I append '-script', then in the Jenkinsfile map your whole codebase in a different workspace (i.e the default).  

          https://github.com/jenkinsci/p4-plugin/blob/master/WORKFLOW.md#using-a-versioned-jenkinsfile

          Paul Allen added a comment - Thank you Rob for forwarding this on. In the Job definition create a workspace view (or virtual stream) to map just the Jenkinsfile (plus any scripts/libs). Use a different name, I append '-script', then in the Jenkinsfile map your whole codebase in a different workspace (i.e the default).   https://github.com/jenkinsci/p4-plugin/blob/master/WORKFLOW.md#using-a-versioned-jenkinsfile

            p4paul Paul Allen
            karthik546 karthik paidi
            Votes:
            4 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: