Live data from Hacker News

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

github.blog

111–120 of 239 posts

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

#111
post #83
post #2

This is great news for developers. The trend has been to combine version control and CI for years now. For a timeline see https://about.gitlab.com/2019/08/08/built-in-ci-cd-version-c... This is bad news for the CI providers that depend on GitHub, in particular CircleCI. Luckily for them (or maybe they saw this coming) they recently raised a series D https://circleci.com/blog/we-raised-a-56m-series-d-what-s-ne... and…

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…

Even if code and deployment config are different (and managed by different teams), there's no reason why they cant be stored in the same repo.

Where else would you put these configs?

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

#112
post #48

I do not understand why Microsoft finances this. I understand the hosting as a specialized social platform, but GitHub Actions vs. Azure DevOps Pipelines are a duplicated effort. Better integration for GitHub for the Azure DevOps suite would solve that in a similar way without duplication of capabilities.

I think (hope) they intentionally avoid tight integration with Microsoft branded stuff. Even at the slightest indication of such a thing happening, I bet it would lead to an exodus and outrage among developers, however irrational that might be.

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

#113
post #97

Earlier quoted context omitted.

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.

I'll give you a counter example: whenever I change CI workflow for something that has nothing to do with the repo - like a new deployment scheme to staging - I have to go and ask people to merge/rebase from master into their branches or they won't be able to deploy. It happens pretty often and I'd rather avoid this.

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

#114
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…

Even if code and deployment config are different (and managed by different teams), there's no reason why they cant be stored in the same repo. Where else would you put these configs?

Into a separate repo. See my other reply: https://news.ycombinator.com/item?id=20647649

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

#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 configuration and pseudo-scripting, and we were only able to come up with a clean syntax for this in YAML.

For example, although HCL supports heredocs, we felt that they suffered from readability problems versus multi-line strings in YAML when you're just trying to read through a workflow file and see what it does.

There are many, many other reasons we felt that YAML was actually the right choice, and I'm optimistic others will come around to it in the same way I have.

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

#116
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…

Why devops, if everything can be deved? If the dev experience is good enough, do anyone needs ops?

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

#117

Earlier quoted context omitted.

It didn't take long. https://about.gitlab.com/2019/08/08/built-in-ci-cd-version-c...

I really love running gitlab on premise and I really love their CI/CD etc, but these kind of posts don’t do their great product any favor. They should put that kind of energy into creating teaching content.

Hopefully Gitlab will learn that a bullet list of features can only take them so far. If (probably when) Github matches their feature set, the most stable product automatically wins. ("breadth over depth" as a strategy assumes a false dichotomy)

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

#118
post #26

I couldn't quickly find out if these features are now supported but what I really want is: - 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)

Hi, GitHub Actions product manager here.

Thanks for your interest in GitHub Actions. You can set a property `continue-on-error: true` for each step and the runner will ignore a failed result and continue the workflow. For more details on workflow configuration please see https://help.github.com/en/articles/workflow-syntax-for-gith...

Workflow runs can be triggered via a `repository_dispatch` event with a custom payload. Using this model you could create a tool to allow for manual triggering. However, we do expect to provide a more integrated experience for triggering manual runs with custom inputs.

More capabilities for actions to post artifacts and reports as part of our experience is absolutely on our radar.

We are working to bring as many new users into the beta as quickly as we can and we look forward to your feedback.

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

#119

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.

Once you’re in the beta, you’ll be able to get started by picking from a varying list of templates. In the meantime, those templates are actually hosted here: https://github.com/actions/starter-workflows. Depending on what you’re interested in setting up, this page might be helpful in getting started. https://help.github.com/en/categories/automating-your-workfl...

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

#120

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…

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?
Post reply on HN