Containerized build
Download as PPTX, PDF0 likes34 views
The document discusses containerized builds and build scripts. It describes how builds are typically done without scripts by listing out build steps manually. Using build scripts encapsulates these steps, making builds more repeatable, portable, and faster. Containerized builds further improve on this by putting each build step in a Docker container for isolation. Benefits include repeatable environments, ability to go back in time to older builds, faster ramp up for new team members, and simplifying infrastructure. The document provides examples of Docker multi-stage builds and caching to improve build speeds and common issues to watch out for like line endings and file paths.
Containerized build
- 1. Containerized Build BUILDING YOUR CODE USING CONTAINERS….AND SOME SCRIPTS HO PENG FOONG
- 2. Build Steps Compiler Code Quality tools Testing Tools Package Manager Other Tools How a build looks like now (usually) Environmental Dependencies
- 3. How a build looks like now (usually)
- 4. How a build looks like now (usually) Build Steps Compiler Code Quality tools Testing Tools Package Manager Other Tools Build Steps Compiler Code Quality tools Testing Tools Package Manager Other Tools Build Steps Compiler Code Quality tools Testing Tools Package Manager Other Tools
- 5. Build Script Compiler Code Quality tools Testing Tools Package Manager Other Tools How a build looks like with build scripts
- 6. Build Script Compiler Code Quality tools Testing Tools Package Manager Other Tools Build Script Compiler Code Quality tools Testing Tools Package Manager Other Tools Build Script Compiler Code Quality tools Testing Tools Package Manager Other Tools How a build looks like with build scripts
- 7. Build Script Compiler Code Quality tools Testing Tools Package Manager Other Tools How containerized build looks like
- 8. Advantages of containerized build ◦ Repeatable builds ◦ Less of “build works on my machine” scenarios ◦ Environment is versioned controlled. Can go back in time to build older versions. ◦ Faster ramp up for new team members. ◦ Can ask new team members to code with only Notepad & Docker 😎 ◦ Simplify IT infrastructure work. Less variants of build agents. ◦ Portability
- 10. What’s needed
- 11. Docker multi stage build
- 12. Docker cache Sending build context to Docker daemon 2.491MB Step 1/28 : FROM microsoft/dotnet:2.1.6-aspnetcore-runtime-stretch-slim AS base ---> ea22d9662fa7 Step 2/28 : WORKDIR /app ---> Using cache ---> 526306fb506d Step 3/28 : EXPOSE 80 ---> Using cache ---> ead27daa8400 Docker cache can dramatically improve your build speed
- 13. Demo
- 14. Other steps that you might need ◦ Pushing to nuget => dotnet nuget push ◦ Pushing docker image to repository => docker push ◦ Building in Windows => create a powershell script
- 15. Common Gotchas ◦ Line endings (CRLF vs LF) with ps1 and sh files. ◦ ALWAYS use LF ◦ Set ps1 and sh files to have LF ending in .gitattributes ◦ Case sensitivity in Linux ◦ Linux & Windows path when using Windows Subsystem for Linux (WSL) ◦ wslpath and WSLENV
- 16. Key takeaway ◦ If you’re not building using build scripts, consider using them ◦ If you’re building build script and want to take things further, take a look at containerized build
- 17. The End HO PENG FOONG pengfoong@gmail.com
Editor's Notes
- #3: No version control for “build steps” (when not using pipelines.yaml)
- #5: Need someone to configure the build server Hard to debug when something goes wrong in build server, cannot reproduce easily Tough on newcomers
- #9: How long does it take for a new developer to setup their machine? Have you been in a situation where nobody remembers/knows how to configure the build server? Or when you need to keep certain versions of Visual Studio around? Or when something was upgraded and build breaks?