--- title: Why Did Our GitHub Actions Builds Get Slower After... description: A discussion asking why CI/CD builds slowed down after migrating from Jenkins to GitHub Actions, pointing to Docker layer caching issues on fresh GitHub-hosted... canonical: https://daily.dev/posts/why-did-our-github-actions-builds-get-slower-after-leaving-jenkins--2k2fq0ycm twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Why Did Our GitHub Actions Builds Get Slower After Leaving Jenkins? | daily.dev og:description: A discussion asking why CI/CD builds slowed down after migrating from Jenkins to GitHub Actions, pointing to Docker layer caching issues on fresh GitHub-hosted... og:url: https://daily.dev/posts/why-did-our-github-actions-builds-get-slower-after-leaving-jenkins--2k2fq0ycm og:image: https://api.daily.dev/og/posts/2K2Fq0YCm.png og:image:alt: Why Did Our GitHub Actions Builds Get Slower After Leaving Jenkins? og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Why Did Our GitHub Actions Builds Get Slower After Leaving Jenkins? **[DevOps & Platform Engineering Hub](https://daily.dev/sources/sanjay)** · [@divyansh30](https://daily.dev/divyansh30) · 1 min read · 4 upvotes · 0 comments ## Summary A discussion asking why CI/CD builds slowed down after migrating from Jenkins to GitHub Actions, pointing to Docker layer caching issues on fresh GitHub-hosted runners as a likely culprit. The poster asks the community about their experiences with runner choice (hosted vs self-hosted) and caching strategies, and links to a write-up covering fixes using self-hosted runners and shared Docker caching. ## Content Moving from Jenkins to GitHub Actions doesn't automatically mean faster builds. One thing that can make a big difference is Docker caching. With fresh GitHub-hosted runners, the cache isn't always there for the next job, so builds can end up pulling and rebuilding the same layers again. I'm curious how other DevOps teams handle this: - Did your builds get faster or slower after moving from Jenkins to GitHub Actions? - How are you handling Docker layer caching? - Are you using GitHub-hosted or self-hosted runners? - What made the biggest difference to your build times? I came across a practical write-up about fixing slow builds after a Jenkins-to-GitHub Actions migration using self-hosted runners and shared Docker caching. [https://www.kubeblogs.com/fixing-slow-ci-cd-pipelines-after-migrating-from-jenkins-to-github-actions/](https://www.kubeblogs.com/fixing-slow-ci-cd-pipelines-after-migrating-from-jenkins-to-github-actions/) Has anyone else run into this after migrating CI platforms? #DevOps #CICD #GitHubActions #Jenkins #Docker #PlatformEngineering ## Similar posts on daily.dev - [GitHub Actions Is Slowly Killing Your Engineering Team](https://daily.dev/posts/github-actions-is-slowly-killing-your-engineering-team-l0ni7jj2k) · Lobsters · 0 upvotes · 0 comments - [GitHub Status](https://daily.dev/posts/github-status-rbmhgeg1f) · Hacker News · 6 upvotes · 1 comments - [Reduce GitHub Actions runner CPU usage](https://daily.dev/posts/reduce-github-actions-runner-cpu-usage-sqgbskprc) · Meziantou · 0 upvotes · 0 comments --- Tags: [#docker](https://daily.dev/tags/docker), [#cicd](https://daily.dev/tags/cicd), [#github-actions](https://daily.dev/tags/github-actions), [#jenkins](https://daily.dev/tags/jenkins) [View this post on daily.dev](https://daily.dev/posts/why-did-our-github-actions-builds-get-slower-after-leaving-jenkins--2k2fq0ycm) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/why-did-our-github-actions-builds-get-slower-after-leaving-jenkins--2k2fq0ycm","headline":"Why Did Our GitHub Actions Builds Get Slower After Leaving Jenkins?","text":"A discussion asking why CI/CD builds slowed down after migrating from Jenkins to GitHub Actions, pointing to Docker layer caching issues on fresh GitHub-hosted runners as a likely culprit. The poster asks the community about their experiences with runner choice (hosted vs self-hosted) and caching strategies, and links to a write-up covering fixes using self-hosted runners and shared Docker caching.","url":"https://daily.dev/posts/why-did-our-github-actions-builds-get-slower-after-leaving-jenkins--2k2fq0ycm","datePublished":"2026-08-18T03:50:34.460Z","dateModified":"2026-09-13T20:49:08.137Z","author":{"@type":"Person","name":"Divyansh","url":"https://daily.dev/divyansh30","image":"https://media.daily.dev/image/upload/s--f9lbkpFv--/f_auto/v1744873189/avatars/avatar_JMQ4qarKTe7zPurSPRrzM","description":"Aspiring engineer with an interest in AI, tech and DevOps :)","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":1050}},"image":"https://media.daily.dev/image/upload/s--TPLw7ekc--/f_auto/v1787025034/posts/2K2Fq0YCm?_a=BAMAMicg0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":4},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/squads/sanjay","name":"DevOps & Platform Engineering Hub"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"DevOps & Platform Engineering Hub","item":"https://daily.dev/squads/sanjay"},{"@type":"ListItem","position":3,"name":"Why Did Our GitHub Actions Builds Get Slower After Leaving Jenkins?"}]} ```