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

Entire stream synced to the script workspace "...@script".

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • p4-plugin
    • None

    Description

      When using a multibranch pipeline with streams...  The entire stream source is synced into a workspace directory called "xxx@script".  This is a huge waste of time and space as the only file needed is the Jenkinsfile.   I see no way to configure the project to filter the @script workspace.  

      This may be unrelated, but my setup also includes a custom path to the Jenkinsfile, using the "script path" field with the value "components/template/Jenkinsfile". 

      Attachments

        Issue Links

          Activity

            p4karl Karl Wirth added a comment -

            Reproduced - Sept 7 2017.

            p4karl Karl Wirth added a comment - Reproduced - Sept 7 2017.

            Hey p4paul, any chance of an ETA on this? It's a real hassle for us, almost daily. We've got a couple of projects, biggest one is ~6-7gb, running with checked in Jenkinsfile and Multibranch Pipeline (via Helix Streams for CVS source), and my master is filling up problematically often. I'm building on another node, of course. Happy to provide info if needed. Best, Daniel, Resolution Games

            danielresolutiongames Daniel Hagström added a comment - Hey p4paul , any chance of an ETA on this? It's a real hassle for us, almost daily. We've got a couple of projects, biggest one is ~6-7gb, running with checked in Jenkinsfile and Multibranch Pipeline (via Helix Streams for CVS source), and my master is filling up problematically often. I'm building on another node, of course. Happy to provide info if needed. Best, Daniel, Resolution Games
            p4paul Paul Allen added a comment -

            There are a few jobs related to this issue, it relates to JENKINS-45999.  There is a workaround using a p4 client with a narrow view for the @Script and a second p4 client for your code.

            p4paul Paul Allen added a comment - There are a few jobs related to this issue, it relates to  JENKINS-45999 .  There is a workaround using a p4 client with a narrow view for the @Script and a second p4 client for your code.
            p4paul Paul Allen added a comment -

            Closing issue as duplicate; please follow JENKINS-45999

            p4paul Paul Allen added a comment - Closing issue as duplicate; please follow  JENKINS-45999

            People

              p4paul Paul Allen
              cmcguire79 Chris McGuire
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: