ci: use GitHub Actions #2401
Closed
ci: use GitHub Actions #2401
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dscho
force-pushed
the
github-action
branch
7 times, most recently
from
860a4e9 to
0d76f83
Compare
dscho
force-pushed
the
github-action
branch
11 times, most recently
from
53aee96 to
dbe366c
Compare
We no longer test specifically whether Git's source code builds under `core.autoCRLF=true`, as this is already tested implicitly by our Windows CI/PR builds. Signed-off-by: Johannes Schindelin <[email protected]>
This should help with adding new CI-specific if-else arms. Signed-off-by: Johannes Schindelin <[email protected]>
For each CI system we support, we need a specific arm in that if/else construct in ci/lib.sh. Let's add one for GitHub Actions. Signed-off-by: Johannes Schindelin <[email protected]>
This patch adds CI builds via GitHub Actions. While the underlying technology is at least _very_ similar to that of Azure Pipelines, GitHub Actions are much easier to set up than Azure Pipelines: no need to install a GitHub App, no need to set up an Azure DevOps account, all you need to do is push to your fork on GitHub. Therefore, it makes a lot of sense for us to have a working GitHub Actions setup. While transmogrifying `azure-pipelines.yml` into `.github/workflows/main.yml`, we also use the opportunity to accelerate the step that sets up a minimal subset of Git for Windows' SDK in the Windows-build job: we now download a `.tar.xz` stored in Azure Blobs and extract it simultaneously (by calling `curl` and piping the result to `tar`, decompressing via `xz`, all three utilities being available by grace of using Git for Windows' Bash that is installed on the build agents). This accelerates that step from ~1m50s to ~7s. Also, we do away with the parts that try to mount a file share on which `prove` can store data between runs. It is just too complicated to set up, so it's little return on investment there. Signed-off-by: Johannes Schindelin <[email protected]>
Signed-off-by: Johannes Schindelin <[email protected]>
We have GitHub Actions now. Running the same builds and tests in Azure Pipelines would be redundant, and a waste of energy. Signed-off-by: Johannes Schindelin <[email protected]>
|
I'll abandon this and open a PR with a branch in my personal fork instead. |
|
Successor: #2577 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch adds CI builds via GitHub Actions. Companion GitGitGadget-submitted patches are here: git#743.
GitHub Actions do not offer as nice a UI for the tests, which is a real downside for now. Not sure whether that's reason enough to with the Azure Pipeline we have. My gut feeling is that we should switch to GitHub Actions.