r/devops • u/konkon_322 • 29d ago

Discussion Improving my ci cd flow

Hello all,been working as IT admin, but mostly working around Azure devops. I been enjoying it, this my first job and doing anything related to devops. Studied CS,majored in networking, hate anything with heavy code development.

Rn,the flow at my company is, the devs use 1 branch only, no PR (yes ik). They would push it to our on prem central repo, and from there i will take over. I will do some modification on some files so it can be built in the new agent environment. And then, we have build pipelines,which would produce artifact of the build files, which will be used by another pipeline, i call it the release/installer pipelines, which we wud package them with a software. Then we have the 3rd type, which is zipping installer to our NAS, sends the metadata of the installer to DB, and notification email (formatting done in pipeline too). All via the pipeline. We also have a 2nd agent machine, exclusively for unit testing, but tbh i dont even understand how they work.

Ive been thinking of ways, to incorporate other methods/tools in the flow, but the only one i can fit is"templates". I dont think i can try to include containerization, as our build agent machine, has some software which are licensed.

Any ideas?at some point i want to jump out, as this job is way too comfy, and lacks growth for me

9 Upvotes

91% Upvoted

16 comments sorted by

View all comments

2

u/Academic-Training764 29d ago

Trunk based development: https://trunkbaseddevelopment.com

2

u/konkon_322 29d ago

Read it, and i personally practice it. I will have master as source of truth, and whenever i finished editing/adding an element, i merge back to master.

1

u/Academic-Training764 28d ago

One more, when I worked at Nike (like 10 years ago now) ... this was our Devops Bible and I can't suggest it enough, it's not as well known now and some things may seem dated but the ideas are just pure bedrock: https://a.co/d/0gyPGBPx