5 ms·

At my project we are forced to use Enterprise GitHub including Actions. Often 80% of the build time consists of up- or downloading intermediate or final build a

At my project we are forced to use Enterprise GitHub including Actions. Often 80% of the build time consists of up- or downloading intermediate or final build artifacts. This can take more than 40 minutes which is extremely painful. I was really looking forward to finally getting a speedup here. The promise: > GitHub Actions: Artifacts v4 available in GitHub Enterprise Server #930 … We will be extending support for v4 of the actions to upload and download artifacts to GitHub Enterprise Server (GHES). This new version improves artifact upload and download speeds by up to 98%. I don‘t understand at all how this is not a priority anymore. :-(

jmainguy 2y ago
I believe the future is GitHub enterprise cloud. https://docs.github.com/en/enterprise-cloud@latest/admin/overview/about-github-enterprise-cloud https://docs.github.com/en/enterprise-cloud@latest/admin/ove... all the benefits of GitHub enterprise, with none of the cons
- richbell 2y ago
  > all the benefits of GitHub enterprise, with none of the con To some organizations, having to use a cloud SaaS instead of hosting the application on-prem is a con.
  - btreecat 2y ago
    Isn't that the value GitLab is trying to provide?
    - richbell 2y ago
      Perhaps. The point remains that GitHub currently offers a self-hosted solution (GitHub Enteprise Server), and saying that the cloud version is the exact same (no cons) isn't true.
theamk 2y ago
Why bother with Github Artifacts at all, especially for intermediate steps? At our self-hosted GHE instance, we use either (self-hosted) Artifactory, or raw S3. Fast, and easy to work with.