gitlab

Now that I have a century-old house to manage, I’ve found myself struggling to keep on top of all the things that need doing. Not only that, but knowing which need to be done by when, which require tools or parts, and which are on hold can be tricky. To alleviate these problems, I’ve come up with a plan…

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.

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.

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.

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.

When multi-project workflows are necessary, the hand-offs can lead to repetition. To alleviate that, Lab Assistant will automate the hand-off for a multi-project workflows.

As DevOps evolves, new technologies enable better processes. If your team has a process defined by tradition, take a fresh look. Use some of these examples and keep an eye out for other accelerators as time passes.

Branches for input, merges for admission, tags for output.

GitLab released a dozen page book about Git Branching Strategies to serve as a high-level overview of branching strategies and how they work.

This is a brief update to share that I switched out the shell version for a golang version. This change made the tweeting mechanism smarter while reducing the container size to 1/5th of what it was.

This is not related to brownfield technology, but it is something that can be done to help with handbook updates and other non-code sorts of projects. This recipe has some interesting ingredients such as GitLab CI, a Twitter API warpper for Go, Twitter Apps, GitLab Pages workflow, A Docker Container, and the route-map file.