Live data from Hacker News

GitHub Actions now supports CI/CD, free for public repositories

github.blog

121–130 of 239 posts

Re: GitHub Actions now supports CI/CD, free for public repositories

#121

This is very interesting to me. It also makes me think about the natural rise of monopolies and monoculture in tech. GitHub has really been extending to "eating the world" as of late. Recently in terms of their package registry that must have folks like Artifactory and Nexus a bit shaken, and now this, which is bad news for folks like CircleCI (and I say this as a CircleCI user). As a developer, in the short term I l…

Are there "bridges" (apart from Git itself) between GitHub, Gitlab, etc? Such could help to mitigate a vendor lock-in.

Re: GitHub Actions now supports CI/CD, free for public repositories

#122

I really want to try GitHub Actions but I signed up as soon as it was released and I am still waiting for an invite. I am mostly just excited for it to be released so I can try it.

Hi! I just looked and we can't find you on the beta list, for some reason. Sign up and then DM me when you have (@_clem).

Re: GitHub Actions now supports CI/CD, free for public repositories

#123
post #115

You lost me at YAML..

Hi I'm an engineer on Actions, and a few months ago I probably would have said the same thing, but I've come around to it (and then some). We spent a ton of time working through the syntax changes in HCL, YAML, and other languages. What we found was that while HCL and other languages are amazing for expressing pure configuration, software development lifecycle and continuous integration workflows are a blend of confi…

Did you evaluate TOML and if so, what were the drawbacks you identified for the workflow use case?

Re: GitHub Actions now supports CI/CD, free for public repositories

#124

Earlier quoted context omitted.

A monopoly is not inherently bad. They often benefit users with increased efficiency and productivity. They're only bad when progress stagnates and/or prices rise. In this case, Github is actively competing and adding features that helps all of their users. If that means that some other companies lose market share then it's just a sign that the value proposition has changed. I see no problem with this, it's how the m…

In what real scenario do you see a monopoly not doing exactly what monopolies do? Do they have some moral code they can't break? Do they hate money? What exactly is it that would make them immune to human tendencies?

Github is an example.

Re: GitHub Actions now supports CI/CD, free for public repositories

#125
post #106

Earlier quoted context omitted.

Why it's horrible? Technically, version control lends itself naturally as part of the now well-accepted infrastructure-as-code mantra. Operationally, version control is the one that developers interfacing most primarily, shifting the interactions to that interface would be benefitical to users. Of course, DevOps as a skill set is becoming less and less relevant, given the increasingly integrated toolings that interfa…

So, it's a very interesting situation. On one hand, I agree with you: when I start a new project, I am the master of it, I take care of everything and I need to make sure deployment and testing are implemented as early as possible. But this needs to scale. When we hired more people, I quickly realized no one wanted to deal with CI. They wanted it to just work and I wanted people to work on features and bugs, not figh…

I'm interested to know how many different teams use your CI system, as well as how many different platforms (operating system, distro, programming language) you support.

Some companies have tons of old and new projects with very heterogeneous technologies in use. Imagine 50+ teams, several different programming languages, and things being deployed to different "hardware" (bare metal, cloud VMs, kubernetes, etc). It just seems like a lot of work to manage CI configs for all those different teams/cases, handle "support" requests from different teams, fix issues, and so forth. Hence, why the "easy way" out is to have each team manage CI configuration themselves as much as possible, to spread the maintenance cost across many capable developers.

Re: GitHub Actions now supports CI/CD, free for public repositories

#127

This is very interesting to me. It also makes me think about the natural rise of monopolies and monoculture in tech. GitHub has really been extending to "eating the world" as of late. Recently in terms of their package registry that must have folks like Artifactory and Nexus a bit shaken, and now this, which is bad news for folks like CircleCI (and I say this as a CircleCI user). As a developer, in the short term I l…

A monopoly is not inherently bad. They often benefit users with increased efficiency and productivity. They're only bad when progress stagnates and/or prices rise. In this case, Github is actively competing and adding features that helps all of their users. If that means that some other companies lose market share then it's just a sign that the value proposition has changed. I see no problem with this, it's how the m…

> A monopoly is not inherently bad. They often benefit users with increased efficiency and productivity. They're only bad when progress stagnates and/or prices rise.

My argument is every single monopoly eventually becomes 'bad' and makes progress stagnate and prices rise.

Just look at Google and Amazon. Up until I'd say late-ish 00s, nearly everyone loved Google and Amazon. I remember when Google search, GMail, Maps, street view, etc. first came out. I loved them, and I felt they were so much better than the competition. Same thing with Amazon - their selection was huge, great delivery and customer service.

I still use Google and Amazon for so much, but it's usually with reluctance and distaste. Check out Google search results these days. The ENTIRE first page about half way past the fold is ads, or AMP carousels, or shit I just want to get out of my way. But I still use them because with their heft and scale no one does long tail searches as comprehensively.

Re: GitHub Actions now supports CI/CD, free for public repositories

#128

Earlier quoted context omitted.

A monopoly is not inherently bad. They often benefit users with increased efficiency and productivity. They're only bad when progress stagnates and/or prices rise. In this case, Github is actively competing and adding features that helps all of their users. If that means that some other companies lose market share then it's just a sign that the value proposition has changed. I see no problem with this, it's how the m…

In what real scenario do you see a monopoly not doing exactly what monopolies do? Do they have some moral code they can't break? Do they hate money? What exactly is it that would make them immune to human tendencies?

Monopolies are subject to the laws of economics.

GitHub has gained near-monopoly status because it has provided a superior user experience at a great price. If either of those value propositions start to crumble,

  git remote add ...
Exploitative monopolies almost always have help from the state: The Patent Office, Interstate Commerce Commission, Federal Reserve, FDA, etc either grant monopoly or cartel privilege to their customers. Monopolies achieved on the market cannot be sustained without continuing to satisfy customer demands.

Re: GitHub Actions now supports CI/CD, free for public repositories

#129
post #77
post #73

Earlier quoted context omitted.

That sounds a bit like Github Pages which has been a thing for a while.

Sure, if your site is solely static content, which is all GitHub pages supports. You can’t run “production code”. I know some people use the service with a static site generator as a free way to host a blog, but it’s not really the same thing at all.

The actual equivalent would be something like Azure AppService.

Re: GitHub Actions now supports CI/CD, free for public repositories

#130
post #61

Earlier quoted context omitted.

I think a good strategy for Microsoft would be to reuse as much as possible CI/CD code from github in Azure devops. Azure devops probably doesn’t need to be as flexible as long as it is robust and just works. Github will probably be the place where experiments can happen.

Azure Pipelines is currently considered the best CI/CD solution. (For example see GitLab issues about how users would like GitLab to improve theirs.)

Last time I checked Azure Pipelines still doesn't have build caching

https://developercommunity.visualstudio.com/content/idea/365...

F.S. I work for Codefresh a CI/CD solution

Post reply on HN