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

Artifact Deployer does not handle OS type well

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Labels:
      None
    • Environment:
      Mixed: Linux Jenkins with Linux/Windows Mixed Slaves
    • Similar Issues:

      Description

      Some jobs are locked to a specific OS (Linux or Windows), but some jobs "float" . . . the point is to test the build under both OS's. Thinking I was designating the location of the build from the master (where post build plugins generally run) I entered the Linux AFS path for my archive:

      /prj/qct/asw/buildcomp/buildcomp_team_archive/Temp/fmerrowtest/${JOB_NAME}/{$BUILD_ID}

      Imagine my surprise when after 18 minutes of copying the share was still empty.

      I eventually found the copy at D:\prj\...

      For jobs that don't float, this can be set to the "right" location, but for jobs that do float there is no right address for a network share that can be seen for both OSs.

      Either you need to let the master resolve this (yes I understand the implications of copying 40K files that way) or else you need to allow for two paths . . . one used for Linux . . . one for Windows.

        Attachments

          Activity

          Hide
          gbois Gregory Boissinot added a comment -

          Use Matrix Job Type for this kind of issue.

          Show
          gbois Gregory Boissinot added a comment - Use Matrix Job Type for this kind of issue.
          Hide
          fmerrow Frank Merrow added a comment -

          Close it if you want, but you've missed the point.

          I don't want to run the job on Linux AND Windows . . . however, the job is setup so it can run on EITHER Linux or Windows.

          One option would be to "node lock" the job to a specific OS type using labels.

          But if the goal is to actually let the job build on either type . . . there is no way to know what type of OS you might actually build on for any given job run.

          Matrix Job would be ideal if I wanted to run both . . . I don't . . . I want to run "here" whatever here happens to be.

          The curse of running a combined Windows/Linux shop where both are equal.

          Frank

          Show
          fmerrow Frank Merrow added a comment - Close it if you want, but you've missed the point. I don't want to run the job on Linux AND Windows . . . however, the job is setup so it can run on EITHER Linux or Windows. One option would be to "node lock" the job to a specific OS type using labels. But if the goal is to actually let the job build on either type . . . there is no way to know what type of OS you might actually build on for any given job run. Matrix Job would be ideal if I wanted to run both . . . I don't . . . I want to run "here" whatever here happens to be. The curse of running a combined Windows/Linux shop where both are equal. Frank
          Hide
          gbois Gregory Boissinot added a comment -

          Use a variable set by the build with a Windows value for Windows and an Unix value for an Unix run.
          And specify the variable for the remote location in the ArtifactDeployer configuration.

          Show
          gbois Gregory Boissinot added a comment - Use a variable set by the build with a Windows value for Windows and an Unix value for an Unix run. And specify the variable for the remote location in the ArtifactDeployer configuration.

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              fmerrow Frank Merrow
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: