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

Deployment shouldn't fail if there is no changes

      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

          [JENKINS-19016] Deployment shouldn't fail if there is no changes

          Hi,

          I can change build status from failed to unstable if the step of pre-requisites check failed.
          If the build is flagged as SUCCESS whereas the deployment didn't occured it could be a bit confusing.

          Does This change can resolve your issue ?

          Regards

          Raphael CHAUMIER added a comment - Hi, I can change build status from failed to unstable if the step of pre-requisites check failed. If the build is flagged as SUCCESS whereas the deployment didn't occured it could be a bit confusing. Does This change can resolve your issue ? Regards

          About my issue I redeploy the app even if the code has not changed adding, after the SVN revision, the Jenkins deployment number. So impossible to repeat the deployment version.

          I agree with you that I may be confusing. Sorry for not thinking about that previously. I let up to you to mark it as UNSTABLE.

          Thanks

          Miquel Serralta added a comment - About my issue I redeploy the app even if the code has not changed adding, after the SVN revision, the Jenkins deployment number. So impossible to repeat the deployment version. I agree with you that I may be confusing. Sorry for not thinking about that previously. I let up to you to mark it as UNSTABLE. Thanks

          version 2.6

          Raphael CHAUMIER added a comment - version 2.6

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

              Created:
              Updated:
              Resolved: