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

Connection refused error does not fail the step

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • ftppublisher-plugin
    • None

      We use ftpPublisher with 

      continueOnError: false, failOnError: true

      so we would expect that the step fails when an error occurs during publishing. 

      However, we get 

      ERROR: Exception when publishing, exception message [Connection refused (Connection refused)]

      but the step does not fail but ends with SUCCESS. 

      This is a problem, because other jobs fail that depend on the published artifacts, and the actual cause goes unnoticed. Instead, we have to check the console logs manually.

      Is there anything else that needs to be configured? Otherwise, I'd say this is a bug.

          [JENKINS-71705] Connection refused error does not fail the step

          mesa created issue -
          mesa made changes -
          Description Original: We use ftpPublisher with 

          continueOnError: false, failOnError: true

          so we would expect that the step fails when an error occurs during publishing. 

          However, we get 
          ERROR: Exception when publishing, exception message [Connection refused (Connection refused)]
          but the step does not fail but ends with SUCCESS. 

          This is a severe problem, because other jobs fail that depend on the published artifacts, and the actual cause goes unnoticed. Instead, we have to check the console logs manually.

          Is there anything else that needs to be configured? Otherwise, I'd say this is a bug.           		New: We use ftpPublisher with 

          {{continueOnError: false, failOnError: true}}

          so we would expect that the step fails when an error occurs during publishing. 

          However, we get 
          {{ERROR: Exception when publishing, exception message [Connection refused (Connection refused)]}}
          {{but the step does not fail but ends with SUCCESS. }}

          This is a severe problem, because other jobs fail that depend on the published artifacts, and the actual cause goes unnoticed. Instead, we have to check the console logs manually.

          Is there anything else that needs to be configured? Otherwise, I'd say this is a bug.
          mesa made changes -
          Description Original: We use ftpPublisher with 

          {{continueOnError: false, failOnError: true}}

          so we would expect that the step fails when an error occurs during publishing. 

          However, we get 
          {{ERROR: Exception when publishing, exception message [Connection refused (Connection refused)]}}
          {{but the step does not fail but ends with SUCCESS. }}

          This is a severe problem, because other jobs fail that depend on the published artifacts, and the actual cause goes unnoticed. Instead, we have to check the console logs manually.

          Is there anything else that needs to be configured? Otherwise, I'd say this is a bug.           		New: We use ftpPublisher with 

          {{continueOnError: false, failOnError: true}}

          so we would expect that the step fails when an error occurs during publishing. 

          However, we get 
          {{ERROR: Exception when publishing, exception message [Connection refused (Connection refused)]}}
          {{but the step does not fail but ends with SUCCESS. }}

          This is a problem, because other jobs fail that depend on the published artifacts, and the actual cause goes unnoticed. Instead, we have to check the console logs manually.

          Is there anything else that needs to be configured? Otherwise, I'd say this is a bug.
          mesa made changes -
          Description Original: We use ftpPublisher with 

          {{continueOnError: false, failOnError: true}}

          so we would expect that the step fails when an error occurs during publishing. 

          However, we get 
          {{ERROR: Exception when publishing, exception message [Connection refused (Connection refused)]}}
          {{but the step does not fail but ends with SUCCESS. }}

          This is a problem, because other jobs fail that depend on the published artifacts, and the actual cause goes unnoticed. Instead, we have to check the console logs manually.

          Is there anything else that needs to be configured? Otherwise, I'd say this is a bug.           		New: We use ftpPublisher with 

          {{continueOnError: false, failOnError: true}}

          so we would expect that the step fails when an error occurs during publishing. 

          However, we get 

          {{ERROR: Exception when publishing, exception message [Connection refused (Connection refused)] }}

          but the step does not fail but ends with SUCCESS. 

          This is a problem, because other jobs fail that depend on the published artifacts, and the actual cause goes unnoticed. Instead, we have to check the console logs manually.

          Is there anything else that needs to be configured? Otherwise, I'd say this is a bug.
          mesa made changes -
          Description Original: We use ftpPublisher with 

          {{continueOnError: false, failOnError: true}}

          so we would expect that the step fails when an error occurs during publishing. 

          However, we get 

          {{ERROR: Exception when publishing, exception message [Connection refused (Connection refused)] }}

          but the step does not fail but ends with SUCCESS. 

          This is a problem, because other jobs fail that depend on the published artifacts, and the actual cause goes unnoticed. Instead, we have to check the console logs manually.

          Is there anything else that needs to be configured? Otherwise, I'd say this is a bug.           		New: We use ftpPublisher with 

          {{continueOnError: false, failOnError: true}}

          so we would expect that the step fails when an error occurs during publishing. 

          However, we get 
          {code:java}
          ERROR: Exception when publishing, exception message [Connection refused (Connection refused)]{code}
          but the step does not fail but ends with SUCCESS. 

          This is a problem, because other jobs fail that depend on the published artifacts, and the actual cause goes unnoticed. Instead, we have to check the console logs manually.

          Is there anything else that needs to be configured? Otherwise, I'd say this is a bug.

            benjaminjaton benjaminjaton
            mesa mesa
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: