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

Allow choice of axes to be applied to workspace

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • matrix-project-plugin
    • None
    • Platform: All, OS: All

      Just tried setting up a first Matrix build and was a bit surprised with the
      SCM/workspace interaction.

      Having Axes:
      Config=Debug Release
      Platform=Win32 x64

      I had 5 copies of the project checked out. First into the main workspace, then
      into the 4 Axes matrix.

      The one build area would have been fine for use on these 2 Axes as the workspace
      already knows through parameterisation how to separate the build results.

          [JENKINS-4285] Allow choice of axes to be applied to workspace

          wohauser added a comment -

          We don't need the checkout into the main workspace too. It is only a waste of
          resources.

          I would also propose to have a check box to select if the main workspace may be
          used for all axes. If the axes should use separate workspaces, no checkout into
          the main workspace is necessary.

          The main project then acts only as a starter of the axes projects. Therefor it
          may not be necessary to occupy a queue slot for this main project.

          So my proposal was:

          • main workspace could be marked to be used for all axes.
          • axes could be grouped to share the same workspace.
          • starter project do not occupy a queue slot.

          This proposal is from my view as a user of hudson, I haven't look deep inside to
          hudson yet.

          wohauser added a comment - We don't need the checkout into the main workspace too. It is only a waste of resources. I would also propose to have a check box to select if the main workspace may be used for all axes. If the axes should use separate workspaces, no checkout into the main workspace is necessary. The main project then acts only as a starter of the axes projects. Therefor it may not be necessary to occupy a queue slot for this main project. So my proposal was: main workspace could be marked to be used for all axes. axes could be grouped to share the same workspace. starter project do not occupy a queue slot. This proposal is from my view as a user of hudson, I haven't look deep inside to hudson yet.

          wohauser added a comment -

          Added myself to cc list

          wohauser added a comment - Added myself to cc list

          anb0s added a comment -

          We have same issue with ClearCase SCM checkouts. We need one checkout in main workspace (ClearCase view) and then build it for different configurations. We need a checkbox to using same workspace for all configurations.

          anb0s added a comment - We have same issue with ClearCase SCM checkouts. We need one checkout in main workspace (ClearCase view) and then build it for different configurations. We need a checkbox to using same workspace for all configurations.

            Unassigned Unassigned
            gdomjan gdomjan
            Votes:
            7 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: