Live data from Hacker News

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

github.blog

101–110 of 239 posts

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

#101
post #99

Lots of comments here about what this means for CircleCI. Found it interesting that CircleCI's CEO has a testimonial in the "What our community is saying" at https://github.com/features/actions : “CircleCI has been building a CI/CD platform since 2011, and GitHub has been a great partner. GitHub Actions is further validation that CI/CD is critical for the success of every software team. We believe that developers thr…

That's kind of a content-free statement, unfortunately.

Although it's possible they can successfully position themselves as the premium upgrade, it's hard to see how this isn't a threat to CircleCI.

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

#102

Earlier quoted context omitted.

GH Actions offers self-hosted agents too, that can be deployed in the VPC

Apparently it’s free if you have self hosted runners (makes sense).

That's going to hurt people like Buildkite (which we love).

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

#103
post #9

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.

Hey there, I’m the Director of Engineering at GitHub with the team working on Actions. We really wanted to get an extremely flexible and powerful SDLC automation platform into our users hands as fast as possible. To do that we borrowed some code and infra from Pipelines to be able to offer a rock-solid CI/CD to every developer on GitHub sooner, and to be able to scale out to 40 million developers. With hosted runners, you’ll be able to run your Actions builds in any cloud, or even on your own hardware; if you don’t want to set that up, builds run on VMs and containers in Azure by default. You can use Actions to deploy anywhere and we have AWS, Azure, and Google Cloud actions to enable you to get started right away. If you want to read up a bit more about our virtual environments as well as what powers our runners check, we have some of that info in our docs here: https://help.github.com/en/articles/virtual-environments-for....

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

#105

Earlier quoted context omitted.

Same as what you have to use in gitlab, for what that's worth. But it is interesting that their existing "main.workflow" file is in a different syntax. Ahh, now I see, support for the main.workflow syntax will be removed, and you must migrate: https://help.github.com/en/articles/migrating-github-actions...

That’s disappointing. The original Actions was amazing and much of that was the thoughtful main.workflow file. This feels like a regression. I’m not a yaml hater like many but main.workflow was clean, almost pleasant to use. It felt like it actually came from understanding developers.

I'm also disappointed, I liked using HCL for GitHub actions.

Did they get negative feedback from beta users?

Or is it related to the recent release of HCL2?

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

#106
post #83

Earlier quoted context omitted.

It's a horrible trend. CI should not be tied to version control. I mean we all have to deal with it now, but I'd much rather have my CI agnostic and not have config files for it checked into the repo. I've browsed through the article you linked to, one of the subtitles was "Realizing the future of DevOps is a single application". Also a horrible idea: I think it locks developers into a certain workflow which is hard…

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 fighting CI. So you can call me a devops guy by accident (turns out, that's a huge chunk of what I do as a CTO - remove obstacles by implementing and managing devops).

I think my ideal devops situation is the one where you start with a simple deployment script from your local machine when it's a one man show and then scale it to a large organization not by switching to a large piece of devops software, but by gradually adding pieces that you need as your team grows and requirements change. Exactly what happened to us and I think our devops workflow is really great and I'm very proud of it.

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

#107
post #97
post #91

Earlier quoted context omitted.

I'm an operations guy, but I think I have a different perspective. The developers I work with don't have to think about CI/CD, but the configuration still lives in the repo, I'm just a contributer to that repo like they are. Having CI configuration separate from the code sounds like a nightmare when a code change requires CI configurations to be updated. A new version of code requires a new dependency for instance, t…

I hear you. I thought about it and I think you need to reframe the problem. If a change in the application breaks your CI, it means you need to adjust the CI so it doesn't break when such changes are introduced. In my experience, these kinds of things happen very rarely.

In my experience maintaining an active project at a large enterprise, these kinds of things happen nearly daily. Sometimes I wake up and our EMEA team has merged in a change that requires a CI change as well, and they are able to self-service those through their PRs.

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

#108

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 market works.

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

#109
post #59

That’s awesome! I’ve always been a big fan of GitLab CI but I’ll have to take a look at this and see how it stacks up. Competition has proven to be good for the market of Git hosting platforms.

Wait, why’d I get buried for this one? I know it’s against guidelines to discuss karma but I am just genuinely puzzled and nobody left any comments.

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

#110

This "sounds" interesting, and I'd absolutely love to manage ci/cd in github. Can anyone point me to some clear docs or articles on its usage? The blog post and developer guide on actions reads like some hybrid of a marketing page and a plain index of terms. Most of the examples on workflows/actions documentation and the like are in HCL which is being deprecated.

THIS. I have yet to even be able to get "echo 'hello world'" running in a container. I want to love this but I cant figure out how to use the damn thing. I don't see any action in the visual builder to "run a shell command" or even access a "Linux container".
Post reply on HN