I'm not sure quite how to phrase this question. I'd like to learn either by answer here or sharing a reference to read from: How do I build a pipeline with versioned build artifact?
I've inherited an established Jenkins build infrastructure that I recognize needs to change. This is especially evident because we want to move into a modern build approach with branches (dev, main, etc.).
This is basically how our builds work
lib-A is created first lib-B is created next lib-C is the last library created prod-DA uses lib-A prod-EC uses lib-C prod-FAB uses both lib-A and lib-B
Our current build infrastructure is what I'd describe as a dev infrastructure. In that it always uses latest.
When lib's A, B and C are created they are dropped into a shared folder to be used by everyone else.
When prod's DA, EC and FAB need to link with the library they just pull from the shared folder.
This is what I inherited. It's adequate for a single branch, riding-latest build system.
Is there a resource, pattern, book, website or toolset to help me learn how to change this to a versioned artifact scenario? Or how to convert to a mechanism that will scale and support branching?
I don't really even know what to call this, I'm really wanting to learn what you have to share.
Thank you for your patience.