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.
Legacy organizations with legacy products have designed complex and rigid processes for releasing software into a production environment. The production environment is special and has limited access and compliance and constraints and needs to always work so developers shouldn’t even try to look at it.
Except things change and stuff breaks. So now what? Continuous deployment to the rescue!?
[Read More]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]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 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]Upgrading code-server from 3.4.1 to 3.5.0 was always supposed to be easy. Turns out it was easy.
Just for the sake of sharing the ease, I’ve written up the embarrassingly simple process.
[Read More]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.
The GitLab Commit this summer is free for all with unlimited attendance due to the pandemic. This creates an opportunity for tons of people to have access to fantastic ideas that can help their organizations, teams, and individually.
[Read More]
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]
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]
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]