Mechanism for identifying released build artifacts and numbers

[dblock]

Is your feature request related to a problem? Please describe

In order to produce a 1.1.1 patch build we need to locate artifacts from the 1.1.0 release, including the manifest, and maven artifacts.

• Where is the released 1.1.0 build output? Probably an URL on artifacts.opensearch.org?
• ...

Describe the solution you'd like

A mechanism/page/something that links to the complete signed and unsigned output of a well known release.

Describe alternatives you've considered

No response

Additional context

No response

[dblock]

@peternied thoughts on this?

[peternied]

Committing the final build manifest back into this repository so it can be used for resolving previous artifacts seems like it could do the trick.

My only concern is the exiting artifacts have had many schema path revisions and whole build fleets will be retired and I wouldn't want us to loss our ability to patch (or have to perform some kind of recovery).

This shouldn't block us in the short term, but I'll file an issue for preserving "important" ci artifacts until we can land on a system we aren't knowing going to depreciate.

[bbarani]

Closing this issue as we are shipping the build manifest with the distribution (starting 1.2.0) that contains the exact location of the artifacts.