Entire repositories are cloned in master even though the pipeline are built on a different agent

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Our Jenkins server got full because of some pipelines checking out full repositories on the server itself even if it's getting build on a different agent. The cloned repositories have a different naming convention also, it looks something like this:

      workspace
      |_____pipeline@script
               |_______commit-hash/ << this is the entire repository
               |_______commit-hash-scm-key.txt
               |_______commit-hash@tmp/
      

      Has anybody encountered this issue before? I don't know what's causing it.

            Assignee:
            Unassigned
            Reporter:
            Jonah Kemuel
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: