| Re: [jakarta.ee-community] Community help request |
_______________________________________________According to EF rules any committer can apply for leadership, or nominate others for leadership. If a project has no lead, you should ask the committers to elect (at least) one.
From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Werner Keil
Sent: Dienstag, 28. August 2018 14:33
To: Jakara EE community discussions
Subject: Re: [jakarta.ee-community] Community help request
Dmitry,
I'll create tickets especially for OpenMQ in areas that seem unclear or need verification.
Btw, is there a concept behind some projects like OpenMQ being without a lead, while others (e.g. JMS) have Tomitribe/David, and at least one other project even has 2 or more project leads?
(not looking at EE4J top level, where sharing this could be a strategic decision)
Werner
On Tue, Aug 28, 2018 at 12:38 PM Werner Keil <werner.keil@xxxxxxxxx> wrote:
Dmitry,
Thanks for the update. Especially for the C client and packaging module it has to be confirmed, if they work in the JIPP.
For others I created issues and saw these confirmed, so I will prune some of these jobs.
Werner
On Tue, Aug 28, 2018 at 11:34 AM Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx> wrote:
On 28 Aug 2018, at 11:07, Werner Keil <werner.keil@xxxxxxxxx> wrote:
Thanks for the overview.
@Dmitry is this also the view by PMC, Steering Committee or Eclipse officials?
We would love to see some consistency, but we also respect projects teams decisions. IMO, what Markus is done is fine.
I made two builds work in OpenMQ, but there could be special requirements e.g. native build jobs that have to be verified, if the necessary slaves are available. I helped a highly distributed Automotive project with their Jenkins infrastructure, there special slaves e.g. for a particular compiler etc. were a key aspect. It may be a little less complex here (maybe for IoT there are similar needs at Eclipse ;-) but MQ is among the projects that have native build-chains and also tight integration with the Glassfish project, which may need to be done in its JIPP rather than OpenMQ.
Thanks, Werner! Does it mean that I can mark the build task for OpenMQ as done?
Feel free to ask Eclipse webmasters about slaves, etc. in EE4J build mailing list: ee4j-build@xxxxxxxxxxx
— Dmitry
Werner
On Tue, Aug 28, 2018 at 7:11 AM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:
Every project is free to do it as they please. There is no need for consistency among projects, and consistency even might be an obstacle to some extend. A project not even needs to have CI at all. At JAX-RS we only have two jobs in JIPP: Nightly build (pushed into EF's Nexus) and Release build (pushed into OSSRH's Nexus).
-Markus
From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Werner Keil
Sent: Montag, 27. August 2018 22:52
To: Jakara EE community discussions
Subject: Re: [jakarta.ee-community] Community help request
What about Jersey?
https://ci.eclipse.org/jersey/ has two jobs, is that sufficient for RI projects?
(OpenMQ has 5, but for the sake of consistency, I'd like to get the *-continuous build to run without errors for now)
Unfortunately the OpenMQ jobs were set up entirely different, one or more point to repositories that don't seem to be in Eclipse-EE4J at all.
Werner
On Mon, Aug 27, 2018 at 8:49 PM Werner Keil <werner.keil@xxxxxxxxx> wrote:
Are there multiple pipelines for JAX-RS?
Because https://github.com/eclipse-ee4j/jaxrs-api has a build badge for Travis-CI, not Jenkins.
On Mon, Aug 27, 2018 at 2:08 PM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:
Yes please mark it as done.
From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Dmitry Kornilov
Sent: Montag, 27. August 2018 13:24
To: Jakarta EE community discussions
Subject: Re: [jakarta.ee-community] Community help request
Markus, can I mark JAX-RS release CI/CD pipeline task as done here:
— Dmitry
On 27 Aug 2018, at 13:18, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:
I requested a JIPP earlier this year for our Nightly Builds and simply set up an additional job for staging on OSSRH.
-Markus
From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Werner Keil
Sent: Montag, 27. August 2018 13:17
To: Jakara EE community discussions
Subject: Re: [jakarta.ee-community] Community help request
Did you request the JIPP for that or was it there already?
On Mon, Aug 27, 2018 at 1:13 PM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:
JAX-RS API: Release pipeline done, Github Task closed, Release 2.1.1 for EE4J_8 is staged on OSSRH. Next: Filing release review.
-Markus
From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Dmitry Kornilov
Sent: Montag, 27. August 2018 11:42
To: Jakarta EE community discussions
Subject: Re: [jakarta.ee-community] Community help request
Hi folks,
Here is the latest state of CI/CD pipelines work:
There is a little progress since last week (almost nothing). If I missed something please report your progress here. There are still a lot of projects waiting for volunteers. I am requesting the community to be more active.
Thanks,
Dmitry
On 21 Aug 2018, at 17:19, Elder Moraes <elder.moraes@xxxxxxxxx> wrote:
Hi folks,
I'm traveling this week with lots of meetings, but next week I'll start working on it.
Cheers,
Em seg, 20 de ago de 2018 às 11:59, Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx> escreveu:
Thanks, Reza. I really appreciate your willingness to help.
Unfortunately, there is not much progress. See the summary here:
- JAX-RS created the release job. Thanks, Markus!
- Elder Moraes volunteered to create release pipelines for Servlet API. No progress reported so far.
- I talked with Werner Keil. He is willing to help, but he didn’t put an assignment to the spreadsheet above. Werner, if you are in, please do it.
That’s it. Help is still needed.
Thanks,
Dmitry
On 17 Aug 2018, at 00:46, Reza Rahman <reza_rahman@xxxxxxxxx> wrote:
Have you found any meaningful community help on this? If that's the case, I'll leave this here. If not, I'm going to try to find someone that can help. It can't be right that no one is willing to help accelerate this given how important this work is. This is not my specialty, but I will do it if no one else is willing.
On 8/8/2018 5:36 AM, Dmitry Kornilov 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 listjakarta.ee-community@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
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@xxxxxxxxxxx
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@xxxxxxxxxxx
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@xxxxxxxxxxx
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@xxxxxxxxxxx
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@xxxxxxxxxxx
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@xxxxxxxxxxx
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@xxxxxxxxxxx
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@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community