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

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • git-plugin
    • None
    • Docker Image: jenkins/jenkins:lts-jdk11

      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.

            Unassigned Unassigned
            kemuelverzosa Jonah Kemuel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: