[JIRA] [git-client-plugin] (JENKINS-25389) Allow push of tags created during the build

[rollertone@gmail.com (JIRA)]

Vito Andolini edited a comment on JENKINS-25389

Re: Allow push of tags created during the build The help text for the "Add Tag" section of the "Git Publisher" Post-Build Action states: bq. Specify tags to push at the completion of the build. bq. If the "Create Tag" or "Update tag" option is selected, the tag will be created or updated and pushed at the completion of the build, and the push will fail if a tag with the given name already exists. If the "Create Tag" option is not selected, the push will fail if the tag does not already exist. bq. *Environment variables may be used in the tag name - they will be replaced at build time.* bq. The repository name needs to be one of the repositories configured in the SCM section above.   I have found that environment variables can be used in the tag message, but not the name. I don't understand why the plug-in would require the tag name to be hard-coded - who would go configure the job before each build to add a hard-coded tag name? Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[rollertone@gmail.com (JIRA)]

Vito Andolini commented on JENKINS-25389

Re: Allow push of tags created during the build

The help text for the "Add Tag" section of the "Git Publisher" Post-Build Action states:

Specify tags to push at the completion of the build.

If the "Create Tag" or "Update tag" option is selected, the tag will be created or updated and pushed at the completion of the build, and the push will fail if a tag with the given name already exists. If the "Create Tag" option is not selected, the push will fail if the tag does not already exist.

Environment variables may be used in the tag name - they will be replaced at build time.

The repository name needs to be one of the repositories configured in the SCM section above.

I have found that environment variables can be used in the tag message, but not the name. I don't understand why the plug-in would require the tag name to be hard-coded - who would go configure the job before each build to add a hard-coded tag name?

Add Comment

[marcello_desales@intuit.com (JIRA)]

Marcello de Sales commented on JENKINS-25389

Re: Allow push of tags created during the build

Hi there, I'm coming from Node.js community... I use the following command when I finish a build: (https://docs.npmjs.com/cli/version) Building Develop Branch: Unable to find source-code formatter for language: sh. Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml npm version prerelease -m "Upgrade by CI" This will create a new commit, with a tag of the version increment for the current version, say, from 1.3.4, to 1.3.4-0. So, that can be ANY tag during the development cycle. Therefore, I also need to have the ability to publish ANY tag created by npm CLI. thanks!

Add Comment

[marcello_desales@intuit.com (JIRA)]

Marcello de Sales edited a comment on JENKINS-25389

Re: Allow push of tags created during the build

Hi there, I'm coming from Node.js community... I use the following command when I finish a build: (https://docs.npmjs.com/cli/version)

* Building Develop Branch:    {code: sh java }

npm version prerelease -m "Upgrade by CI"

{code}

This will create a new commit, with a tag of the version increment for the current version, say, from 1.3.4, to 1.3.4-0. So, that can be ANY tag during the development cycle. Therefore, I also need to have the ability to publish ANY tag created by npm CLI. thanks!

Add Comment

[david.vangompel@gmail.com (JIRA)]

David Van Gompel edited a comment on JENKINS-25389

Re: Allow push of tags created during the build

For anyone who's interested, I've found a workaround: 1. Add something like this to your shell script: {code:java} #!/bin/sh APP_BUILD_NUMBER=`npm version patch` echo APP_BUILD_NUMBER=${APP_BUILD_NUMBER} > build.properties {code} 2. then add build step *Inject environment variables* and set there Properties File Path to `$WORKSPACE/build.properties` 3. after that, $APP_BUILD_NUMBER is accessible in all build steps as environment variable. Click `Add tag` in Git Publisher (Post-build action) and set tag to push to $APP_BUILD_NUMBER.

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[david.vangompel@gmail.com (JIRA)]

David Van Gompel edited a comment on JENKINS-25389

Re: Allow push of tags created during the build

For anyone who's interested, I've found a workaround: 1. Add something like this to your shell script: {code:java} #!/bin/sh APP_BUILD_NUMBER=`npm version patch` echo APP_BUILD_NUMBER=${APP_BUILD_NUMBER} > build.properties {code}

2. then add build step* Inject environment variables *and set there Properties File Path to `$WORKSPACE/build.properties`

3. after that, $APP_BUILD_NUMBER is accessible in all build steps as environment variable. Click `Add tag` in Git Publisher (Post-build action) and set tag to push to $APP_BUILD_NUMBER.

Add Comment

[david.vangompel@gmail.com (JIRA)]

David Van Gompel commented on JENKINS-25389

Re: Allow push of tags created during the build

For anyone who's interested, I've found a workaround: 1. Add something like this to your shell script:

#!/bin/sh APP_BUILD_NUMBER=`npm version patch` echo APP_BUILD_NUMBER=${APP_BUILD_NUMBER} > build.properties

2. then add build step* Inject environment variables *and set there Properties File Path to `$WORKSPACE/build.properties` 3. after that, $APP_BUILD_NUMBER is accessible in all build steps as environment variable. Click `Add tag` in Git Publisher (Post-build action) and set tag to push to $APP_BUILD_NUMBER.

Add Comment

[hassony@yahoo.com (JIRA)]

Jon Has commented on JENKINS-25389

Re: Allow push of tags created during the build

It was sure easier if this feature would exist. Using the jgitflow:release-start/finish creates a tag in the build process, but doesn't push it to remote git. This feature would make it easier instead of configuring git ssh with the jenkins machine + manually call git commands (because git commands requires password, which cannot be done in an automatic job)

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite updated JENKINS-25389

Jenkins / JENKINS-25389

Allow push of tags created during the build

Change By: Mark Waite Status: Reopened Open

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)