My First Pipeline as a DevOps Engineer ๐
By Neil Jyoshi ๐จโ๐ป
Itโs been just under a month since I joined NebulaStack Pvt. Ltd. ๐ข and Iโm still wrapping my head around how everything fits together. Today, though, felt like a turning point โ I finally finished my first end-to-end pipeline at work! ๐
Settling into the role ๐งโ๐
Coming straight out of college ๐, the transition has been eye-opening. In academia, most of what I learned was theory โ diagrams on CI/CD, lectures about cloud architecture โ๏ธ, or group projects that never went beyond running on one personโs laptop ๐ป. I had never really touched a production system before.
Here, itโs a whole new world ๐. The first few weeks were a blur of logins ๐, RhinoTunnel VPN setups ๐, and forms ๐. Honestly, I think I spent more time inside our HRFlare than inside an IDE ๐ฅ๏ธ. Every time I needed to update my profile or check a leave balance, I found myself lost in that system. It was overwhelming but also exciting ๐ .
The pipeline story ๐ ๏ธ
This week, my lead finally gave me a real task: set up a pipeline for Project Rainstack 2.0 ๐ง๏ธ. Seeing that project name on my Jira board made me nervous ๐ฌ and proud ๐ at the same time.
The pipeline itself wasnโt rocket science ๐, but for me, it was huge:
- Pull the code from GitHub ๐
- Build the app ๐๏ธ
- Run some tests ๐งช
- Package it with Docker ๐ณ
- Deploy it to our test cluster via Jenkins ๐ค
The Jenkins UI looked intimidating at first ๐ฑ. I must have broken things a dozen times before it finally worked. When that โSUCCESSโ label popped up โ , it felt way better than any grade I ever got in college ๐.

People make the difference ๐ค
I would never have managed this without my manager Ravish Prakash Sharma ๐. He reviewed my pipeline scripts and gave the final approval when I was too scared to hit the button myself ๐ . Slack must be tired of my notifications by now because I pinged him for every silly doubt ๐ฌ. Seeing โApproved by Ravishโ in the Jenkins logs felt like a real achievement ๐ฅณ.
Looking back ๐
The biggest revelation has been that DevOps is as much about collaboration and communication as it is about technology ๐ก. In college, mastering YAML files or Docker commands felt like the whole game ๐ฎ. Now, I see how crucial it is to coordinate with teammates ๐ฅ, navigate approval workflows โ๏ธ, and understand how every tool fits into a larger process ๐งฉ. The human side is what really keeps everything moving ๐ฆ.
Today was just one pipeline, but it made me feel like I finally crossed the gap between theory and practice ๐. I got to contribute a small piece to NebulaStackโs bigger picture ๐ผ๏ธ. Tomorrow, it might be more complex pipelines, automated testing, or scaling deployments ๐.
For now, Iโm just happy I finally got to build something real โ and watch it go live ๐ข.
โจ Hereโs to many more pipelines (and hopefully fewer late nights reading Jenkins logs) ๐.
โ Neil Jyoshi ๐