Details

    • Type: Bug
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: git-plugin
    • Labels:
      None
    • Environment:
      Hudson 1.342 with git plugin 0.8
    • Similar Issues:

      Description

      There is no 'Push GIT tags back to origin repository' post-build action (as described on the plugin page), just 'Push Merges back to origin'. But tags don't get pushed back automatically either.

        Attachments

          Activity

          eris eris created issue -
          Hide
          woodstock3368 woodstock3368 added a comment -

          http://github.com/bruyeron/Hudson-GIT-plugin/commit/7cd28e8f854507037cc333097016f6ea44aaa289 would resolve this issue. How do you go about getting that change merged into the next release of git hudson plugin?

          Show
          woodstock3368 woodstock3368 added a comment - http://github.com/bruyeron/Hudson-GIT-plugin/commit/7cd28e8f854507037cc333097016f6ea44aaa289 would resolve this issue. How do you go about getting that change merged into the next release of git hudson plugin?
          abayer Andrew Bayer made changes -
          Field Original Value New Value
          Assignee jbq [ jbq ] abayer [ abayer ]
          Hide
          abayer Andrew Bayer added a comment -

          I'd say the right approach here would be to add a post-build action for pushing tags back, or better yet, to expand the "push merges" action to be more configurable, so that you can push back just tags, or merges, or changes without there having been merges, etc. I'll take a look.

          Show
          abayer Andrew Bayer added a comment - I'd say the right approach here would be to add a post-build action for pushing tags back, or better yet, to expand the "push merges" action to be more configurable, so that you can push back just tags, or merges, or changes without there having been merges, etc. I'll take a look.
          Hide
          abayer Andrew Bayer added a comment -

          About to make a run at this, with the intent of including an expanded GitPublisher in the next release.

          Show
          abayer Andrew Bayer added a comment - About to make a run at this, with the intent of including an expanded GitPublisher in the next release.
          Hide
          dogfood dogfood added a comment -

          Integrated in plugins_hudson-git-plugin #8
          JENKINS-5371 Final part of rewrite of GitPublisher, adding support for pushing tags and branches

          Andrew Bayer :
          Files :

          • src/main/resources/hudson/plugins/git/GitPublisher/help-pushMerge.html
          • src/main/webapp/gitPublisher.html
          • src/main/resources/hudson/plugins/git/GitPublisher/help-branchesToPush.html
          • src/main/resources/hudson/plugins/git/GitPublisher/help-tagsToPush.html
          Show
          dogfood dogfood added a comment - Integrated in plugins_hudson-git-plugin #8 JENKINS-5371 Final part of rewrite of GitPublisher, adding support for pushing tags and branches Andrew Bayer : Files : src/main/resources/hudson/plugins/git/GitPublisher/help-pushMerge.html src/main/webapp/gitPublisher.html src/main/resources/hudson/plugins/git/GitPublisher/help-branchesToPush.html src/main/resources/hudson/plugins/git/GitPublisher/help-tagsToPush.html
          abayer Andrew Bayer made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          abayer Andrew Bayer made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 135460 ] JNJira + In-Review [ 203496 ]
          Hide
          dantliff David Antliff added a comment -

          This isn't really fixed in my opinion - the plugin page still mentions the non-existent option, and the GitPublisher plugin doesn't have a way to push all tags - it can only push tags that can be explicitly named, so it's not useful for dynamically named tags that Jenkins doesn't know about.

          Show
          dantliff David Antliff added a comment - This isn't really fixed in my opinion - the plugin page still mentions the non-existent option, and the GitPublisher plugin doesn't have a way to push all tags - it can only push tags that can be explicitly named, so it's not useful for dynamically named tags that Jenkins doesn't know about.
          Hide
          dantliff David Antliff added a comment -

          Please reconsider this issue in light of my earlier comment.

          Show
          dantliff David Antliff added a comment - Please reconsider this issue in light of my earlier comment.
          dantliff David Antliff made changes -
          Resolution Fixed [ 1 ]
          Status Closed [ 6 ] Reopened [ 4 ]
          Hide
          bertr Bert Roos added a comment -

          Still quite confusing. The help text for "Create a tag for every build" of the Jenkins Git Plugin says this:

          Create a tag in the workspace for every build to unambiguously mark the commit that was built. You can combine this with Git publisher to push the tags to the remote repository.

          But the Git publisher has no option to push all tags. After a long internet search, I decided to go with just the Git publisher plug in.

          Show
          bertr Bert Roos added a comment - Still quite confusing. The help text for "Create a tag for every build" of the Jenkins Git Plugin says this: Create a tag in the workspace for every build to unambiguously mark the commit that was built. You can combine this with Git publisher to push the tags to the remote repository. But the Git publisher has no option to push all tags. After a long internet search, I decided to go with just the Git publisher plug in.

            People

            • Assignee:
              abayer Andrew Bayer
              Reporter:
              eris eris
            • Votes:
              5 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated: