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

Feature Request: Fail build when SCP fails

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: scp-plugin
    • Labels:
      None
    • Environment:
      Using Hudson v1.352, Hudson SCP publisher plugin v1.6, on Redhat Fedora Core 5
    • Similar Issues:

      Description

      When the SCP publisher fails (for example, because the source file can't be found, or the destination is unwritable, or the credentials are invalid, or the remote host is unavailable), I'd like the entire build to be marked as a failure. Presumably, some folks may want to keep the current behavior (i.e. the build does not fail) so this should probably be configurable per project.

      Thanks for your consideration!

        Attachments

          Activity

          Hide
          torbent torbent added a comment -

          For me, scp failing to upload results in UNSTABLE builds. Example can be seen in JENKINS-7419.

          Show
          torbent torbent added a comment - For me, scp failing to upload results in UNSTABLE builds. Example can be seen in JENKINS-7419 .
          Hide
          thaljef thaljef added a comment -

          Ok, an UNSTABLE build is good enough then – as long as someone gets notified. However, I'm no longer working on a project that uses Hudson, so I can't verify that it actually behaves this way. But I'll take your word for it.

          Personally, I never quite understood the concept of an UNSTABLE build. I think the build should succeed completely or not at all. That includes test coverage, static analysis, and any post-build steps. But that's just how I like to configure my builds.

          Thanks for your response.

          Show
          thaljef thaljef added a comment - Ok, an UNSTABLE build is good enough then – as long as someone gets notified. However, I'm no longer working on a project that uses Hudson, so I can't verify that it actually behaves this way. But I'll take your word for it. Personally, I never quite understood the concept of an UNSTABLE build. I think the build should succeed completely or not at all. That includes test coverage, static analysis, and any post-build steps. But that's just how I like to configure my builds. Thanks for your response.
          Hide
          torbent torbent added a comment -

          Actually I would also prefer that failure to upload results in a failed build – I was merely stating my observations in the belief that they were different from yours.
          Anyway, failed build is better.

          Show
          torbent torbent added a comment - Actually I would also prefer that failure to upload results in a failed build – I was merely stating my observations in the belief that they were different from yours. Anyway, failed build is better.

            People

            • Assignee:
              ramazanyich2 ramazanyich2
              Reporter:
              thaljef thaljef
            • Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: