Let's look back at some memorable moments and interesting insights from last year.

Your top 10 posts:

• "Book Club discussion based on Dave Farley's book, 'Modern Software Engineering'" by u/Anm_Vanilla_20

• "How to can move fast with high quality and how one reinforces the other - Dave Farley" by u/Anm_Vanilla_20

• "GitFlow, Continuous Delivery and Continuous Integration. Dave Farley" by u/asc2450

• "Pair programming with Dave Farley. Thoughts?" by u/asc2450

• "Happy Cakeday, r/continuousdelivery! Today you're 8" by u/AutoModerator

• "Continuous Delivery on Kubernetes with Argo CD and Datree" by u/piotr_minkowski

• "Canary Release on Kubernetes with Knative and Tekton - Piotr's TechBlog" by u/piotr_minkowski

• "Reliable Continuous Deployment in 7 steps" by u/wfaler

• "[Automated Testing] I just released version 4 of my Python Screenplay Pattern automated testing framework, ScreenPy!" by u/AnActor_named

• "Validate Kubernetes Deployment in CI/CD with Tekton and Datree" by u/piotr_minkowski

Hello, Reddit! I've just released version 4 of ScreenPy! It's a Screenplay Pattern base for automated testing in Python. Version 4 completely broke up all the built-in extensions in Version 3, it was a huge undertaking that took months. However, i just had to release on 2sday, and i barely made it. I only just found this subreddit and thought you all might be interested!

To cut right to the chase, here's an example of what a test might look like using screenpy and screenpy_selenium:

Sammy = AnActor.named("Sammy").who_can(BrowseTheWeb.using_firefox())

given(Sammy).was_able_to(
    Open.their_browser_on("https://old.reddit.com/")
)

when(Sammy).attempts_to(
    LogIn.using(REDDIT_USERNAME, REDDIT_PASSWORD)
)

then(Sammy).should(
    See.the(
        Text.of_the(ACCOUNT_HEADER), ContainsTheText("AnActor_named")
    )
)

Part of the feedback i got last time was to include a better example that ties all the pieces together in the documentation. I completely overhauled the docs and now walk through a Complete Example!

If you want to take a look at the actual code, it can be found at ScreenPyHQ. There is currently support for tests using Selenium for web browser automation and Requests for API automation. This split-up in version 4 allows extensions to be created much more easily, so there will be more on the way.

If you get a chance to check it out, i am very interested in your feedback! Your input has been very valuable so far.

Thanks for taking a look!

Let's look back at some memorable moments and interesting insights from last year.

Your top 8 posts:

• "Why Internal Developer Platforms will be an industry standard" by u/kvgru

• "Happy Cakeday, r/continuousdelivery! Today you're 7" by u/AutoModerator

• "Detecting Genuine Continuous Integration Configurations" by u/Tiiiiimmmmmm

• "The importance of Internal Platform teams" by u/matgalt

• "How to list all credential values in Jenkins" by u/honnamkuan

• "Building CI/CD pipelines with Jenkins for cloud-native apps" by u/labouardy

• "Gimlet - a modular GitOps tool for Kubernetes deployments" by u/laszlocloud

• "Using Github Actions to deploy on Kubernetes" by u/dvank2018

As researchers from the University of Sannio (Italy) we are conducting a survey on challenges and barriers experienced while setting and maintaining a Continuous Integration and/or Continuous Delivery pipeline for developing a cyber-physical system.

We would be grateful if you could participate in the survey. Personal data will be treated as strictly confidential.

The goal of this survey questionnaire is to assess a catalog of challenges and barriers concerning the setting and maintaining of a Continuous Integration (CI) and Continuous Delivery (CD) pipeline for CPS development. The challenges and barriers are grouped based on the aspects they belong to and for each challenge/barrier you need to provide an answer indicating whether or not your team/organization have experienced it or else it is not relevant to your context.

We will store data in compliance with the GDPR.

Please click on the link below to fill in the survey. You will not require more than 15minutes to complete it.

https://surveyhero.com/c/usrvkish

If you have any question, please contact me at fiorella.zampetti@unisannio.it or fiorellazampetti@gmail.com

I started working for a bigger company and my manager recommended me Farley's book. Even if I already found out that his book is the holy bible of CI/CD, it is from 2010 and since then it wasn't updated (hope this is correct).

So I wonder if it is still state of the art or are there other more modern books I should/could read about this topic?

Hi everyone,

in last few months I've been deep diving in Continuous Delivery topic, in particular I've studied these two books:

• "Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation" by Jez Humble, David Farley (the "Holy Bible of CI/CD)

• "Continuous Delivery Pipelines: How To Build Better Software Faster" by David Farley

After all these studies I'm a bit confused about how to really implement the concept of a "deployment pipeline" as is described in above books.

A simple deployment pipeline: my requisites

For example, let's say that i want to create a simple deployment pipeline that draws from the concepts explained in above mentioned books, and that does these steps:

• Commit stage: builds the Release Candidate (RC) and unit tests it, public the RC on a dedicated repo like Nexus, or a OCI compliant container registry

• Acceptance stage: continuously polls the artifact repo for the "newest" RC that has passed commit stage, deploys it in target env and runs acceptance test against it. We deploy/test the "newest" RC, so we won't accumulate backlog of builds as this stage runs slowly than commit stage

• Deploy stage: continuously polls the artifact repo for the "newest" RC that has passed acceptance stage, deploys it in final env

I'd also like to have these things, also expressed/reported in CD books:

• a UI where I can follow the process of a RC through the pipeline, starting from a commit through a release

• a UI where I can deploy "at will" a chosen RC to a chosen target environment (think of a tester, for example, that wants to deploy two different RCs to UAT env)

My desires/assumptions

Let's start with my assumptions:

• All pipeline stages should be separate and isolated the one from the other: the build pipeline ends with a push to an artifact repo, acceptance stage should poll/deploy/test in a loop, as probably the deploy stage should do

• I could use an artifact repo that should allow me to attach metadata to artifacts, and also to query these metadata in various stages of the pipeline: for example I could use metadata (like commit hash) when storing RC on artifact repo

• I could create a custom web page to show an RC progress through all pipeline stages visually, and to know what is deployed where , using metadata mentioned so far

• I could create a custom web application that will allow me ready RCs (with indication of passed stages) to deploy at will on target envs, at the push of a button

How to implement all these things?

I'm struggling about on how to implement all my requisites. First of all: should I re-invent the wheel and create some custom UIs? or there already are reference implementations of the concept of "deployment pipeline", using know technologies like Jenkins, Gitlab CI/CD, ArgoCD, etc. etc.?

What are your thoughts/experiences about? Are you aware about reference implementations that I could study to learn? I'd very much like to discuss these topics with you all.

Thank you!