From experiencing organizations ranging from 10-person start-ups to dozens-of-thousands-of-people organizations, I have found a consistent experience among shared service providers. They say “no.” A lot.[Read More]
Highlighting and sharing patterns to enable new approaches and increase velocity on old applications. Just as a car undergoes a binary conversion from “new” to “used” as soon as it leaves the lot, so do custom applications.
So how are things?
As-of posting this, Mike is moving from GitLab to Coder. The purpose of this site and the gitlab.com group are not changing, though the day-to-day problems to solve are likely to be more about Developer Experience going forward.[Read More]
Coder Enterprise vs Raw Code-Server
Comparing my Frankenstein code-server with Coder Enterprise
Coder recently made their enterprise offering free for up to 10 developers. Since my solution, which I will henceforth call “ICSW”, supports 1 developer, it is well within that limit. I configured a new namespace in the same cluster to run the Coder Enterprise system to see how they compare.
TL;DR: Coder Enterprise has a lot of benefits for centrally managed code-server deployments as well as a multi-image workflow.[Read More]
Upgrade Code Server to 3.5.0
Nice and easy, update 2 files
iPad Code-Server Owns Its Namespace
Code-server pod can create resources in its namespace
The new capability is running additional pods and services (and ingress and statefulsets) within the
development namespace using the
developer service account. This limited access role can’t impact other services but can start a container and use internal DNS and services to access them.
GitLab Commit 2020 – Brownfield Topics
Which sessions will be most relevant and useful?
Lab Assistant 1.1 and Deploy Fast
Repository File API call reduces pipeline by 61 lines, also explore the Segregation of Auto Duties / Deploy but Fast project
In support of simplifying the Segregation of Duties pipeline definition, the Lab Assistant app will now create a dotenv formatted file and deliver it to the newly created branch. This perfectly meshes with what the Auto Deploy Image is expecting to allow Segregation of Auto DevOps Duties.
To help make it clear what the intermediate step is between the existing Deployment project example and real DevOps, I created a streamlined version.[Read More]
DevOps: Transition Path Video Walkthrough
The previous article is pretty dense, this video shows the suggested workflow
The original recording was 40 minutes of chatting and pipelines and other nonsense. I sliced it up and we are left with about 9 minutes of the process and 4 minutes explaining a few pipeline jobs in greater detail.[Read More]
DevOps: Transition the Path to Production
Multiple projects with automated handoff to mitigate generic roles
When transitioning from classic methods to Agile and DevOps, the gatekeepers can feel stuck in limbo. The first step to easing the transition for security reviews, change management, and independent verification is to give them a place they control. As of GitLab 13-ish, the existing roles do not meet this need, despite the merge request approval with branch, tag, and environment protections.
This article lays out a 2 project workflow with an automated merge request handoff to support the access levels needed for segregation of duties with Auto DevOps.[Read More]