Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-build] Question about setting up Eclipse GlassFish repository

Ok, thanks for the update. 

For now I keep those build jobs disabled and focus on the other ones.

Werner

Ed Bratt <ed.bratt@xxxxxxxxxx> schrieb am Fr., 31. Aug. 2018, 22:45:

Werner

It is in the works now and every day it's closer. Once we submit, it will likely take some time for the ICQ (initial IP/3rd-party) clearance. I keep reporting, "real soon now" so I'm reluctant to try another date. Vacations and holidays haven't helped.

-- Ed


On 8/31/2018 11:29 AM, Werner Keil wrote:
Ed/all,

What's the timeline for migrating the Glassfish repository?
At least OpenMQ also has some integration jobs that depend on Glassfish.

Regards,
Werner


On Fri, Aug 31, 2018 at 6:59 PM Frederic Gurr <frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Ed,

I'm sure, we can adjust the provisioning process to generate less
"noise". I'd suggest to explicitly state in the Bugzilla issues that
committers should only be added later on.

Regards,

Fred

On 31.08.2018 18:33, Ed Bratt wrote:
> Hi Frederic and Mikael
>
> As we migrate repositories over to the Github eclipse-ee4j organization,
> we are also migrating the issues associated with that repository.
> Generally, we do this after the project source contribution has
> completed. The migration of issues is rather "noisy" with notifications
> from GitHub. I believe that four notices are generated for each migrated
> issue.
>
> In general, we have been migrating all issues. For GlassFish, this is
> over 22K issues. Times 4 equals a very clogged inbox (and probably
> complaints).
>
> Needless to say, this will generate an excessive number of notifications.
>
> Should we look for alternative provisioning mechanisms for this
> repository? Perhaps -- Eclipse admins set up the repository
> (eclipse-ee4j/glassfish -- then only provision the contribution user (or
> a small sub-set) -- we push the source -- migrate the issues -- /then/
> we add the remainder of the committers.
>
> Would that be something we can consider? Otherwise, I'm not sure what
> options exist, if Admins can remove watchers for the period of time it
> takes to migrate the issues, perhaps that's an alternative but we'd need
> to make sure we send notice about this so folks know what is going on.
>
> Thanks,
>
> -- Ed
>
> _______________________________________________
> 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


Back to the top