azure-pipelines-agent
setup-buildx-action
azure-pipelines-agent | setup-buildx-action | |
---|---|---|
15 | 14 | |
1,677 | 862 | |
0.7% | 2.1% | |
9.1 | 8.0 | |
4 days ago | 7 days ago | |
C# | TypeScript | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
azure-pipelines-agent
-
GitHub Actions Are a Problem
> GitHub Actions is based on Visual Studio Team Foundation Server's CI, and later Azure DevOps
Yes and no, ADO Agent (https://github.com/microsoft/azure-pipelines-agent) is far more secretive and "black-box" alike.
-
GitHub Actions could be so much better
Fun fact: Microsoft had a plan to provide that!
They canned it.
https://github.com/microsoft/azure-pipelines-agent/pull/2687...
- Self-hosted Devops agent: managed ID?
- Can anyone help me out
-
Pipeline to spawn build agent on Azure
You will need to download the agent (https://github.com/microsoft/azure-pipelines-agent/releases/latest ) and run the configure command.
-
Azure Pipelines - Node.js 16 and custom pipelines task extensions
A GitHub issue was opened to track support for different Node versions with custom tasks, but it remained unresolved for a long time. In October 2022 it was announced that Node.js 16 support was available.
-
AZ Modules gone on MS Hosted Devops Agents?
Even thought im in the EU datacenter, my hosted agent is version 2.213.2, which is also the latest version of the agent taht was released by MS - https://github.com/microsoft/azure-pipelines-agent
-
Hosting Azure DevOps Pipelines agents on GitHub Codespaces
{ "name": "AzurePipelines", "dockerFile": "Dockerfile", // Configure tool-specific properties. "customizations": { // Configure properties specific to VS Code. "vscode": { // Add the IDs of extensions you want installed when the container is created. "extensions": [ "ms-vscode.azurecli", "ms-vscode.powershell", "hashicorp.terraform", "esbenp.prettier-vscode", "tfsec.tfsec" ] } }, // Use 'forwardPorts' to make a list of ports inside the container available locally. // "forwardPorts": [], // Use 'postStartCommand' to run commands each time the container is successfully started.. "postStartCommand": "/home/vscode/azure-pipelines/start.sh", // Comment out to connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. "remoteUser": "vscode", // Amend Azure Pipelines agent version and arch type with 'ARCH' and 'AGENT_VERSION'. https://github.com/microsoft/azure-pipelines-agent/releases. "build": { "args": { "UPGRADE_PACKAGES": "true", "ARCH": "x64", "AGENT_VERSION": "2.206.1" } }, "features": { "terraform": "latest", "azure-cli": "latest", "git-lfs": "latest", "github-cli": "latest", "powershell": "latest" } }
-
Unpopular opinion: As a hobbyist and professional, I kind of prefer Azure DevOps.
Looks like they are working on it:https://github.com/microsoft/azure-pipelines-agent/issues/3922
-
ADO pipelines not rendering PS 7.2 new color escape sequences
Thanks for sharing this. As mentioned in this GitHub issue, the build pipeline does render PS 7.2 new color escape sequences, however release pipeline does not.
setup-buildx-action
-
GitHub Actions Are a Problem
Good luck running this locally. There's no script code to speak of, just references to external "actions" and parameters (for example, https://github.com/docker/setup-buildx-action).
Some CI platforms are just a simple glue layer (Gitlab CI - which I prefer - is one of them), but in most cases Github CI is not. Maybe it adds to the author frustration?
-
Automate Docker Image Builds and Push to Docker Hub Using GitHub Actions š³š
Set up Docker Buildx: We will use the docker/setup-buildx-action action to set up Docker Buildx.
-
One Dockerfile is all it takes, falling in love with bake
Thereās an amazing docker/bake-action which makes it insanely easy to build all of your containers in the most optimal way. Since weāve set the group ādefaultā block in the docker-bake.hcl, config is very minimal. One step in your GitHub Action workflow file will build all of your images and will push all of your cache layers, tag all of your containers, and push all your final images. Youāll still have to do things like checkout the code and donāt forget that youāll want to use the docker/setup-buildx-action since bake is a buildx feature. Thereās one quick gotcha for the actual docker/bake-action. We donāt want to push PR builds and we donāt want to pollute the cache with PR builds.
-
Building with Qemu via Github Actions taking forever. What other options are there?
To be clear, that article does NOT provide a solution for avoiding QEMU. I suggested it because it describes "the hard way" to get a single image multi-arch image. The github action crazy-max/ghaction-docker-buildx has been archived and replaced by docker/setup-qemu-action and docker/setup-buildx-action, which it seems like you were already using.
-
Pushing Cutom Images to Docker Hub using GitHub Actions
Third step is docker/setup-buildx-action configures buildx, which is a Docker CLI plugin that provides enhanced build capabilities.
-
Containerizing Laravel Applications
We then use the docker/setup-buildx-action action to initialize an environment to build Docker images:
-
How to use Docker layer caching in GitHub Actions
The setup-buildx-action configures Docker Buildx to create a builder instance for running the image build. The following step build-push-action, makes use of that instance to build your Docker image. The build-push-action supports all of the features provided by BuildKit out of the box. In our simple example, we are only specifying the Docker context, but more advanced features like SSH, secrets, and build args are supported.
- Why Darwin Failed (2006)
-
Multi-arch docker images the easy way, with Github Actions
# Get the repository's code - name: Checkout uses: actions/checkout@v2 # https://github.com/docker/setup-qemu-action - name: Set up QEMU uses: docker/setup-qemu-action@v1 # https://github.com/docker/setup-buildx-action - name: Set up Docker Buildx id: buildx uses: docker/setup-buildx-action@v1
-
Semantic release to npm and/or ghcr without any tooling
docker/setup-buildx-action@v1 - we use it to setup the docker builder
What are some alternatives?
actions-runner-controller - Kubernetes controller for GitHub Actions self-hosted runners
setup-qemu-action - GitHub Action to install QEMU static binaries
runner - The Runner for GitHub Actions :rocket:
build-push-action - GitHub Action to build and push Docker images with Buildx
github-act-runner - act as self-hosted runner
buildkit - concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
auth - A GitHub Action for authenticating to Google Cloud.
metadata-action - GitHub Action to extract metadata (tags, labels) from Git reference and GitHub events for Docker
act - Run your GitHub Actions locally š
setup-node - Set up your GitHub Actions workflow with a specific version of node.js
actions-runner-
cache - Cache dependencies and build outputs in GitHub Actions