Hmmm I Need a New Pipeline
I was recently asked to discuss a topic regarding DevOps and CI/CD pipelines. It wasn’t a ‘how do you do this’ question. Rather, it was more a behavioral question. More to talk about not only how you would do a pipeline, but also, why you would to it, what was the thought process, what would the interaction be like for you to implement a pipeline for the developer(s) who were asking for the pipeline
Here are some mostly random thoughts (unless you came after after I decided to organize my thoughts haha)
Generically, What would be the process and the thinking behind it?
don’t just build pipelines—you think like a DevOps engineer who cares about quality, reliability, scalability, and stakeholder alignment
Do not just build the pipeline because you are asked to do so. Consider the following:
- quality
- reliability
- availability
- scalability
Actually, if you consider the above for whatever you do, no matter your role or responsibility, your management is going to love you.
the thought process
Your customer tells you that they need a new pipeline. You could whip up a new Jenkinsfile or YAML and be done with it. But you really should try first to:
- understand the requirements
- clarify and understand the risks
- think about how this can be made more generic, more flexible, and a more scalable solution
We’ll come back to this, step 0 is: why am I even doing this?
Discovery and Context
You want to understand the requirements, what is the purpose for doing this, and how this should work ideally.
Start With Discovery and Context
“Before I start designing anything, I begin by understanding the request.”
You ask the application team:
What type of application is it? (microservice? monolith?)
What language/runtime/environment?
How is it built today?
What is the deployment target? (ECS, EKS, EC2, Lambda, on-prem)
How often do you deploy?
Any compliance or security requirements?
Do you already have patterns or standards I should align to?
Why this matters: Shows you don’t act blindly—you pull context to avoid breaking things.
Why am I being asked to create the pipeline?
What can I do in the future so that I won’t have to create a pipeline?
Getting to VFS NYC
Resources & References
NSM Lawyers
Contact Information:
Phone: +351 215 847 264
Email: geral@nsmadvogados.pt
Visit: www.nsmadvogados.pt
Address: Av. Fontes Pereira de Melo, 21, 2º 1050 116 Lisboa
Outbound Migration Consultancy
Contact Information:
click here to request free 30 minute consult
Email: planb@outboundmigration.com
Visit: outboundmigration.com
USA
Phone: +1 424 404 9399
Address: 8383 Wilshire Blvd. Ste 800 Beverly Hills, CA 90211
Canada
Phone: +1 604 200 3560
Address: 230-1290 Howe St Vancouver, BC V6Z0C2
VFS.Global
Contact Information:
Visit: VFS.Global
VFS Global application centers
Houston: 1001 Texas Avenue, Suite 1020, Houston, TX 77002.
Miami: 2655 S. Le Jeune Rd, Penthouse 1A, Coral Gables, FL 33134.
New York: 128 E. 32nd Street, 3rd Floor, New York, NY 10016.
San Francisco: 642 Harrison Street, Suite 200, San Francisco, CA 94107.
Washington D.C.: 1025 Vermont Ave NW, Suite 200, Washington, DC 20005.
Have questions or want to share your own sysadmin story? Leave a comment below!
(I will set up comments eventually ;)