4 ms·

GitHub Actions is such a pain to use just because of how sluggish it feels. I hope they’ll improve performance.

• Roark66 1y ago
  We used to use bitbucket Web hooks that used to trigger Jenkins jobs. This was almost instant. Now after migrating to GH actions it can take minutes before jobs start on push for example...
  • simooooo 1y ago
    How big are these jobs? I’ve never seen an action take more than 15s to start
• blibble 1y ago
  > I hope they’ll improve performance. it's Microsoft, so the answer is: buy a new computer (which comes with a bundled Windows license)
  • futurecat 1y ago
    yeah I'll keep my M3
  • layer8 1y ago
    We are at a point where buying a new computer doesn’t actually help.
• wheybags 1y ago
  It also continuously fails to scroll down in the log view when watching output of a ci job live, and has done for years. It's so annoying that I made a userscript to force scrolling: https://github.com/wheybags/userscripts/blob/main/github_actions_scroll_down.js https://github.com/wheybags/userscripts/blob/main/github_act...
  • futurecat 1y ago
    I feel you. The UX is a gigantic mess. Navigating between jobs and builds is also a terrible experience.
    • wheybags 1y ago
      Oh man. Start a manual job, wait for it to appear in the UI. 10 minutes later, it finally appears. Or just refresh the page manually immediately after starting the job, and there it is...