Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Eliminate git sha from version in case of release #1188

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Commits on Jul 29, 2024

  1. eliminate git sha from version when a release is created

    For the PATCH value of the VERSION variable the git sha of the last
    commit was used, but in case of a release we want to change that value
    to 0, so it can be added in a package repository.
    
    If we set an environment variable IS_RELEASE then the PATCH variable will
    remain 0, otherwise will still be initialized with git sha.
    
    Signed-off-by: Andreea Andrisan <Andreea.Andrisan@analog.com>
    AAndrisa committed Jul 29, 2024
    Configuration menu
    Copy the full SHA
    238ed7c View commit details
    Browse the repository at this point in the history
  2. artifact_manifest.txt.cmakein: replace git sha variable with patch

    After switching to patch variable artifact check also needs to be
    updated.
    
    Signed-off-by: Andreea Andrisan <Andreea.Andrisan@analog.com>
    AAndrisa committed Jul 29, 2024
    Configuration menu
    Copy the full SHA
    340f71c View commit details
    Browse the repository at this point in the history

Commits on Aug 1, 2024

  1. ci:azure:ci-ubuntu.sh: configure /ci directory as safe

    In order to extract the git sha of the last commit from libiio the
    directory where a volume of the project was created needs to be set as
    safe, otherwise an error message will appear.
    
    Signed-off-by: Andreea Andrisan <Andreea.Andrisan@analog.com>
    AAndrisa committed Aug 1, 2024
    Configuration menu
    Copy the full SHA
    9fd8f57 View commit details
    Browse the repository at this point in the history
  2. azure-pipelines.yml: add checkout specifications

    In order to maintain the same length of the git sha during package
    creation all the jobs must have the same parameters at repository checkout.
    
    Signed-off-by: Andreea Andrisan <Andreea.Andrisan@analog.com>
    AAndrisa committed Aug 1, 2024
    Configuration menu
    Copy the full SHA
    c6d322a View commit details
    Browse the repository at this point in the history

Commits on Aug 6, 2024

  1. azure-pipelines.yml: integrate IS_RELEASE variable

    In case the build was triggered for a release purpose we don't want to
    use the git sha in the version of libiio.
    
    The new variable will be used in order to identify that is a build
    dedicated to a release.
    
    Signed-off-by: Andreea Andrisan <Andreea.Andrisan@analog.com>
    AAndrisa committed Aug 6, 2024
    Configuration menu
    Copy the full SHA
    7b407c4 View commit details
    Browse the repository at this point in the history