{"id":245657,"date":"2026-02-10T16:29:42","date_gmt":"2026-02-10T16:29:42","guid":{"rendered":"https:\/\/www.travis-ci.com\/?p=245657"},"modified":"2026-02-10T17:28:46","modified_gmt":"2026-02-10T17:28:46","slug":"bring-your-own-environment-introducing-customized-images-for-linux","status":"publish","type":"post","link":"https:\/\/www.travis-ci.com\/blog\/bring-your-own-environment-introducing-customized-images-for-linux\/","title":{"rendered":"Bring Your Own Environment: Introducing Customized Images for Linux"},"content":{"rendered":"\n<p>We begin 2026 with the introduction of a new feature &#8211; Customized Images for Linux builds. Any user who has had to update our default images knows how cumbersome and expensive it is to spend the first 2-3 minutes downloading additional libraries for each build. Travis CI has always striven for maximum flexibility and user convenience, so we expect that the introduction of the Customized Images feature will certainly have a positive impact on your workflow.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"feature\">What is this Feature?<\/h2>\n\n\n\n<p>You can use Travis CI to modify standard Linux build environment images by creating a specific build recipe using a .travis.yml file. Such images are stored within the Travis CI infrastructure.<\/p>\n\n\n\n<p>A list of such images will be available to Travis CI end-user account administrators the Travis Web UI, so you can review and delete obsolete or unnecessary customized images (controlling the cost).<\/p>\n\n\n\n<p>You can use these customized images by specifying their identifiers in regular build recipes; once called that way, they will be used as build environments.<\/p>\n\n\n\n<p>Custom image sizes stored on Travis CI will be billed at a rate of credits per GB of storage space.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"561\" src=\"https:\/\/www.travis-ci.com\/wp-content\/uploads\/2026\/02\/image-1024x561-1.png\" alt=\"\" class=\"wp-image-245658\" srcset=\"https:\/\/www.travis-ci.com\/wp-content\/uploads\/2026\/02\/image-1024x561-1.png 1024w, https:\/\/www.travis-ci.com\/wp-content\/uploads\/2026\/02\/image-1024x561-1-300x164.png 300w, https:\/\/www.travis-ci.com\/wp-content\/uploads\/2026\/02\/image-1024x561-1-768x421.png 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"Built\">Why We Built It<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Modern Dev teams need specialized environments.<\/li>\n\n\n\n<li>This feature allows users to modify these build environments without waiting for official build environment updates, while optimizing build times.<\/li>\n\n\n\n<li>It gives users control over specific operating-system-level build-environment settings, which is typically not possible or costly in terms of build execution time when using default build environments.<\/li>\n\n\n\n<li>Users can create custom Linux images based on their requirements. They need a small subset of tools.<\/li>\n<\/ul>\n\n\n\n<p><strong>Key Benefits&nbsp;<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Speed &#8211; experience a reduction in build setup time; no more repetitive install steps.<\/li>\n\n\n\n<li>Consistency &#8211; parity between a developer&#8217;s local and the CI environment.<\/li>\n\n\n\n<li>Security &#8211; increase security by using your own &#8220;hardened&#8221; images that meet internal compliance standards.<\/li>\n<\/ul>\n\n\n\n<p>For more details on using Customized Images, please visit <a href=\"https:\/\/docs.travis-ci.com\/user\/build-custom-images\/\">https:\/\/docs.travis-ci.com\/user\/build-custom-images\/<\/a>.<\/p>\n\n\n\n<p>Happy building!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>We begin 2026 with the introduction of a new feature &#8211; Customized Images for Linux builds. Any user who has had to update our default images knows how cumbersome and expensive it is to spend the first 2-3 minutes downloading additional libraries for each build. Travis CI has always striven for maximum flexibility and user [&hellip;]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_breakdance_hide_in_design_set":false,"_breakdance_tags":"","footnotes":""},"categories":[27],"tags":[],"class_list":["post-245657","post","type-post","status-publish","format-standard","hentry","category-educations"],"_links":{"self":[{"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/posts\/245657","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/comments?post=245657"}],"version-history":[{"count":4,"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/posts\/245657\/revisions"}],"predecessor-version":[{"id":245665,"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/posts\/245657\/revisions\/245665"}],"wp:attachment":[{"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/media?parent=245657"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/categories?post=245657"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.travis-ci.com\/wp-json\/wp\/v2\/tags?post=245657"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}