[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-37050 Pipeline Job Cannot Checkout Git Tag Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173121.146974870.14313.1571794269423%40Atlassian.JIRA.
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title Torsten Reinhard commented on JENKINS-37050 Re: Pipeline Job Cannot Checkout Git Tag Michael DeGuzis I totally agree to what you said. Typically, DeployJobs need to checkout a specific tag and it would be very helpful in getting this done as simple as possible (means supported by git branch: "", credentials: "", url: "" ) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title Michael DeGuzis edited a comment on JENKINS-37050 Re: Pipeline Job Cannot Checkout Git Tag Sorry, but this is a bit ridiculous silly that tags are not considered a "simple" use case here. Thousands of projects use a tag for releases. Making them use the GitSCM class to pull a tag is not ideal. The vast majority of our Git workflow uses releases, as do many, many projects. Creating a branch for a release is not the intended workflow of Git. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title Michael DeGuzis commented on JENKINS-37050 Re: Pipeline Job Cannot Checkout Git Tag Sorry, but this is a bit ridiculous that tags are not considered a "simple" use case here. Thousands of projects use a tag for releases. Making them use the GitSCM class to pull a tag is not ideal. The vast majority of our Git workflow uses releases, as do many, many projects. Creating a branch for a release is not the intended workflow of Git. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title
Mark Waite edited a comment on JENKINS-37050
Re: Pipeline Job Cannot Checkout Git Tag
[~allan_burdajewicz] described correctly why this is not a bug. The `git` step intentionally is a simple subset of the full capabilities of the `checkout` step. Use the `checkout` step[~ plabedan derrickgw ] you can find an example using the full checkout step to checkout a specific tag in the [Jenkinsfile|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-37050/Jenkinsfile] of my [jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/] on the [JENKINS-37050 branch|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-37050]. The default clone settings intentionally do not download tags so that less data is transferred for multi-branch pipelines that are building a single branch. The example file adds the {{CloneOption}} which downloads tags.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title
Mark Waite edited a comment on JENKINS-37050
Re: Pipeline Job Cannot Checkout Git Tag
[~allan_burdajewicz] described correctly why this is not a bug. The `git` step intentionally is a simple subset of the full capabilities of the `checkout` step. Use the `checkout` step[~plabedan] you can find an example using the full checkout step to checkout a specific tag in the [Jenkinsfile|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-37050/Jenkinsfile] of my [jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/] on the [JENKINS-37050 branch|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-37050]. The default clone settings intentionally do not download tags so that less data is transferred for multi-branch pipelines that are building a single branch. The example file adds the {{CloneOption}} which download downloads tags.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title Mark Waite resolved as Not A Defect Allan BURDAJEWICZ described correctly why this is not a bug. The `git` step intentionally is a simple subset of the full capabilities of the `checkout` step. Use the `checkout` step Paul Labedan you can find an example using the full checkout step to checkout a specific tag in the Jenkinsfile of my jenkins-bugs repository on the JENKINS-37050 branch. The default clone settings intentionally do not download tags so that less data is transferred for multi-branch pipelines that are building a single branch. The example file adds the CloneOption which download tags. Jenkins / JENKINS-37050 Pipeline Job Cannot Checkout Git Tag Change By: Mark Waite Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title
Allan BURDAJEWICZ commented on JENKINS-37050
Re: Pipeline Job Cannot Checkout Git Tag
The git step is meant to be used for simple use cases. You can't for example specify a specific refspec. If you want to build tags, use the checkout step and specify the refspec +refs/tags/:refs/remotes/origin/tags/. For example:
node {
stage("testCheckout") {
checkout([$class: 'GitSCM',
branches: [[name: 'refs/tags/mytag']],
userRemoteConfigs: [[
credentialsId: 'myCredentialsId',
refspec: '+refs/tags/*:refs/remotes/origin/tags/*',
url: 'https://my.github.server/myuser/myrepo.git']]
])
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title Paul Labedan reopened an issue Jenkins / JENKINS-37050 Pipeline Job Cannot Checkout Git Tag Change By: Paul Labedan Resolution: Duplicate Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title Paul Labedan commented on JENKINS-37050 Re: Pipeline Job Cannot Checkout Git Tag I also don't think it's a duplicate of JENKINS-46207. What's needed here is a 'tag' or 'ref' parameter, like the 'branch' one. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title Brad M updated an issue Jenkins / JENKINS-37050 Pipeline Job Cannot Checkout Git Tag Change By: Brad M Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title Brad M commented on JENKINS-37050 Re: Pipeline Job Cannot Checkout Git Tag This is a show-stopper for us before switching to pipeline builds for our packaging. In this case the plugin's parameter 'branch' is a bit limiting Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-37050 Pipeline Job Cannot Checkout Git Tag Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title
Christopher Boumenot updated an issue
Jenkins / JENKINS-37050
Pipeline Job Cannot Checkout Git Tag
Change By:
Christopher Boumenot
I created a Pipeline project to build a Git project based on it's tag.node {git branch: 'refs/tags/VMAccess-1.4.1.0', url: 'https://github.com/azure/azure-linux-extensions'}The console output contains the following data. > git rev-parse refs/remotes/origin/refs/tags/VMAccess-1.4.1.0^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/refs/tags/VMAccess-1.4.1.0^{commit} # timeout=10 > git rev-parse origin/refs/tags/VMAccess-1.4.1.0^{commit} # timeout=10The correct rev-parse should be refs/tags/VMAccess-1.4.1.0, but that value is never tried by the plugin. (The value refs/remotes/origin/refs/tags/VMAccess-1.4.1.0 may also be valid.) I tried to influence the refspec, but setting the refspec key in the git command, but this had no effect.I create a Freestyle project, and set the branch to refs/tags/VMAccess-1.4.1.0. The project build built successfully.The console output contains the following data. > git rev-parse refs/tags/VMAccess-1.4.1.0^{commit} # timeout=10 > git rev-parse refs/remotes/origin/refs/tags/VMAccess-1.4.1.0^{commit} # timeout=10Checking out Revision 97fb7b019946ef71f15e73881b761e4ba1933781 (refs/tags/VMAccess-1.4.1.0)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title
Christopher Boumenot created an issue
Jenkins / JENKINS-37050
Pipeline Job Cannot Checkout Git Tag
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2016/Jul/28 11:31 PM
Environment:
jenkins v2.7.1 git-plugin v2.5.2
Labels:
workflow pipeline git tags
Priority:
Minor
Reporter:
Christopher Boumenot
I created a Pipeline project to build a Git project based on it's tag. node { git branch: 'refs/tags/VMAccess-1.4.1.0', url: 'https://github.com/azure/azure-linux-extensions' } The console output contains the following data. > git rev-parse refs/remotes/origin/refs/tags/VMAccess-1.4.1.0^ {commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/refs/tags/VMAccess-1.4.1.0^{commit} # timeout=10 > git rev-parse origin/refs/tags/VMAccess-1.4.1.0^ {commit} # timeout=10 The correct rev-parse should be refs/tags/VMAccess-1.4.1.0, but that value is never tried by the plugin. (The value refs/remotes/origin/refs/tags/VMAccess-1.4.1.0 may also be valid.) I tried to influence the refspec, but setting the refspec key in the git command, but this had no effect. I create a Freestyle project, and set the branch to refs/tags/VMAccess-1.4.1.0. The project build successfully. The console output contains the following data. > git rev-parse refs/tags/VMAccess-1.4.1.0^{commit} # timeout=10 > git rev-parse refs/remotes/origin/refs/tags/VMAccess-1.4.1.0^ {commit} # timeout=10 Checking out Revision 97fb7b019946ef71f15e73881b761e4ba1933781 (refs/tags/VMAccess-1.4.1.0)
