Re: [cross-project-issues-dev] Backend storage migration of Jenkins inst

[Frederic Gurr <frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx>]

No, repo.eclipse.org is not migrated yet, but we are working on it.

On 27.09.24 09:21, Aleksandar Kurtakov via cross-project-issues-dev wrote:
> Is repo.eclipse.org <http://repo.eclipse.org> migrated already? It 
> should get the attention first as it's the most common reason for 
> failing builds.
>
> On Thu, Sep 26, 2024 at 11:16 PM Frederic Gurr via 
> cross-project-issues-dev <cross-project-issues-dev@xxxxxxxxxxx 
> <mailto:cross-project-issues-dev@xxxxxxxxxxx>> wrote:
>
>     P.S.: If you have any questions or concerns, please let me know or
>     comment on bug
>     https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5054
>     <https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5054> where we
>     are also tracking this effort.
>
>     Regards,
>
>     Fred
>
>     On 26.09.24 22:10, Frederic Gurr wrote:
>      > Hi,
>      >
>      > As you might have noticed, we have been facing some backend storage
>      > issues that affect several services, most noticeable
>     repo.eclipse.org <http://repo.eclipse.org>
>      > and several Jenkins instances. In order to fix this, we need
>      > to migrate all Jenkins Home dirs to a different storage device.
>      >
>      > For most of the Jenkins instances that are rather small, this
>     migration
>      > can be done quite quickly in half an hour or less.
>      > For a handful of Jenkins instances, the migration will take longer,
>      > depending on the used disk space and the number of files.
>      > During the migration, the Jenkins instances will be offline.
>     After the
>      > migration, everything should work as before.
>      >
>      > During the next few weeks, smaller instances will be migrated,
>     when it's
>      > their turn. If required, we will announce maintenance windows
>      > for larger instances.
>      >
>      > In order to speed up the migration, we would like to encourage all
>      > projects to clean up their Jenkins instances:
>      > * Get rid of old build jobs (especially if they are several years
>     old)
>      > * Limit the number of builds to keep with artifacts (remember that
>      > Jenkins is not a file server)
>      > * Please make sure that Multibranch pipeline jobs have the following
>      > settings enabled:
>      >    * Scan Repository Triggers -> Periodically if not otherwise
>     run: 2 days
>      >    * Orphaned Item Strategy -> Discard old items -> Max # of old
>     items
>      > to keep: 5
>      >
>      > See also
>     https://github.com/eclipse-cbi/jiro/wiki/CI-Best-Practices
>     <https://github.com/eclipse-cbi/jiro/wiki/CI-Best-Practices>
>      >
>      > Your support in this effort is much appreciated.
>      >
>      >
>      > Regards,
>      >
>      > Fred
>      >
>      >
>
>     -- 
>     Frederic Gurr
>     Team Lead - Release Engineering | Eclipse Foundation Europe GmbH
>
>     Berliner Allee 47, D-64295 Darmstadt
>     Handelsregister: Darmstadt HRB 92821
>     Managing Directors: Gaël Blondelle, Mike Milinkovich, Michael Plagge
>     _______________________________________________
>     cross-project-issues-dev mailing list
>     cross-project-issues-dev@xxxxxxxxxxx
>     <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>     To unsubscribe from this list, visit
>     https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>     <https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev>
>
>
>
> --
> Aleksandar Kurtakov
> Red Hat Eclipse Team
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Frederic Gurr
Team Lead - Release Engineering | Eclipse Foundation Europe GmbH

Berliner Allee 47, D-64295 Darmstadt
Handelsregister: Darmstadt HRB 92821
Managing Directors: Gaël Blondelle, Mike Milinkovich, Michael Plagge