Allow SCMs to provide the location of the workspace

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

XMLWordPrintable

    • Type: Improvement
    • Resolution: Cannot Reproduce
    • Priority: Critical
    • Component/s: core
    • Environment:
      Platform: All, OS: All

      User's of clearcase get a suboptimal Hudson experience because of the way
      Clearcase snapshot views work. Clearcase snapshot views create a view directory
      within the Hudson workspace that must be globally unique. This means that this
      view directory generally has to contain the name of the build agent host in
      order to avoid conflicts. Since Hudson can relocate the build to other slave
      agents, that path to the real directory that the build runs from changes based
      on host. This breaks downstream plugins that require relative paths from the
      workspace root directory.

      To remedy this situation, I would like to suggest that SCM providers be able to
      set the actual workspace root directory that downstream functions use as the
      root of the workspace. This would save a lot of job specific configuration work
      (like setting the path to the pom.xml in every Maven execution, path to the
      clover output, path to the javadoc, etc.).

            Assignee:
            Unassigned
            Reporter:
            Peter Hayes
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: