Thanks Sebb,
Note that previously the GH action was running the default goal:
'clean verify javadoc:javadoc'.
Since we now need to specify the 'deploy' goal as well the above
defaults can be switched in for your additions when Infra have created
the credentials.
Alex
On Tue, 19 Dec 2023 at 14:2
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 wr
Created https://issues.apache.org/jira/browse/INFRA-25297 to get
access to credentials
Added code to maven.yml to deploy the snapshot (needs to be enabled
when creds are granted)
-
To unsubscribe, e-mail: dev-unsubscr...@commons.
On Tue, 19 Dec 2023 at 12:25, Alex Herbert wrote:
>
> On Tue, 19 Dec 2023 at 10:41, sebb 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 ac
On Tue, 19 Dec 2023 at 10:41, sebb 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 jav
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
reference
