Sravan, this is great info. please add this information to the wiki page

https://wiki.eclipse.org/Platform-releng/Migration_To_GitHub


On Wed, Mar 10, 2021 at 4:55 PM Sravan K Lakkimsetti <
[email protected]> wrote:

> The idea was if you run the scripts listed here
> https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/cje-production/mbscripts
> in ascending order(
> https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/cje-production/master-build.sh
> was supposed to do that) you should get built eclipse, equinox and update
> site along with all the reports in
> https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/cje-production/siteDir
> folder.
>
> Kit Lo(current build engineer from IBM) was able to do it when he first
> implemented. Unfortunately while adopting these scripts to work on JIRO I
> ended up breaking that workflow. If anyone likes to contribute, this would
> be a good place to start.
>
>
>
> Thanks
>
> Sravan
>
>
>
> *From:* Aleksandar Kurtakov <[email protected]>
> *Sent:* 10 March 2021 21:02
> *To:* Eclipse platform general developers list. <[email protected]>
> *Subject:* [EXTERNAL] Re: [platform-dev] Has the time come?
>
>
>
> On Wed, Mar 10, 2021 at 4:56 PM Wim Jongman <[email protected]>
> wrote: Maybe we can skip adding features completely for one or two releases
> and have all hands focusing entirely on the releng process. This is what
> some of us have been
>
>
>
>
>
> On Wed, Mar 10, 2021 at 4:56 PM Wim Jongman <[email protected]> wrote:
>
> Maybe we can skip adding features completely for one or two releases and
> have all hands focusing entirely on the releng process.
>
>
>
> This is what some of us have been doing for years  with the clear goal to
> be able to have predictable builds, shorter build times, support for newer
> JVMs and etc. But the process is not good enough. TBH I am not confident we
> can move on as easily as people think. Please try to replicate the build
> locally incl. reports generation, download pages and etc. - you will notice
> many discrepancies - pick one, open bug about it with proposal how to
> improve it and be ready to work on it.
>
> Nothing is set in stone - if we are about to merge repos - please propose
> exact things to do. I don't believe that big bang let's break everything
> will produce any good rather that constant improvements allow for better
> understanding of technical issues, requirements, implementation and etc. to
> be more robust if every step is questioned regularly.
>
>
>
>
>
> On Wed, Mar 10, 2021 at 3:42 PM Christoph Läubrich <[email protected]>
> wrote:
>
> +1 for move to github, we should take the opportunity to merge several
> repos, this cluttering of code is just a mess.
>
>
> Am 10.03.21 um 15:37 schrieb Wim Jongman:
> > Hi,
> >
> > Can we discuss the move to GitHub again?
> >
> > Cons:
> > * No Gerrit -> best review system ever
> >
> > Pros:
> > * All the developers are there.
> > * No Gerrit -> easy entry for new devs
> >
> > Cheers,
> >
> > Wim
> _______________________________________________
> platform-dev mailing list
> [email protected]
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
> _______________________________________________
> platform-dev mailing list
> [email protected]
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
>
>
> --
>
> Aleksandar Kurtakov
>
> Red Hat Eclipse Team
>
> _______________________________________________
> platform-dev mailing list
> [email protected]
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
>
_______________________________________________
platform-dev mailing list
[email protected]
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Reply via email to