Re: [ee4j-build] Wrong release in staging

[arjan tijms <arjan.tijms@xxxxxxxxx>]

Hi Vinay,

If I understand correctly, the "standard" job, that seemingly not everyone is using it seems, does the staging without risk of a release to Maven Central.

However, the job stages to an unreachable repo. It's a repo that can only be reached via nexus, but if I understand correctly no-one has the credentials for Nexus. I'm not 100% sure why there even are repos that nobody has access to (have the credentials been lost?), but it is what it is. I could well misunderstand of course, but from reading some of the posts that has been my understanding.

Kind regards,

Arjan

On Mon, Nov 5, 2018 at 7:21 AM vinay.vishal@xxxxxxxxxx <vinay.vishal@xxxxxxxxxx> wrote:

Isn't then this issue limited to the jobs where nexus-staging plugin was
used to do the release. If a release job is based on
https://wiki.eclipse.org/JakartaEE_New_Infra_Release_Job#Build_and_Deploy_Artifacts,
then it just deploys to staging repository and nothing else, is this
correct?

On 02/11/18 10:20 PM, Lukas Jungmann wrote:
> the bug was basically that the call to rc-release goal in the script
> was not guarded by 'if', so instead of rc-release being executed
> conditionally, it run every on each job run.
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build