Re: [release-plugin] thoughts on automated validation of releases

Maybe use creadur as home, it is exactly its goal: https://creadur.apache.org/ Le mar. 4 août 2020 à 00:13, sebb a écrit : > On Mon, 3 Aug 2020 at 22:15, Rob Tompkins wrote: > > > > > > > > > On Aug 3, 2020, at 5:14 PM, sebb wrote: > > > > > > On Mon, 3 Aug 2020 at 19:43, Rob Tompkins wrote

Re: [release-plugin] thoughts on automated validation of releases

On Mon, 3 Aug 2020 at 22:15, Rob Tompkins wrote: > > > > > On Aug 3, 2020, at 5:14 PM, sebb wrote: > > > > On Mon, 3 Aug 2020 at 19:43, Rob Tompkins wrote: > >> > >> That’s just an example of what I’ve been doing. The question is whether we > >> move this logic into the release plugin for the

Re: [release-plugin] thoughts on automated validation of releases

> On Aug 3, 2020, at 5:14 PM, sebb wrote: > > On Mon, 3 Aug 2020 at 19:43, Rob Tompkins wrote: >> >> That’s just an example of what I’ve been doing. The question is whether we >> move this logic into the release plugin for the sake of validation. > > I think it's best to keep any checking

Re: [release-plugin] thoughts on automated validation of releases

On Mon, 3 Aug 2020 at 19:43, Rob Tompkins wrote: > > That’s just an example of what I’ve been doing. The question is whether we > move this logic into the release plugin for the sake of validation. I think it's best to keep any checking scripts entirely separate from the Maven generation process

Re: [release-plugin] thoughts on automated validation of releases

That’s just an example of what I’ve been doing. The question is whether we move this logic into the release plugin for the sake of validation. > On Aug 3, 2020, at 2:19 PM, Gary Gregory wrote: > > Hi Rob, > > I am missing something. Is this something you will provide for each > component? Or

Re: [release-plugin] thoughts on automated validation of releases

At OpenWhisk, they've come up with a more standardized process around this as they have a lot of components, too. https://github.com/apache/openwhisk-release And the related utilities for enforcing releasability and similar things: https://github.com/apache/openwhisk-utilities This began as a r

Re: [release-plugin] thoughts on automated validation of releases

Hi Rob, I am missing something. Is this something you will provide for each component? Or, is this a command that is generated in the VOTE.txt? The latter seems more reasonable since there are so many variables. Note that some components have different component names from their artifact IDs: poo

[release-plugin] thoughts on automated validation of releases

Currently I run the following scripts for signature valitaion: https://github.com/chtompki/notes/blob/master/commons-release-validation/commons-text-1.7-downloader.sh and https://github.co