[JIRA] (JENKINS-38127) Git plugin does not build arbitrary tags in history

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

Mark Waite updated an issue

Jenkins / JENKINS-38127 Git plugin does not build arbitrary tags in history Change By: Mark Waite Summary: Git plugin does not build arbitrary tags in history Add Comment

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

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

Mark Waite commented on JENKINS-38127

Re: Git plugin does not build arbitrary tags in history Is there any pattern to the tags which are built vs. the tags which are not built? For example, the plugin is designed to consider successor commits as supersets of predecessor commits, so it might choose to ignore a change if the tag is applied to a commit in the history which precedes a commit that has already been built.

Add Comment

[m@medvecky.net (JIRA)]

Michal Medvecky commented on JENKINS-38127

Re: Git plugin does not build arbitrary tags in history

I pushed those tags: v12360 v12361 v12362 v12363 v12364 v12365 v12366 v12367 v12371 v12372 v12373 v12374 v12375 v12376 v12377 v12378 v12379 v12381 v12382 v12383 v12384 v12385 v12386 v12387 v12388 v12389 And those were built: v12365 v12366 v12376 v12381 v12389 All tags are annotated and pointing to the same commit. Situation is the same even when there are commits between tags, e.g. git commit ... git tag -a tag1 git tag -a tag2 git tag -a tag3 .. modify repo git commit ... git tag -a tag4 git tag -a tag5 ...

Add Comment

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

Mark Waite closed an issue as Won't Fix

This bug report is requesting to build the same commit again based on a new tag name being assigned to the commit. The git plugin considers a SHA-1 as the key to decide if a build should be run again. Once a SHA-1 has been built, it won't be built again by the polling mechanism because it has already been built.

Jenkins / JENKINS-38127

Git plugin does not build arbitrary tags in history

Change By: Mark Waite Status: Open Closed Resolution: Won't Fix

Add Comment

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