DevOps Pipeline

Mike's Notes

Here are my working notes from day 6 of building the DevOps Engine for Pipi 9.

Resources

DevOps Pipeline

By: Mike Peters
28/02/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Today, I added pipelines to the initial DevOps Engine data model. 

Pipeline

In Pipi 9, a DevOps pipeline is a set of automated processes and tools that enable team members and Pipi, the robot, to collaborate on deploying data model changes, workflows, code, experiments, algorithms, engine mixtures, digital twin, etc., to the live production environment that is Pipi.

Steps

I also enabled any DevOps team to select what steps to use in a pipeline from a library of steps.

  • Each step has configurable properties.
  • The set of steps can be different for each pipeline.
  • Different team structures could need different step configurations.
  • For example, Atlassian has these steps.
    • Discover
    • Feedback


DevOps Engine

The DevOps Engine can be used in different situations, including:
  • Internally on Pipi.
  • By those who create and deploy enterprise SaaS applications.
  • Providing support to paying customers.
  • Etc.

WBS

Because of dependencies, every task has a Work Breakdown Structure (WBS). They are all part of a larger whole. However, the tasks are being done out of order because it is easier. In the end, they all need to be done. This use of WBS needs more experimentation and thinking.

Next steps

The published web page roadmap has been imported as data into the DevOps database. After some tweaking at both ends, it worked. Tasks can now be edited. I just need the Render Engine to republish the web page whenever an edit is made or automation runs.

I would like to talk to people who have experience using DevOps tooling.
By ,
Tags ,

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)