[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ee4j-build] Wrong release in staging
|
Hi,
On 11/2/18 4:25 PM, arjan tijms wrote:
Hi,
On Fri, Nov 2, 2018 at 3:22 PM Lukas Jungmann <lukas.jungmann@xxxxxxxxxx
<mailto:lukas.jungmann@xxxxxxxxxx>> wrote:
depends on what one tells the job to do...
Yes, about that, I "hoped" (but in vain, I guess), that the job didn't
have enough power/access to actually release. E.g. that at most it could
stage and prompt to close/release, but that actually synching to Maven
central would still be a manual step.
for 99% jakarta projects I don't think that the statement 'In each
project, there exists a committer who has access to ossrh nexus to
verify staging/release and who can push required 'drop'/'release'
button' is true, pmc would probably know that for sure.
Only jenkins jobs do have such power here - that is not what you wanted
to hear, right?
in case of jpa-api, the "bug" has been already identified and fixed[1]
Unfortunately, the diff is protected. When logged-in I get: "No
permission to view config history".
Can you post the diff here if possible? Might be good for all of us to
learn from.
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.
thanks,
--lukas
and have good understanding of
what, when and why they do what is written in them, you should be
safe...
Yeah, I guess ;) But I have a sinking feeling most everybody is walking
a little in the dark here, copied the scripts from the wiki and just
prayed they worked >
Kind regards,
Arjan
_______________________________________________
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
