21–30 of 239 posts
Really interesting. My project just migrated to Azure DevOps and I noticed that their configuration file looks really similar. My suspicion is that Azure DevOps is backing GitHub CI/CD.
Anyone have thoughts on how this compares to e.g. Google Cloud Builder in terms of functionality? Being integrated into the GH backend seems like a big perk, rather than having to use webhooks for everything.
Seems like you can do things like build your Docker containers (https://developer.github.com/actions/creating-github-actions...).
One thing that's great about Gitlab is the Gitlab server/runner split, where you can run workers in your own VPC, but still use their hosted offering. This makes it easier to keep your deploy secrets (aka the keys to the kingdom) locked down, as they never leave your cloud provider.
I wonder what they'll offer for Github Enterprise. Especially for organisations that are using it on prem and would prefer not to use Azure for builds. Anyone know?
There are self-hosted Build agents and eventually this will become available inside GitHub Enterprise Server too (after it GA’s)
What's the typical latency for these kinds of features to arrive?
Is it official now that Github is becoming Gitlab? Does anyone know how they are going to bill for the compute used in the CI?
No doubt there will soon be a Gitlab blog post passive aggressively complaining about Github copying them again.
- Actions can fail, but still continue (more like an additional success/failure status)
- Manually triggered actions (maybe with parameters that need to be entered by the user)
- Artifacts attached to actions especially HTML reports (next to plain text, this is the universal output type for a lot of quality tools)
Really interesting. My project just migrated to Azure DevOps and I noticed that their configuration file looks really similar. My suspicion is that Azure DevOps is backing GitHub CI/CD.
It’s not backed by Azure DevOps, the infrastructure is different and maintained by GitHub. However, the underlying technology is based on the Azure Pipelines technology (a sort of fork).
Is it official now that Github is becoming Gitlab? Does anyone know how they are going to bill for the compute used in the CI?
Is it official now that Github is becoming Gitlab? Does anyone know how they are going to bill for the compute used in the CI?
The features page has a pricing table: https://github.com/features/actions It is totally free for public repos. For private repos: - Free accounts get 2000 free minutes - Pro accounts get 3000 free minutes - Team accounts get 10k free minutes - Enterprise accounts get 50k free minutes Additional runner minutes are: - Linux: $0.008 per min - Windows: $0.016 per min - macOS: $0.08 per min (yeah that's not a typo, it is…
I'm not sure if for large open source projects, these machines will be nearly enough to run the CI jobs.
The price for Linux seems quite steep when you compare with for example what you pay with GCP.
It will be interesting to see the Github security teams catching those "public" repos doing nasty stuff like mining crypto - even with hard timeouts on each job it will be cool to see how this plays out!
Earlier quoted context omitted.
There are self-hosted Build agents and eventually this will become available inside GitHub Enterprise Server too (after it GA’s)
> (after it GA’s) What's the typical latency for these kinds of features to arrive?