diff options
author | Edward Thomson <ethomson@edwardthomson.com> | 2020-06-07 00:39:27 +0100 |
---|---|---|
committer | Edward Thomson <ethomson@edwardthomson.com> | 2020-06-16 09:22:58 +0100 |
commit | 47fb33baf07ff359ed0c1c62aef03a70b7989d16 (patch) | |
tree | 86b188e0a3a501b0bf05f364369eb0936193140f /azure-pipelines/build.sh | |
parent | 4852d8daa51772bc585ec983d3badfa89f90e6d3 (diff) | |
download | libgit2-ethomson/github_actions.tar.gz |
Introduce CI with GitHub Actionsethomson/github_actions
Add CI using GitHub Actions and GitHub Packages:
* This moves our Linux build containers into GitHub Packages; we will
identify the most recent commit that updated the docker descriptions,
and then look for a docker image in libgit2's GitHub Packages registry
for a container with the tag corresponding to that description. If
there is not one, we will build the container and then push it to
GitHub Packages.
* We no longer need to manage authentication with our own credentials or
PAT tokens. GitHub Actions provides a GITHUB_TOKEN that can publish
artifacts, packages and commits to our repository within a workflow
run.
* We will use a matrix to build our various CI steps. This allows us
to keep configuration in a single place without multiple YAML files.
Diffstat (limited to 'azure-pipelines/build.sh')
-rwxr-xr-x | azure-pipelines/build.sh | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/azure-pipelines/build.sh b/azure-pipelines/build.sh index 27e2f3e38..bec855d4a 100755 --- a/azure-pipelines/build.sh +++ b/azure-pipelines/build.sh @@ -13,6 +13,10 @@ BUILD_PATH=${BUILD_PATH:=$PATH} CMAKE=$(which cmake) CMAKE_GENERATOR=${CMAKE_GENERATOR:-Unix Makefiles} +if [[ "$(uname -s)" == MINGW* ]]; then + BUILD_PATH=$(cygpath "$BUILD_PATH") +fi + indent() { sed "s/^/ /"; } echo "Source directory: ${SOURCE_DIR}" |