Dependency on Third-Party GitHub Actions

“GitHub Actions limitations and gotchas GitLab team-member here. Obviously coming in with a lot of bias, but I wanted to address how each point relates to GitLab CI&#x2F;CD’s view of the world. I’m also thinking about writing a longer post with more details as I have a lot of thoughts (™) about this topic.<p>2.1 Caching isn’t available: GitLab has this everywhere.<p>2.2 GitHub Enterprise Server is behind GitHub Enterprise Cloud: GitLab ships the same code to GitLab.com as it does to our self-managed customers. This was a tough decision but has a lot of benefits...the central being feature parity and scalability for self-managed folks<p>2.3 Using Public GitHub.com Actions: This is a symptom more than the problem itself - relying on third-party plugins for build jobs is scary, and leads to many of the same issues we’ve seen in the Jenkins ecosystem - easy to get started, hard to maintain.<p>2.4 Dockerhub pull rate limiting: for self-hosted runners, you can use a registry mirror or Dependency Proxy to reduce your number of pulls from Docker Hub. The key is the entire platform has to be there to enable the right workflows.<p>3.1 No dropdowns for manually triggered jobs: GitLab also doesn’t have drop downs, but does have the ability to pre-fill these values.<p>3.2 Self-hosted runner default labels: I think this is also more of a symptom than a problem. 3.3 Being able to tag and use runners for specific tasks is key - so I understand the frustration and we’ve spent a lot of time on this.<p>3.4 You can’t restart a single job of a workflow: You can do this with GitLab.<p>3.5 Slow log output: I haven’t seen this be a problem, and is a benefit of our scalability features being built into the self-managed code.<p>3.6 You can’t have actions that call other actions: There are lots of ways to relate pipelines (parent&#x2F;child, triggers. etc.) in GitLab.<p>3.7 Metrics and observability: The GitLab runner has Prometheus build in, and the dashboards we use to manage GitLab.com are partially public: <a href="https:&#x2F;&#x2F;dashboards.gitlab.com" rel="nofollow">https:&#x2F;&#x2F;dashboards.gitlab.com</a><p>3.8 Workflow YAML Syntax can confusing: This can be really hard to get right. I learned to stop worrying and love the YAML long ago, and I know we’ve got through a lot of iterations to try and get this right.<p>I&#x27;d love to know where folks think I got this assessment wrong. And is there value in writing more about it?<p>(edited for line spacing)”