Re: [ee4j-build] Jakarta Stable release Jenkins jobs unable to access gi

[Tomas Kraus <tomas.kraus@xxxxxxxxxx>]

Dne 23.08.19 v 15:43 Jim Krueger napsal(a):

Thanks Maxim,   That makes sense.    I've hit another problem though that maybe somebody else on this mailing list has hit?

The PR is failing with this error:  “Genie Jakartaee-stable (jakartaee-stable-bot@****.org) did not include the “Signed-off-by footer” which is required for all commits made by a contributor.”I’ve added jim-krueger/jaxr-api to Eclipse ECA Validation (https://github.com/settings/installations/1629989) but no luck.

On Thu, Aug 22, 2019 at 6:34 AM Maxim Nesen <maxim.nesen@xxxxxxxxxx> wrote:

Hi Jim,

Basically the idea is that the job prepares release branch and tag and commits them to Github. However it's difficult to create PR directly from job, so it is left for manual processing. So, after job is done it is required to submit PR with merge request to master for release branch. After PR is accepted (PR is merged into master), the release branch shall be deleted. And the release tag remains in Github.

I already made job that can create issue or PR on github. Check any autoupdate job in jaxb-impl or metro project, e.g. https://jenkins.eclipse.org/jaxb-impl/job/istack-commons-master-dependency-update/

Tomas

Regards,

Maxim