Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • CMake CMake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,802
    • Issues 3,802
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CMake
  • CMakeCMake
  • Issues
  • #20677

Closed
Open
Created May 05, 2020 by Kris Thielemans@krthieContributor

ExternalProject_Add and git tags

in our SuperBuild we use

  ExternalProject_Add(${proj}
 GIT_REPOSITORY ${${proj}_URL}
 GIT_TAG ${${proj}_TAG}
 ...)

We run into a problem when using a tag (as opposed to a hash or remote branch), the tag isn't recognised.

fatal: ambiguous argument 'rel_4.0.1': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Steps to reproduce

  1. git clone the superbuild
  2. build, everything is fine
  3. update one of the external projects and tag it
  4. build the superbuild with the new tag

It seems that ExternalProject_Add does a git fetch but not git fetch --tags. Some more info is at https://github.com/SyneRBI/SIRF-SuperBuild/issues/388

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking