GitVersion unable to work with remote reference and needs local copy of branches

Abierto
#2,921 6 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
csharp, git
Área
devtools, release

Línea de trabajo

Comienza con los pasos de reproducción usando un repositorio en el que develop se haya eliminado localmente mientras todavía existe en el remoto, e inspecciona los puntos de entrada que determinan la información de rama y versión de GitVersion. Se considera terminado cuando un feature branch puede resolver el historial de develop y producir la versión esperada 1.2.0-version-test.1+## sin descargar localmente todas las ramas.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

feature

Currently the GitVersion to support gitflow requires all the branches to be local in-order to get the correct version. This is not an issue when working on individual dev machines, but when you start using them with centralized build tool like Jenkins etc., downloading all the branches into the container becomes a challenge. As it takes lots of disk space and time (depends on how clean the graph is, i.e. people remove unwanted feature branches with discipline). My company build pipeline do not download all the branches and thus versioning breaks.

Expected Behavior

Let refer to a simple example, where master is tagged at 1.1.0

  • a commit on develop branch and build creates a version 1.2.0-alpha.#
  • a feature branch "version_test" created from develop, with commit and build should give version 1.2.0-version-test.1+##

Actual Behavior

A feature branch "version_test" created from develop, with commit and build gives version 1.1.0-version-test.1+##
The reason is the develop branch is not downloaded in to the build pipeline container, as it only gets master and "version_test" branch.

Possible Fix

If GitVersion is able to get the information from the remote repository instead dependent on branches available it would resolve the issue.

Steps to Reproduce

  1. create a simple repo with spring boot samples
  2. tag the master with 1.1.0
  3. create develop and make a commit , creating the version "Major": 1, "Minor": 2, "Patch": 0,
  4. create a feature branch "feature/version_test" and make a commit.
  5. gitversion will show a version "Major": 1, "Minor": 2, "Patch": 0,
  6. delete the develop branch from local
  7. gitversion will show a version "Major": 1, "Minor": 1, "Patch": 0,

Context

Since due to limited space for the build container, the build pipeline cannot download all the branches. This is limiting us to make the use of this wonderful tool. Only teams in our company that uses Mainline branch strategy are able to use this tool while projects that uses gitflow have to continue manually control their versions.

Your Environment

All environments

  • Version Used: 5.8.1
  • Operating System and version (Windows 10, Ubuntu 18.04): all
  • Link to your project: cannot due to confidentiality
  • Link to your CI build (if appropriate): NA
Lenguaje dominante
C#
Estrellas
3.1k
Forks
661
Merge medio
7 h 4 min
PR fusionados (30 d)
77

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de GitTools/GitVersion

Todos los issues de GitTools/GitVersion

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.