I think it would be a nice-to-have feature for all active components, allowing us to achieve parity with what used to happen with Jenkins (which I never used and rarely pay attention to). When can then drop all Jenkins build and free up those resources.
Gary On Tue, Dec 19, 2023, 5:41 AM sebb <seb...@gmail.com> wrote: > Crypto now has a workflow [4] that deploys a SNAPSHOT version. > > I don't know if we want to do this for all components, but if so, the > process is: > - raise INFRA Jira to request access to the secrets that hold the > credentials [1] > - use the java-settings action to create a settings.xml which > references the variables holding the credentials [2] > - pass the secrets as environment variables in the job-step that needs > them [3] (Note:: we don't need the GPG variable) > > The Crypto workflow is rather complicated because it needs to build > the code on several different OSes and then piece the bits together. > Other components will be much simpler. > > Are there any other components that would benefit from/need snapshots? > > Sebb > [1] e.g. https://issues.apache.org/jira/browse/INFRA-25296 > [2] https://github.com/actions/setup-java#maven-options > [3] > https://github.com/actions/setup-java/blob/main/docs/advanced-usage.md#yaml-example > [4] > https://github.com/apache/commons-crypto/blob/master/.github/workflows/maven_crosstest.yml > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
