Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-build] EE4J CI/CD roadmap (JIPP provisioning, etc)

Werner,

Can you please create a bugzilla ticket so that we can proceed with the creation of the JIPP?

Everyone,

I'm glad to inform you that JIPPs for all other EE4J projects have been provisioned. Thanks for you patience. 

Next steps OSSRH+Github

Cheers,

Mikaël Barbero 
Team Lead - Release Engineering | Eclipse Foundation
📱 (+33) 642 028 039 | 🐦 @mikbarbero
Eclipse Foundation: The Platform for Open Innovation and Collaboration

Le 21 sept. 2018 à 10:39, Werner Keil <werner.keil@xxxxxxxxx> a écrit :

If David is too busy and any committer is able to do it I'll look into that over the weekend.

Frederic Gurr <frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx> schrieb am Do., 20. Sep. 2018, 23:58:
Hi Dmitry,

AFAICS, we did no receive a request for creating the JMS JIPP instance yet.
Please contact the project lead, so we can work on it.

Regards,

Fred

On 18.09.2018 12:39, Dmitry Kornilov wrote:
> Mikael,
>
> Thanks for updating your plans. Jenkins instances for all projects must
> be provisioned anyway. I’ll ping the project leads who haven’t requested
> it yet.
>
> Thanks,
> Dmitry
>
>> On 18 Sep 2018, at 01:34, Mikaël Barbero
>> <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx
>> <mailto:mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx>> wrote:
>>
>> Based on feedbacks we received, we adjusted our roadmap. We
>> will provision all requested EE4J JIPP instances by the end of week 38
>> (Friday, September 22nd). This will only include the
>> JIPP provisioning, it will *not* include the complete setup to deploy
>> to OSSRH, GitHub PullRequest, committing to GitHub, etc.
>>
>> Finishing the setups (GitHub, OSSRH, etc) will happen in week 39 and
>> week 40.
>> See https://docs.google.com/spreadsheets/d/1O2NA6YddYQy34riTabQd_lkNwwFzKq1HevxCJYNXrv4/edit?usp=sharing for
>> full schedule. 
>>
>> If some projects need to be switched from week 40 to week 39, feel
>> free to raise your hand. Note that it will need to be made at the
>> detriment of another project.
>>
>> Finally, the following projects did not request a JIPP:
>>
>>   * jakartaee-platform
>>   * ejb
>>   * jaf
>>   * javamail
>>   * jms
>>   * websocket
>>
>> Is it expected? If JIPPs are needed for these projects, please open
>> tickets for them ASAP so we can schedule their creations.
>>
>> Thanks,
>> *
>> Mikaël Barbero *
>> *Team Lead - Release Engineering | Eclipse Foundation*
>> 📱 (+33) 642 028 039 | 🐦 @mikbarbero
>> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open
>> Innovation and Collaboration
>>
>>> Le 13 sept. 2018 à 09:02, Frederic Gurr
>>> <frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx
>>> <mailto:frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx>> a écrit :
>>>
>>> Hi,
>>>
>>> To quote myself:
>>>> All projects that don't have a JIPP yet, will get a JIPP on the new
>>>> infra.
>>>
>>> :)
>>>
>>> Regards,
>>>
>>> Fred
>>>
>>> On 13.09.2018 17:46, Werner Keil wrote:
>>>> Fred,
>>>>
>>>> Thanks for the update. I plan to soon request a Jenkins instance for
>>>> jms-api, will it automatically be the new one or do I have to take
>>>> anything into consideration?
>>>>
>>>> As for the Sonatype part, that will have to be on hold for ALL Spec/API
>>>> deploy jobs until the new groupId is in place and can be ordered AFAIS.
>>>>
>>>> Regards,
>>>> Werner
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Sep 13, 2018 at 5:37 PM Frederic Gurr
>>>> <frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx
>>>> <mailto:frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx>
>>>> <mailto:frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx>> wrote:
>>>>
>>>>    Hi,
>>>>
>>>>    We would like to give an update about the current status and the
>>>> roadmap
>>>>    for the next weeks in the light of yesterday's presentation.
>>>>
>>>>    Current status:
>>>>     * 39 projects EE4J projects
>>>>     * 12 projects have their own Jenkins instance
>>>>     *  9 projects have a JIPP on our old infra
>>>>     *  3 projects have a JIPP on our new infra (CJE)
>>>>     *  6 projects have a working build/release pipeline
>>>>
>>>>    All projects that don't have a JIPP yet, will get a JIPP on the new
>>>>    infra. We are currently working out a few issues to be able to
>>>> provide
>>>>    the environment to deploy artifacts to OSSRH/Maven Central on the
>>>>    new infra.
>>>>
>>>>    The provisioning process involves quite a few manual steps (including
>>>>    creating GitHub bot users, setting up OSSRH accounts, etc.) and is
>>>>    therefore people-bound.
>>>>
>>>>    We will aim to provision five new Jenkins instances per week,
>>>> starting
>>>>    next week (Week 38).
>>>>
>>>>    If projects need to be prioritized, this can be incorporated, but
>>>> will
>>>>    affect other projects (provisioning will be pushed back).
>>>>
>>>>    Please see this Google spreadsheet for status and planned
>>>>    provisioning week:
>>>>    https://docs.google.com/spreadsheets/d/1O2NA6YddYQy34riTabQd_lkNwwFzKq1HevxCJYNXrv4/edit?usp=sharing
>>>>
>>>>    Please let us know, if you have any questions or concerns.
>>>>
>>>>    Regards,
>>>>
>>>>    Fred
>>>>
>>>>
>>>>    -- 
>>>>    Frederic Gurr
>>>>    Release Engineer | Eclipse Foundation Europe GmbH
>>>>
>>>>    Annastr. 44, D-64673 Zwingenberg
>>>>    Handelsregister: Darmstadt HRB 92821
>>>>    Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque
>>>>    _______________________________________________
>>>>    ee4j-build mailing list
>>>>    ee4j-build@xxxxxxxxxxx
>>>> <mailto:ee4j-build@xxxxxxxxxxx> <mailto:ee4j-build@xxxxxxxxxxx>
>>>>    To change your delivery options, retrieve your password, or
>>>>    unsubscribe from this list, visit
>>>>    https://dev.eclipse.org/mailman/listinfo/ee4j-build
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> ee4j-build mailing list
>>>> ee4j-build@xxxxxxxxxxx <mailto:ee4j-build@xxxxxxxxxxx>
>>>> To change your delivery options, retrieve your password, or
>>>> unsubscribe from this list, visit
>>>> https://dev.eclipse.org/mailman/listinfo/ee4j-build
>>>>
>>>
>>> -- 
>>> Frederic Gurr
>>> Release Engineer | Eclipse Foundation Europe GmbH
>>>
>>> Annastr. 44, D-64673 Zwingenberg
>>> Handelsregister: Darmstadt HRB 92821
>>> Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque
>>> _______________________________________________
>>> ee4j-build mailing list
>>> ee4j-build@xxxxxxxxxxx <mailto:ee4j-build@xxxxxxxxxxx>
>>> To change your delivery options, retrieve your password, or
>>> unsubscribe from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/ee4j-build
>>
>> _______________________________________________
>> ee4j-build mailing list
>> ee4j-build@xxxxxxxxxxx <mailto:ee4j-build@xxxxxxxxxxx>
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/ee4j-build
>
>
>
> _______________________________________________
> ee4j-build mailing list
> ee4j-build@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ee4j-build
>

--
Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH

Annastr. 44, D-64673 Zwingenberg
Handelsregister: Darmstadt HRB 92821
Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-build
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-build

Attachment: signature.asc
Description: Message signed with OpenPGP


Back to the top