Radu, In concept I agree, no good reason to have multiple tools to do similar things. I wonder if we just fork off the release validation process into a separate script vs the Java-based processes. I'm just not convinced of the value re-implementing in Java brings vs a few simple bash commands. Let me poke around and see if I can come up with something.
Thanks, Dan On Fri, Aug 23, 2019 at 6:31 AM Radu Cotescu <r...@apache.org> wrote: > Hello, > > I’m +1 for any tool that reduces the number of manual steps I have to do > when performing, validating or promoting a release. > > I have one question though: couldn’t we push these features into the > Apache Sling Committer CLI tool [0]? That tool is already based on a > minimalistic Docker image with an embedded jlink-customised JRE. Sensible > information is provided from the outside anyways (think Apache user and > password, JIRA user and password), so if we’re thinking about the keys file > we could do something similar. > > The only reason for asking such a question is that it would be nice to > consolidate all CLI checks into one tool. > > Thanks, > Radu > > [0] - https://github.com/apache/sling-org-apache-sling-committer-cli < > https://github.com/apache/sling-org-apache-sling-committer-cli>
