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

Deployment shouldn't fail if there is no changes

XMLWordPrintable

      I thinks I could find a non-sense scenario.

      I use a redeploy feature implemented in the version 2.4, so I cannot redeploy the same version of the app more than once. For that reason I marked the option Deploying only when sources changes.

      On the other hand, I want to be notified when deployment fails, so I marked Build failed when deployment failed.

      The "problem" is that marking as failed a non deployed app if it has not been deployed because there is no changes on the source may not be logic. Do you agree? Or am I misunderstood the usage of these options?

      Wouldn't it be marked as failed only if it fails when there was an attempt to deploy (or redeploy)?? I understand if the source does not change there is no attempt to (re-)deploy...

      Thanks

            raphc Raphael CHAUMIER
            miquelserralta Miquel Serralta
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: