virtual-environments
runner
Our great sponsors
virtual-environments | runner | |
---|---|---|
54 | 59 | |
6,399 | 4,498 | |
- | 2.6% | |
9.8 | 9.1 | |
over 1 year ago | 2 days ago | |
PowerShell | C# | |
MIT License | MIT License |
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.
virtual-environments
-
Deploy to Google AppEngine with GitHubActions
This action runs using Node 16. If you are using self-hosted GitHub Actions runners, you must use runner version 2.285.0 or newer.
-
Ensuring Your E2E Tests Run On Every Code Push
This is the OS and version used for the virtual environment in which run our tests. I recommend always using a specific version, such as the latest stable version, rather than latest, which is risky because you may then suddenly start to see test failures caused by a version update that has nothing to do with your tests. See virtual-enviroments for the latest stable version.
-
How would you suggest running unit tests within containers in a CI AKS based considering docker.sock isnβt available anymore?
This, I setup Azure DevOps pipeline that clones this: https://github.com/actions/virtual-environments Runs it in Linux servers, copies VHD into Storage Account, creates an image from it and makes it new image for Azure Scale Set. Runs every Monday Morning on timer.
-
Ask HN: How are you dealing with the M1/ARM migration?
I'm in a similar boat - love the performance/battery of my M1 MacBook Air, but the ecosystem is just too messy at the moment for me. I have a few tools I need to use that haven't yet been making official Apple Silicon releases due to GitHub actions not supporting Apple Silicon fully yet. The workaround involves maintaining two versions of homebrew, one for ARM and one for x86-64, and then being super careful to make sure you don't forget if you're working in an environment that's ARM and one that's X86. It's too much of a pain to keep straight for me (I admit it - I lack patience and am forgetful, so this is a bit of a "me" problem versus a tech problem).
My solution was to give up using my M1 mac for development work. It sits on a desk as my email and music machine, and I moved all my dev work to an x86 Linux laptop. I'll probably drift back to my mac if the tools I need start to properly support Apple Silicon without hacky workarounds, but until GitHub actions supports it and people start doing official releases through that mechanism, I'm kinda stuck.
It is interesting how much impact GitHub has had by not having Apple Silicon support. Just look at the ticket for this issue to see the surprisingly long list of projects that are affected. (See: https://github.com/actions/virtual-environments/issues/2187)
-
Struggling to setup GithubAction with a .NET 4 app build
https://github.com/actions/virtual-environments/issues you can always request additional software to added to GitHub's machines, costs nothing to ask.
-
Any tool that can help me convert Azure ADO Pipelines to GitHub Actions YAML?
I'm not disputing your claim that it could be true as I say, it makes sense, there is even some evidence they are getting ready for feature parity as I said in my comment with the hosted agent builds but I am arguing the point with my "what aboutism" as it isn't clear.
-
Czkawka 4.1.0 - Fast duplicate finder, with finding invalid extensions, faster previews, builtin icons and a lot of fixes
Also Ubuntu 22.04 is not currently available on Github so I can't use CI for now - https://github.com/actions/virtual-environments/issues/5428
-
Emacs 28.1's been cut
As for M1 support, Iβm still waiting for GitHub to add M1-based GitHub Actions runners (issue).
-
Getting started with GitHub Actions and workflows
GitHub provides hosted runners which can run your workflow in different virtual environments. The "ubuntu-latest" environment already contains a recent version of Node.js which is ideal for testing JavaScript applications.
-
AzurePipeline failing due to: The reference assemblies for .NETFramework,Version=v4.6.1 were not found
As mentioned in this GitHub issue, the issue seems to affect only windows-2022 image. You can use the following script to install .NETFramework 4.6.1 to the agent.
runner
- 20-line PR to add key Docker feature to GitHub Actions, please upvote
-
Why the fuck are we templating YAML? (2019)
In the case of GitHub Actions, it's made more painful by the lack of support for YAML anchors, which provide a bare minimum of composability.
https://github.com/actions/runner/issues/1182
- please dont state this as a "workaround". your version simply "pretends" it is a tty when infact it is not an actual tty
-
PySide vs. .NET WinForms for a Desktop GUI App in 2023?
Even if you donβt pick Avalonia, their notes for Mac distribution look useful:
https://docs.avaloniaui.net/docs/distribution-publishing/mac...
For example, the GitHub actions runner itself is a modern .NET core project with CI except for .app packaging.
https://github.com/actions/runner/tree/main/.github/workflow...
-
GitHub Actions Are a Problem
This probably answers your question:
https://github.com/actions/runner/blob/a4c57f27477077e57545a...
-
DevOps CI/CD Quick Start Guide with GitHub Actions π οΈπβ‘οΈ
$ mkdir actions-runner && cd actions-runner $ curl -o actions-runner-osx-arm64-2.311.0.tar.gz -L https://github.com/actions/runner/releases/download/v2.311.0/actions-runner-osx-arm64-2.311.0.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 98.1M 100 98.1M 0 0 20.0M 0 0:00:04 0:00:04 --:--:-- 23.5M $ echo "fa2f107dbce709807bae014fb3121f5dbe106211b6bbe3484c41e3b30828d6b2 actions-runner-osx-arm64-2.311.0.tar.gz" | shasum -a 256 -c actions-runner-osx-arm64-2.311.0.tar.gz: OK $ tar xzf ./actions-runner-osx-arm64-2.311.0.tar.gz β― ./config.sh --url https://github.com/dpills/devops-quick-start-guide --token AGDCRGCMZWN34QIVISIO5XXXXXX -------------------------------------------------------------------------------- | ____ _ _ _ _ _ _ _ _ | | / ___(_) |_| | | |_ _| |__ / \ ___| |_(_) ___ _ __ ___ | | | | _| | __| |_| | | | | '_ \ / _ \ / __| __| |/ _ \| '_ \/ __| | | | |_| | | |_| _ | |_| | |_) | / ___ \ (__| |_| | (_) | | | \__ \ | | \____|_|\__|_| |_|\__,_|_.__/ /_/ \_\___|\__|_|\___/|_| |_|___/ | | | | Self-hosted runner registration | | | -------------------------------------------------------------------------------- # Authentication β Connected to GitHub # Runner Registration Enter the name of the runner group to add this runner to: [press Enter for Default] Enter the name of runner: [press Enter for dpills-mac] This runner will have the following labels: 'self-hosted', 'macOS', 'ARM64' Enter any additional labels (ex. label-1,label-2): [press Enter to skip] β Runner successfully added β Runner connection is good # Runner settings Enter name of work folder: [press Enter for _work] β Settings Saved. β― ./run.sh β Connected to GitHub Current runner version: '2.311.0' 2023-10-27 13:32:16Z: Listening for Jobs
-
Automate Flutter app delivery to AppCenter with GitHub Actions
A runner is where your action's jobs will be run. It can be a hosted virtual environment, or you can self-host a runner in your machine.
- GitHub Actions Frequently Failing
- Runners fail to set up job with tar -xzf error
-
How to deal with MSVC in DevOps
If i understand this writing correctly (https://github.com/actions/runner/issues/904), running Windows containers in a windows-latest GH Actions host is not possible. While using a self-hosted runner on a Windows server might be an option, this is not what I want since it is a package repo for a well-known open source project, think of the package repo part as a mini-Conan. I wouldn't know who would want to host that. In the best case we would stay with just GH Actions to keep everything confined in one space :)
What are some alternatives?
action-gh-release - π¦ :octocat: GitHub Action for creating GitHub Releases
act - Run your GitHub Actions locally π
azure-pipelines-agent - Azure Pipelines Agent π
widevine-l3-guesser
github-act-runner - act as self-hosted runner
SwagLyrics-For-Spotify - π Get lyrics of currently playing Spotify song so you don't sing along with the wrong ones and embarrass yourself later. Very fast.
mockoon - Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
UTM - Virtual machines for iOS and macOS
docker-github-runner-linux - Repository for building a self hosted GitHub runner as a ubuntu linux container
web-api - This issue tracker is no longer used. Join us in the Spotify for Developers forum for support with the Spotify Web API β‘οΈ https://community.spotify.com/t5/Spotify-for-Developers/bd-p/Spotify_Developer
duckduckgo-locales - Translation files for <a href="https://duckduckgo.com"> </a>