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]
SAFe Indicates Unsafety
What it means to choose SAFe in 2020
Why Won't Anyone Use Our Pipeline? (ATARC Talk)
Waterfall processes lead to dysfunctional pipelines.
Software Development vs FARs
Can federal software development be agile?
Agile software development has revolutionized the way private sector organizations build software. The primary tenets are that all companies are software companies, software is never done, and requirements always change. What does that mean for the federal space?[Read More]
Workflow: Pull is Better
GitLab’s developers use a pull workflow so the
assigned field is editable by anyone. The intended worfklow is to leave the issue unassigned (though tagged for a team) and when a developer is ready, they assign it to themself and work on it. Assignment is seen as a “leave this alone if it’s not you” sort of signal rather than “someone wants me to get this done.”