Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-committers] build.eclipse.org will be going away - March 31, 2021

> So far, we have not had any feedback on CBI related to GitLab. Https://wiki.eclipse.org/CBI

The Eclipse ESCET project has a successful Jenkins build from our GitLab repository.

Pushes and merge requests are automatically picked up by Jenkins now, and Jenkins reports back the status/results to GitLab. Integration is very nice.

We worked on this with Frederic Gurr. See also the discussion here: https://www.eclipse.org/lists/cbi-dev/msg02307.html.

Kind regards,
Dennis Hendriks


Van: eclipse.org-committers-bounces@xxxxxxxxxxx <eclipse.org-committers-bounces@xxxxxxxxxxx> namens Denis Roy <denis.roy@xxxxxxxxxxxxxxxxxxxxxx>
Verzonden: vrijdag 18 december 2020 17:59
CC: eclipse.org-committers@xxxxxxxxxxx <eclipse.org-committers@xxxxxxxxxxx>
Onderwerp: Re: [eclipse.org-committers] build.eclipse.org will be going away - March 31, 2021
 
Some answers and comments. In the end, we realize that migrating systems
is time consuming and we're here to assist along the way.

There was a time -- several years ago -- where the complaints about
Bugzilla were frequent.  Nowadays, there are no more complaints, because
those developers have taken their projects (and development talent)
elsewhere. Remaining on the arguably niche (Gerrit) or obsolete
(Bugzilla) system is self-serving when resource constraints are at play,
but does nothing to attract new talent that does not want to use those
systems, thus exacerbating or perpetuating the resource constraint.



On 2020-12-18 2:52 a.m., Mickael Istria wrote:
>
> Thanks for rationalizing the infra with the goal of serving all of us
> better. It's a good thing overall.
> My only concern is about Bugzilla: concretely, despite its austere
> appearance, it seems to be the only trackers of all the ones available
> at the Foundation which has a semantic capability to mark issues as
> dependencies with the depends on/blocks flags.

Yes, GitLab supports issue dependency, even across repositories /
projects. See this as an example, where GitLab issue #1 is blocked by
Technology/Dash issue #146

https://gitlab.eclipse.org/eclipsefdn/gitlab/-/issues/6


On 2020-12-18 9:23 a.m., Christian Pontesegger wrote:

> It would be great if the move in infrastructure would be accompanied by
> howtos and some guidance for both developers and users.
>
> Lots of the core/platform projects are still based on
> gerrit/bugzilla/mediawiki. It would help to have some lighthouse
> projects moving and documenting in detail what to keep an eye on. This
> will help us all to move swiftly.

That is the goal; we've had a few early adopters migrate (from GitHub
and from BZ/Gerrit) and we're all taking notes. We do rely on the
community's willingness to share their own experiences with the
migration, however.

I've been maintaining the Gitlab Wiki page as I get questions and/or
concerns ( https://wiki.eclipse.org/Gitlab )  and the Releng team
maintains the CBI page. So far, we have not had any feedback on CBI
related to GitLab. Https://wiki.eclipse.org/CBI

As a note, both of those pages will need to migrate over to GitLab wiki
at some point.


Many thanks,


Denis


_______________________________________________
eclipse.org-committers mailing list
eclipse.org-committers@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-committers

Back to the top