You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@archiva.apache.org by Martin <ma...@apache.org> on 2020/07/17 05:40:27 UTC
Build Server Migration
Hi together,
as Apache Infra is moving the build system to a new build server (ci-build.apache.org), we have to move our builds to the
new system. They will create a new Folder for archiva, if we request it.
Should we limit the edit access to the new archiva folder to a limit set of developers, or just give all archiva commiters edit rights?
If we are limiting the access, who should have the edit right?
Regards
Martin
RE: Build Server Migration
Posted by Eric Barboni <sk...@apache.org>.
+1
Best Regards
Eric
-----Message d'origine-----
De : Olivier Lamy <ol...@apache.org>
Envoyé : vendredi 17 juillet 2020 08:42
À : dev@archiva.apache.org
Objet : Re: Build Server Migration
Hi
I would say all archiva developers. We are not so much :)
On Fri, 17 Jul 2020 at 15:40, Martin <ma...@apache.org> wrote:
> Hi together,
>
> as Apache Infra is moving the build system to a new build server (
> ci-build.apache.org), we have to move our builds to the new system.
> They will create a new Folder for archiva, if we request it.
> Should we limit the edit access to the new archiva folder to a limit
> set of developers, or just give all archiva commiters edit rights?
> If we are limiting the access, who should have the edit right?
>
> Regards
>
> Martin
>
>
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Build Server Migration
Posted by Olivier Lamy <ol...@apache.org>.
Hi
I just fixed the settings.xml
On Thu, 23 Jul 2020 at 19:45, Eric Barboni <sk...@apache.org> wrote:
> Hi,
> Just copy / paste the Archiva gitbox TLP job. But I'm not having karma to
> read settings.xml to transfer to ci-build.
>
> I seems that during scan first candidate repo is failing the job.
>
> Best Regards
> Eric
>
> -----Message d'origine-----
> De : Olivier Lamy <ol...@apache.org>
> Envoyé : dimanche 19 juillet 2020 13:21
> À : dev@archiva.apache.org
> Objet : Re: Build Server Migration
>
> I have asked infra to install the jenkins plugin we used previously for
> scanning projects (https://github.com/apache/infrastructure-jenkins)
> this will make configuration easier.
>
> On Sat, 18 Jul 2020 at 15:16, Martin <ma...@apache.org> wrote:
>
> > Ok, ignore this. I requested edit access for all archiva commiters.
> >
> > Am Freitag, 17. Juli 2020, 19:18:20 CEST schrieb Martin:
> > > Hi,
> > >
> > > do you know, is there is a group (LDAP group) or something with the
> > archiva developers that Infra is able to assign as permitted group?
> > > If I have to provide individual names, I will add the developers
> > > that
> > are (more or less) active on this list.
> > >
> > > Regards
> > >
> > > Martin
> > >
> > > Am Freitag, 17. Juli 2020, 08:41:45 CEST schrieb Olivier Lamy:
> > > > Hi
> > > > I would say all archiva developers. We are not so much :)
> > > >
> > > > On Fri, 17 Jul 2020 at 15:40, Martin <ma...@apache.org> wrote:
> > > >
> > > > > Hi together,
> > > > >
> > > > > as Apache Infra is moving the build system to a new build server
> > > > > ( ci-build.apache.org), we have to move our builds to the new
> > > > > system. They will create a new Folder for archiva, if we request
> > it.
> > > > > Should we limit the edit access to the new archiva folder to a
> > > > > limit
> > set
> > > > > of developers, or just give all archiva commiters edit rights?
> > > > > If we are limiting the access, who should have the edit right?
> > > > >
> > > > > Regards
> > > > >
> > > > > Martin
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
RE: Build Server Migration
Posted by Eric Barboni <sk...@apache.org>.
Hi,
Just copy / paste the Archiva gitbox TLP job. But I'm not having karma to read settings.xml to transfer to ci-build.
I seems that during scan first candidate repo is failing the job.
Best Regards
Eric
-----Message d'origine-----
De : Olivier Lamy <ol...@apache.org>
Envoyé : dimanche 19 juillet 2020 13:21
À : dev@archiva.apache.org
Objet : Re: Build Server Migration
I have asked infra to install the jenkins plugin we used previously for scanning projects (https://github.com/apache/infrastructure-jenkins)
this will make configuration easier.
On Sat, 18 Jul 2020 at 15:16, Martin <ma...@apache.org> wrote:
> Ok, ignore this. I requested edit access for all archiva commiters.
>
> Am Freitag, 17. Juli 2020, 19:18:20 CEST schrieb Martin:
> > Hi,
> >
> > do you know, is there is a group (LDAP group) or something with the
> archiva developers that Infra is able to assign as permitted group?
> > If I have to provide individual names, I will add the developers
> > that
> are (more or less) active on this list.
> >
> > Regards
> >
> > Martin
> >
> > Am Freitag, 17. Juli 2020, 08:41:45 CEST schrieb Olivier Lamy:
> > > Hi
> > > I would say all archiva developers. We are not so much :)
> > >
> > > On Fri, 17 Jul 2020 at 15:40, Martin <ma...@apache.org> wrote:
> > >
> > > > Hi together,
> > > >
> > > > as Apache Infra is moving the build system to a new build server
> > > > ( ci-build.apache.org), we have to move our builds to the new
> > > > system. They will create a new Folder for archiva, if we request
> it.
> > > > Should we limit the edit access to the new archiva folder to a
> > > > limit
> set
> > > > of developers, or just give all archiva commiters edit rights?
> > > > If we are limiting the access, who should have the edit right?
> > > >
> > > > Regards
> > > >
> > > > Martin
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Build Server Migration
Posted by Olivier Lamy <ol...@apache.org>.
I have asked infra to install the jenkins plugin we used previously for
scanning projects (https://github.com/apache/infrastructure-jenkins)
this will make configuration easier.
On Sat, 18 Jul 2020 at 15:16, Martin <ma...@apache.org> wrote:
> Ok, ignore this. I requested edit access for all archiva commiters.
>
> Am Freitag, 17. Juli 2020, 19:18:20 CEST schrieb Martin:
> > Hi,
> >
> > do you know, is there is a group (LDAP group) or something with the
> archiva developers that Infra is able to assign as permitted group?
> > If I have to provide individual names, I will add the developers that
> are (more or less) active on this list.
> >
> > Regards
> >
> > Martin
> >
> > Am Freitag, 17. Juli 2020, 08:41:45 CEST schrieb Olivier Lamy:
> > > Hi
> > > I would say all archiva developers. We are not so much :)
> > >
> > > On Fri, 17 Jul 2020 at 15:40, Martin <ma...@apache.org> wrote:
> > >
> > > > Hi together,
> > > >
> > > > as Apache Infra is moving the build system to a new build server (
> > > > ci-build.apache.org), we have to move our builds to the
> > > > new system. They will create a new Folder for archiva, if we request
> it.
> > > > Should we limit the edit access to the new archiva folder to a limit
> set
> > > > of developers, or just give all archiva commiters edit rights?
> > > > If we are limiting the access, who should have the edit right?
> > > >
> > > > Regards
> > > >
> > > > Martin
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Build Server Migration
Posted by Martin <ma...@apache.org>.
Ok, ignore this. I requested edit access for all archiva commiters.
Am Freitag, 17. Juli 2020, 19:18:20 CEST schrieb Martin:
> Hi,
>
> do you know, is there is a group (LDAP group) or something with the archiva developers that Infra is able to assign as permitted group?
> If I have to provide individual names, I will add the developers that are (more or less) active on this list.
>
> Regards
>
> Martin
>
> Am Freitag, 17. Juli 2020, 08:41:45 CEST schrieb Olivier Lamy:
> > Hi
> > I would say all archiva developers. We are not so much :)
> >
> > On Fri, 17 Jul 2020 at 15:40, Martin <ma...@apache.org> wrote:
> >
> > > Hi together,
> > >
> > > as Apache Infra is moving the build system to a new build server (
> > > ci-build.apache.org), we have to move our builds to the
> > > new system. They will create a new Folder for archiva, if we request it.
> > > Should we limit the edit access to the new archiva folder to a limit set
> > > of developers, or just give all archiva commiters edit rights?
> > > If we are limiting the access, who should have the edit right?
> > >
> > > Regards
> > >
> > > Martin
> > >
> > >
> > >
> >
> >
>
>
>
>
>
>
Re: Build Server Migration
Posted by Martin <ma...@apache.org>.
Hi,
do you know, is there is a group (LDAP group) or something with the archiva developers that Infra is able to assign as permitted group?
If I have to provide individual names, I will add the developers that are (more or less) active on this list.
Regards
Martin
Am Freitag, 17. Juli 2020, 08:41:45 CEST schrieb Olivier Lamy:
> Hi
> I would say all archiva developers. We are not so much :)
>
> On Fri, 17 Jul 2020 at 15:40, Martin <ma...@apache.org> wrote:
>
> > Hi together,
> >
> > as Apache Infra is moving the build system to a new build server (
> > ci-build.apache.org), we have to move our builds to the
> > new system. They will create a new Folder for archiva, if we request it.
> > Should we limit the edit access to the new archiva folder to a limit set
> > of developers, or just give all archiva commiters edit rights?
> > If we are limiting the access, who should have the edit right?
> >
> > Regards
> >
> > Martin
> >
> >
> >
>
>
Re: Build Server Migration
Posted by Olivier Lamy <ol...@apache.org>.
Hi
I would say all archiva developers. We are not so much :)
On Fri, 17 Jul 2020 at 15:40, Martin <ma...@apache.org> wrote:
> Hi together,
>
> as Apache Infra is moving the build system to a new build server (
> ci-build.apache.org), we have to move our builds to the
> new system. They will create a new Folder for archiva, if we request it.
> Should we limit the edit access to the new archiva folder to a limit set
> of developers, or just give all archiva commiters edit rights?
> If we are limiting the access, who should have the edit right?
>
> Regards
>
> Martin
>
>
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy