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

Provide lightweight checkout capability for bitbucket to avoid repository clone for multi-branch pipeline jobs

    XMLWordPrintable

    Details

    • Epic Link:
    • Sprint:
      Blue Ocean 1.4 - beta 2
    • Similar Issues:

      Description

      JENKINS-33273 introduced a lightweight checkout capability to allow SCM implementors to avoid having checkout the scm on the master to read the contents of the Jenkinsfile from the SCM.  The comments in that bug mention that git doesn't offer a way to do so but I would think this is possible to do using Bitbucket APIs to read a particular file's contents on a branch.  

      In our use case, our repository is multi-gigabyte and we have many developers working within it creating many branches so cloning the repo on master for every branch is very costly in terms of time and storage.

        Attachments

          Issue Links

            Activity

            Hide
            ghristov88 Georgi Hristov added a comment -

            Michael Neale yes I am running 2.2.7. What can I provide to help you reproduce the issue?

            Show
            ghristov88 Georgi Hristov added a comment - Michael Neale yes I am running 2.2.7. What can I provide to help you reproduce the issue?
            Hide
            michaelneale Michael Neale added a comment - - edited

            Georgi Hristov perhaps should put this in a new issue, as it looks a bit distinct from what others are seeing. 

            Just reproduction instructions should be doable, I expect it is more encoding confusion where it can't find the resource, so falls back to what it knows works, but I assume when it falls back it does work at least. 

            Show
            michaelneale Michael Neale added a comment - - edited Georgi Hristov perhaps should put this in a new issue, as it looks a bit distinct from what others are seeing.  Just reproduction instructions should be doable, I expect it is more encoding confusion where it can't find the resource, so falls back to what it knows works, but I assume when it falls back it does work at least. 
            Hide
            ghristov88 Georgi Hristov added a comment -

            Michael Neale, yes it falls back and it works. I will open a new issue later today.

            Show
            ghristov88 Georgi Hristov added a comment - Michael Neale , yes it falls back and it works. I will open a new issue later today.
            Hide
            netappbluedevil NetAppBlueDevil added a comment -

            I am also seeing the same issue as Georgi using 2.2.7 plugin version.  I'm running with Bitbucket Server version 4.11.  Is there a Bitbucket version requirement for the API used to be available?

            Show
            netappbluedevil NetAppBlueDevil added a comment - I am also seeing the same issue as Georgi using 2.2.7 plugin version.  I'm running with Bitbucket Server version 4.11.  Is there a Bitbucket version requirement for the API used to be available?
            Hide
            alunsford Aaron Lunsford added a comment -

            Is this feature toggle-able? Upgraded today from 2.2.3 and it randomly broke pipelines across the board. All of our jobs were configured to use the stash step in the @script directory to take advantage of that initial checkout. After upgrading to 2.2.7, jobs will sometimes do the heavy checkout while others will sometimes do the light checkout, with no real distinction as to why.

            Do we now need to explicitly have a step in our pipeline code to checkout out the repository? I've rolled back to 2.2.3 but I don't want to keep relying on an old version of the plugin. Does anyone have a recommendation on how to proceed?

            Show
            alunsford Aaron Lunsford added a comment - Is this feature toggle-able? Upgraded today from 2.2.3 and it randomly broke pipelines across the board. All of our jobs were configured to use the stash step in the @script directory to take advantage of that initial checkout. After upgrading to 2.2.7, jobs will sometimes do the heavy checkout while others will sometimes do the light checkout, with no real distinction as to why. Do we now need to explicitly have a step in our pipeline code to checkout out the repository? I've rolled back to 2.2.3 but I don't want to keep relying on an old version of the plugin. Does anyone have a recommendation on how to proceed?

              People

              • Assignee:
                vivek Vivek Pandey
                Reporter:
                petehayes Peter Hayes
              • Votes:
                18 Vote for this issue
                Watchers:
                30 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: