Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-community] Community help request
Like I said, those kinds of tool choices would be up to the PMC or Eclipse and its Webmasters;-)

BR,

Werner




On Wed, Aug 8, 2018 at 12:27 PM, Mihai A. <amihaiemil@xxxxxxxxx> wrote:
Hi Werner,

Well, Rultor is quite configurable via a .rultor.yml file, which should be present in the base ditectory of the repo.

There, you can declare who are the architects - rultor will obey them instantly or ask for their perimission if the commander is not an architect.

Br,
Mihai


On Wed, Aug 8, 2018, 13:07 Werner Keil <werner.keil@xxxxxxxxx> wrote:
Hi Mihai,

Thanks for the suggestion.
You mean, Rultor would automatically merge a PR assuming that e.g. a committer or if necessary PMC member (could Rultor tell those cases apart?;-) has approved it?

Not sure, what Eclipse Foundation or the EE4J PMC, Steering Committee etc. think of that.

Regards,
Werner


On Wed, Aug 8, 2018 at 11:56 AM, Mihai A. <amihaiemil@xxxxxxxxx> wrote:
Hi Dmitry,

Look into rultor.com, maybe you can use it to release to OSSRH automatically. See the latest release of amihaiemil/docker-java-api, for instance.

Rultor will basically clone the repo and perform the configured build in a dedicated Docker container. I just say "@rultor release, tag is `0.0.1`" and the artifact is released on Maven Central based on plugins from pom.xml and encrypted keys which only rultor can decrypt.

Br,
Mihai

On Wed, Aug 8, 2018, 12:36 Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx> wrote:
Hi,

I took the initiative and created a list of tasks we need help with. All these task are related to projects CI/CD pipelines and releasing the first Eclipse versions of projects. I created two tasks in projects issues trackers:

1. Build CI/CD pipeline. 

This is about creating a basic pipeline which build the project and runs tests on Eclipse provided infra.

2. Release pipeline and first release

This is about creating a release pipeline which releases a Maven artefact to OSSRH *staging* repository. Staging is a keyword, we don’t want public releases before projects pass the release review.

Here is a summary spreadsheet with links to all issues created for progress tracking:

Please self assign to tasks ion GitHub and and add a comment to the corresponding "Responsible Person” cell in the spreadsheet above, I’ll check it periodically and update it based on your comments.

There are also two wiki pages which you can use as a reference:

1. How to release the first Eclipse version of projects. 
It contains general flow and HOWTOs.

2. JSONP release job. 
It describes JSONP release pipeline which is the only one which works for now. You can use it as a reference for your project release job or you can come out with something else. 

Don’t hesitate to ask questions if you have any.

Thanks,
Dmitry
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community

_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community


_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community

_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community


Back to the top