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

Git push tag in case if build SUCCESS only, UNSTABLE result is not pushing a tag.

      Git push tag only in case if build SUCCESS only, UNSTABLE result is not push a tag.

      Since UNSTABLE status in general can be "stable" with warnings. Since compilation errors or something critical don't happens during build we need to have ability to push tag even build is unstable.

      Possible fix I will push as pull request.

          [JENKINS-16646] Git push tag in case if build SUCCESS only, UNSTABLE result is not pushing a tag.

          Vladimir Kravets created issue -

          if "UNSTABLE status in general can be "stable" with warnings" then your job is just misconfigured. if "warnings" aren't relevant they shouldn't break the build. I don't consider an UNSTABLE build to be production-ready, so should not be tagged and go further in the build-pipeline

          Nicolas De Loof added a comment - if "UNSTABLE status in general can be "stable" with warnings" then your job is just misconfigured. if "warnings" aren't relevant they shouldn't break the build. I don't consider an UNSTABLE build to be production-ready, so should not be tagged and go further in the build-pipeline

          From our point of view in continous process it's can be life, since there can be exists some issues due which tests are failed (bug or bugs about which we are know) and QA should get build with some limitation.(Since another features are working and QA should test it)
          To fix these issues need some time e.g. 2-4 days. As I said before QA should get build during this 2-4 days.

          We are using tagging to have stable(or unstable) build (but not failed). Continous build marks in source control tag e.g. "stable" and nighly build use this tag to have "good" build.

          Vladimir Kravets added a comment - From our point of view in continous process it's can be life, since there can be exists some issues due which tests are failed (bug or bugs about which we are know) and QA should get build with some limitation.(Since another features are working and QA should test it) To fix these issues need some time e.g. 2-4 days. As I said before QA should get build during this 2-4 days. We are using tagging to have stable(or unstable) build (but not failed). Continous build marks in source control tag e.g. "stable" and nighly build use this tag to have "good" build.

          Possible fix was implemented in the pull request - https://github.com/jenkinsci/git-plugin/pull/128

          Kutzi comments some things in this pull request. Thus I will change some behavior in the fix.

          Vladimir Kravets added a comment - Possible fix was implemented in the pull request - https://github.com/jenkinsci/git-plugin/pull/128 Kutzi comments some things in this pull request. Thus I will change some behavior in the fix.

          Mikolaj Leszczynski added a comment - - edited

          Hello, any updates on this issue?
          We consider failing tests acceptable, as Android's test suite tends to be unreliable. The plugin not pushing when it's unstable disrupts our tagging and versioning system. It would be nice to at leat have the option to push if it's also unstable.

          Mikolaj Leszczynski added a comment - - edited Hello, any updates on this issue? We consider failing tests acceptable, as Android's test suite tends to be unreliable. The plugin not pushing when it's unstable disrupts our tagging and versioning system. It would be nice to at leat have the option to push if it's also unstable.
          Vladimir Kravets made changes -
          Summary Original: Git push tag only in case if build SUCCESS only, UNSTABLE result is not push a tag. New: Git push tag in case if build SUCCESS only, UNSTABLE result is not pushing a tag.

          Mark Waite added a comment -

          The git publisher has a post build action has a checkbox to push only on success. Is that sufficient to meet this need?

          Mark Waite added a comment - The git publisher has a post build action has a checkbox to push only on success . Is that sufficient to meet this need?

          Mark Waite added a comment -

          Publish only if build succeeds - screen clip

          Mark Waite added a comment - Publish only if build succeeds - screen clip
          Mark Waite made changes -
          Attachment New: publish-only-if-ok.png [ 27781 ]
          Kanstantsin Shautsou made changes -
          Labels New: git-publisher

            Unassigned Unassigned
            vkravets Vladimir Kravets
            Votes:
            4 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: