(replies inline) On Mon, 30 Apr 2018, Jesse Glick wrote:
> On Fri, Apr 27, 2018 at 12:54 PM, R. Tyler Croy <[email protected]> wrote: > > why not just have the full artifact URL listed > > in the Bill of Materials? For example: > > > > plugins: > > - groupId: org.jenkins-ci.plugins > > artifactId: git > > url: > > https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/git/3.8.1-rc1663.454c4a5e4d30/git-3.8.1-rc1663.454c4a5e4d30.hpi > > > > From the Jenkins Essentials perspective, all I really need is an artifact ID > > and URL for the artifact, but I'm not sure if that's all that's needed for > > the > > other use-cases here. > > You could do that, though a plain `version` attribute would suffice, > so long as the tool pulling binaries includes the Incrementals repo in > its list of locations. _If_ you wish to permit branch references or > local disk paths or other options in this format, then you would > anyway need some alternative ways of referring to binaries. > > The more interesting question to my mind is how you make edits to the > manifest like the above. After you have more than a handful of plugins > with versions like these, manually copying and pasting such > URLs/versions would be cumbersome. I think JENKINS-50953 can be used > to track this. For example, I might run something like > > $ update-incrementals configuration/essentials.yaml > > or > > $ update-incrementals configuration/essentials.yaml git workflow-api > > which for each selected component (or all) would check the current > version; gather a list of all deployed versions (from > `maven_metadata.xml`) that compare as strictly ???newer??? than that; > filter those by commits which are ancestors of current `master`; pick > the newest of the resulting versions; and edit the file to select that > version. > > You could then commit the result and push to a pull request, which > would get validated by a PR builder somehow TBD, and if all automated > checks pass it would be eligible for merging, meaning deployment to > production. > > WDYT? Admittedly the above is a very rough sketch, which I need to > flesh out quite a bit. If an update-incrementals tool existed, then yes, that would address my concerns here. So long as something can automatically update my yaml file, i'm happy to use it, I more wanted to make sure that we weren't going to have two or three implementations of what `update-incrementals` effectively should be providing. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180430204749.GL2935%40grape.lasagna.io. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
