9 ms·
We use GitHub Actions to build GitHub
- ctvo 5y agoIs that why it's down all the time? bazing I'll show myself out.
- candiddevmike 5y agoHow does GitHub fix GitHub using GitHub when GitHub is down?
- incel 5y agoThey probably have some sort of development test server. That what I'd do.
- rvz 5y agoObviously they internally self-host a version of GitHub Actions to build GitHub itself. They know how unreliable it is to use the live version to do it.
- sdab 5y agoI don't know what github is doing here, but I've seen this antipattern quite a few times in production at some big name companies...
- watermelon0 5y agoMaybe they use GitHub Enterprise Server to host internal repositories?
- spartanatreyu 5y agoHuh, it just occurred to me that Stack Overflow would still have access to their own database and probably be able to run a copy of it locally. If Stack Overflow went down, they'd still be able to check Stack Overflow to fix their issue.
- botdan 5y agoStack Exchange (and by extension, Stack Overflow) publishes all their data (anonymized) for download and offline usage as part of the Archive.org project. If you wanted, you too could have a copy of it locally to search while the site is down. https://archive.org/details/stackexchange https://archive.org/details/stackexchange
- Rapzid 5y agoHot take; they don't use their security alerts to manage dependency vulnerabilities. Sorry, taking this on a tangent but the security alerts feature as integrated into the product is WAY less usable than other features, such as actions. Just off the top of my head: * No way to assign alerts to people * No free-form comments when dismissing alerts? * Old alerts re-open if a regression introduces the change back.. With no history on the alert to see why an "opened 6 months ago" alerts suddenly appeared * Alerts that can't have PR fixes opened because "The vulnerable package is no longer used"(paraphrasing) are still open.. Why? Such a lackluster area of the product it has me wanting to give Snyk(blarghh) another look or some other alternatives.
- danpalmer 5y agoI haven't used the security alerts, but isn't the idea that you open an issue and then track it there using the regular project management tools? > Snyk(blarghh) What's wrong with Snyk?
- asciimike 5y agoThat's how everyone does it today, but given that GitHub has an issues product, it really should be better integrated. The main issue is that issues are publicly viewable, while security alerts are only available to certain users (e.g. repo admins). Since repo owners of e.g. popular OSS repos might not want public issues around their security vulnerabilities, this isn't something that's been actioned. Should GitHub offer more granular permissions on issues to resolve this? Probably, but unfortunately that's reaching fairly deep into how GitHub works today. (Disclosure: former Dependabot PM, no longer at GitHub)
- asciimike 5y agoI don't think it's too hot a take, but it is incorrect. Dependabot Alerts (and Updates) are required on all internal services and folks use them (and provide similar feedback). Dependabot Alerts is working on some of these things, starting with e.g. https://github.blog/changelog/2022-02-08-dependabot-alerts-persisted-after-fix-now-one-per-advisory/ https://github.blog/changelog/2022-02-08-dependabot-alerts-p... I know that security alerts in general are working on ways of assigning alerts (or opening issues that reference those alerts)--hopefully this is something that will show up soon. (Disclosure: former Dependabot PM, no longer work at GitHub)
- danpalmer 5y agoI've used GitHub Actions quite extensively now, across infrastructure automation, Python CI/CD, and iOS CI/CD, and while not perfect, it's the best platform I've used for this stuff so far. Compared to Jenkins it needed far less maintenance. Compared to CircleCI it felt much easier to work with and to build reliable pipelines due to the locking primitives it provides, and compared to Semaphore I found it easier to understand how the pieces fit together. My criticism would mostly be about missing features, but the pace of development has been great and the only one I have left on my list is SSH debugging, which didn't end up being much of a blocker to our adoption anyway. As for reliability, nothing is perfect, but in my experience it's at-or-above the level that CircleCI provided, and far surpassed our in-house Jenkins server.
- judge2020 5y ago> My criticism would mostly be about missing features, My only real requested feature is one that's been open since early 2020 (this issue replaced the old 2020 issue) and has the status "Status: Q1 2022 – Jan-Mar" https://github.com/github/roadmap/issues/161 https://github.com/github/roadmap/issues/161 Without this, i'm relying on Azure actions to start/stop+deallocate a self-hosted runner, which adds ~1 minute to the job startup time.
- ethomson 5y agoThanks for the feedback! I'm one of the PMs for GitHub Actions, and I appreciate this. Thinking about Actions as a set of primitives that you can compose is very much how I think about the product (and I think the other PMs as well) so I'm glad that resonates. We're always welcome to feedback, and we're continuing to invest and improve on the product, so I'm hopeful that we can address the features that you're missing.
- newman314 5y agoHere's my ask: * Setting up GHA is still a lot of "commit and hope for the best". I've resorted to having a sandbox repo just for experimentation/testing so that I don't overly pollute repos that I actually care about. It would be great to get more instrumentation to see what is going on. * I have a monorepo for Dockerfiles. It's quite annoying that I have to have separate invocations for different Dockerfiles in dependabot.yml. I should be able to specify /Dockerfile or /Dockerfile* as patterns for detection. The Dependabot invocation for GitHub Actions is a single entry and it would be great to have that. * I quite like Step Security's Harden Runner but it does require more work/invocations to get this set up. Maybe GH can work with them to more closely incorporate said functionality? * Make the cache bigger? I build a fair number of multi-arch containers and starting all of them at once tends to blow out the cache. * Given the interest around sigstore and SBOMs, maybe incorporate native capabilities to sign artifacts and generate SBOMS?
- deleted 5y ago[deleted]
- stickfigure 5y agoGitHub Actions has a lot of basic usability issues, none of which are fatal but all of which irritate me on a daily basis. Let's start with the first and simplest: Why did my build fail? You'd think this should be front and center. Yet, the UX is "click through a couple links, then wade through thousands of lines of log output". In practice this is "download the logs and grep them for text strings like FAILURE". The only way we've made this livable is by writing action code that sends test failures to a slack channel, and more or less ignoring the GitHub UI. Second usability issue: Restarting a build. Happens all the time because of some flakey third-party service. It's pretty much my primary interaction with the GitHub Actions UI. 1. Click on build name 2. Click on "Re-run jobs" which brings down a dropdown menu 3. Click on "Re-run failed jobs" menu item 4. Click on "Re-run jobs" button on the confirm dialog Seriously, after five times going through this flow I'm screaming for a JUST RERUN THE FUCKING JOBS ALREADY button. What's annoying is that this used to be better - the dropdown and confirm dialog are recent additions. The UX is degenerating. The irony is that we migrated from CircleCI because they were screwing up their UX, and we figured GitHub would make something better... sigh.
- saurik 5y agoFWIW, while the UI for re-running jobs used to be better, the result was a LOT worse as it would re-run all the jobs instead of just the failing ones, so I am still MUCH happier with the new flow ;P.
- longcommonname 5y agoFor the majority of my pipelines I rerun from the start. The pipeline itself is idempotent, I don't care about each step and I much rather have a clean run than a fast run.
- booi 5y agoI feel like those are not mutually exclusive. The button could say "Rerun failed jobs" no confirmation with a small ▼ next to it that has the other "rerun all jobs" drop down.
- lloydatkinson 5y ago" Turn weekly team photos into GIFs and upload to README" Well, as a remote worker that has my camera off as much as possible out of principle I'd really hate this. It actually puts me off applying knowing glimpses of my home get turned into GIFs for the entire company to see.
- bbrree66 5y ago
- lloydatkinson 5y ago
- glouwbug 5y agoI wonder if JIRA uses JIRA to track itself
- and0 5y agoThey do, actually! All of the public help requests and feature suggestions have been in Jira since, like, the early 00s. It's weird to see when they pop up in Google results with ancient screenshots attached.
- DoctorDabadedoo 5y agoAnd it's still awful.
- Dachande663 5y agoWe switched to buddy.works[0] about a year ago and honestly it’s just been… smooth. The UI is just great, the wealth and breadth of options is ever increasing and all the basics like knowing what went wrong, restarting, debugging, duplicating etc just work as you’d expect. One of the few companies I can recommend. [0] https://buddy.works https://buddy.works
- manigandham 5y agoI also highly recommend Buddy. It's the most intuitive build system I've found: every step in the pipeline is a container image and commands on top. Incredibly flexible and powerful but also easy to maintain.
- nimbius 5y agonot to sound snarky, but what are you doing to address the 34 incident outages in the past 90 days? i feel like theres been no real update on this slow rolling disaster. we're not even a week into april and already a 5 hour outage in codespaces.
- uuyi 5y agoThis is my biggest concern. The more we centralise on GitHub, the more we centralise the risk on a service which goes down harder and more often than our Jenkins infrastructure did.
- yowlingcat 5y agoI've had multiple meetings with my team in the past month about what our contingency plan is for moving off GH if need be. It's gotten that bad. So far, we've gotten to "well I guess GitLab is available and we can put it behind a VPN" and punted on talking about it any further. But I'm curious about what others think.
- ewhauser421 5y agoIt's weird to me that GitHub doesn't have larger machines types available for actions yet. I don't want to bother with a self-hosted runner just to get more CPUs. They have much larger machines available for Codespaces - why not actions? I'm happy to pay for them.
- thinkafterbef 5y agoHey founder of BuildJet here, With BuildJet for GitHub Actions, you can get up to 64 vCPU as a GitHub Actions runner. We plug right into your existing setup and have a significantly higher per core performance compared to the native runner. Check us out here: https://buildjet.com/for-github-actions https://buildjet.com/for-github-actions
- otterley 5y agoAny arm64 resources in the works?
- white_dragon88 5y ago[dead]
- hayd 5y agoI this is in preview, I've seen it in a few projects (ubuntu-latest-xl), so perhaps we'll see wider release soon?
- dudeinjapan 5y agoGithub Actions folks if you're listening, please address lack of "Allow Failure" modifier for job runs. There is a reason every other CI on the planet has this, and no, it's not the same as "Continue on Error" https://github.com/actions/toolkit/issues/399 https://github.com/actions/toolkit/issues/399 (currently 800+ upvotes and counting)
- ossusermivami 5y agoAs someone who has been working with apis from all the major git platforms, i find the Github api the most complete and most featureful to work with.. As an example not having Gitlab apps the same way Github apps has it is a bit of a disapointment for me since i generally like gitlab as company
- WhyNotHugo 5y agoIn other news, Mercedes executives drive Mercedes cars.
- onionisafruit 5y agoIt’s not even that. GitHub still uses Jenkins internally to build and deploy their rails monolith.
- emsy 5y agoHow Github uses Github (Actions) to build Github. Yes I'm this old.
- rsclarke 5y agoI've been capturing a list of GitHub Actions gotchas; 1. If you reference an environment in a build step, this causes an `on: deployment` event trigger. This is not intuitive. 2. Environments with deployment protection rules are just for branches. Using tagged releases for a production environment means we must allow all branches to be deployed to that environment. 3. Workflows are unable to start other workflows to prevent cyclic actions. Understandable, there are exceptions however e.g (1) above. 4. Pull requests raised by Dependabot will not have the `id-token: write` permission needed to create an OIDC ID token that we use to access external systems (the benefit of then not having to manage secrets). Note: Using `on: pull_request_target` will be granted the permission but then you're executing the `main` branch and not building/testing the Dependabot changes. Then we have secrets, Organisation, Repository, Environment and Dependabot. Anything in Organisation, Repository or Dependabot should really be at most read only permissions. Environment based secrets may have write permissions but be wary of the malicious PR that then references this environment, what protections are in place? Environment approval? Deployment branch protection?
- OutsmartDan 5y agoI’m trying to love GitHub Actions, however, when builds and tests randomly fail on custom runners when they’re configured the exact same and there’s no option to debug, it becomes painstakingly frustrating. We’ve tried most of the big CIs, Travis/CircleCI/codeship- and while GH Actions integrates nicely with GitHub itself, it’s a far less superior product compared to its peers.
- kingabc 5y ago[flagged]
- ogazitt 5y agoWe have based our entire deployment pipeline on GHA. Works great when it works... and after all the outages of the past month, we're working on an exit strategy.
- manwe150 5y agoIf anyone at GHA is reading comments, could you pressure your upstream VM hosts to all allow ‘rr’ (Mozilla record and replay) usage? They must enable performance measurement counters (PMU), but it is game-changing to be able to use CI not only to detect issues, but also exactly reproduce rare bugs by simply downloading an exact replay of the exact steps that led to it. We currently use self-hosted buildkite and buildbot runners specifically because we can enable the required performance counters, and temporarily save every run as an rr file so any result can be reproduced locally and investigated. To quote an old post by the program author for more specifics: https://news.ycombinator.com/item?id=23076703 https://news.ycombinator.com/item?id=23076703
- mostertoaster 5y agoI’m probably just slow, but are they trying to say this is analogous to “the compiler is written in the language it compiles”?
- runeks 5y agoI love everything about GitHub Actions except that there’s no official tool to run them locally.
- xcambar 5y agoI never understood this state of things as well. Additionally, I can't picture a rationale for this decision, coming from Github.
- oxff 5y agoI prefer CircleCI over GitHub Actions.
- donatj 5y agoI wish GitHub Actions worked more like Drone. Just run commands in specified Docker containers. None of this weird probably dangerous in-channel signaling via STDOUT. Completely skip the base level OS with a billion tools people might want pre installed that shifts over time, that’s just asking for your build to break while you’re on vacation. It’s a very Microsoft way to do it. It’s messy. I know GitHub Actions has a built in opinion to kinda run like that, but I have had a ton of problems with permissions in that mode and it incurs an unavoidable 30 second overhead as it sets up Docker, every single time. Which for a 2 second unit test suite is an eternity. I loved Drone CI when it was OSS. I contributed to Drone, I loved Drone with my whole heart. Drone stopped loving me; they pulled the rug out from under me, made my contributions non-free, and charged more than me and my company could possibly justify to use my own contributions. I learned the valuable lesson of why you don’t want to sign a CLA the hard way. I am using GitHub Actions and I am not particularly happy about it. GitHub Actions: “It’s better than Jenkins and about on par with Travis”
- Bennett121 5y ago[flagged]
- Bennett121 5y ago[dead]