[Travis/GitHub] Migrating SELinuxProject projects to travis-ci.com (vs. travis-ci.org)

[Travis/GitHub] Migrating SELinuxProject projects to travis-ci.com (vs. travis-ci.org)

[Ondrej Mosnacek]

Hello everyone (mainly the maintainers of projects on GH, but to avoid
a huge cc list, I'm sending this to the ML),

As you may or may not know, Travis is migrating open-source projects
to their main site [1][2] (to .com from .org, where they have been
until now). AFAIK, the functionality stays pretty much the same, they
just want to have open-source and private projects under the same
infrastructure to unify things.

Recently, they started migrating runners away from the .org site [3],
resulting in new builds being queued for a very long time. [4]

I tried to migrate some of my forks (selinux-testsuite and selinux) to
the new site and it went smoothly. The only downside seems to be that
the build history is not migrated immediately (but it did show up
after a while). The queue times were indeed resolved after the
migration.

So, I'd like to propose to start migrating the projects under
SELinuxProject that use the Travis CI (selinux, refpolicy,
selinux-testsuite, setools) now, so that we are not affected by the
lack of workers.

If there are no objections until next week, I'll migrate the
selinux-testsuite, for a start. The other projects I'll leave for the
other maintainers, unless they choose to mandate me to do so :)

[1] https://docs.travis-ci.com/user/migrate/open-source-repository-migration
[2] https://travis-ci.community/t/org-to-com-migration-deadline/10260
[3] https://travis-ci.community/t/builds-hang-in-queued-state/10250/6
[4] https://www.traviscistatus.com/

--
Ondrej Mosnacek
Software Engineer, Platform Security - SELinux kernel
Red Hat, Inc.

Re: [Travis/GitHub] Migrating SELinuxProject projects to travis-ci.com (vs. travis-ci.org)

[Paul Moore]

On Mon, Oct 26, 2020 at 9:54 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> Hello everyone (mainly the maintainers of projects on GH, but to avoid
> a huge cc list, I'm sending this to the ML),
>
> As you may or may not know, Travis is migrating open-source projects
> to their main site [1][2] (to .com from .org, where they have been
> until now). AFAIK, the functionality stays pretty much the same, they
> just want to have open-source and private projects under the same
> infrastructure to unify things.
>
> Recently, they started migrating runners away from the .org site [3],
> resulting in new builds being queued for a very long time. [4]
>
> I tried to migrate some of my forks (selinux-testsuite and selinux) to
> the new site and it went smoothly. The only downside seems to be that
> the build history is not migrated immediately (but it did show up
> after a while). The queue times were indeed resolved after the
> migration.
>
> So, I'd like to propose to start migrating the projects under
> SELinuxProject that use the Travis CI (selinux, refpolicy,
> selinux-testsuite, setools) now, so that we are not affected by the
> lack of workers.
>
> If there are no objections until next week, I'll migrate the
> selinux-testsuite, for a start. The other projects I'll leave for the
> other maintainers, unless they choose to mandate me to do so :)

Sounds good to me.

-- 
paul moore
www.paul-moore.com

Re: [Travis/GitHub] Migrating SELinuxProject projects to travis-ci.com (vs. travis-ci.org)

[Petr Lautrbach]

[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]

On Mon, Oct 26, 2020 at 07:04:52PM -0400, Paul Moore wrote:
> On Mon, Oct 26, 2020 at 9:54 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> > Hello everyone (mainly the maintainers of projects on GH, but to avoid
> > a huge cc list, I'm sending this to the ML),
> >
> > As you may or may not know, Travis is migrating open-source projects
> > to their main site [1][2] (to .com from .org, where they have been
> > until now). AFAIK, the functionality stays pretty much the same, they
> > just want to have open-source and private projects under the same
> > infrastructure to unify things.
> >
> > Recently, they started migrating runners away from the .org site [3],
> > resulting in new builds being queued for a very long time. [4]
> >
> > I tried to migrate some of my forks (selinux-testsuite and selinux) to
> > the new site and it went smoothly. The only downside seems to be that
> > the build history is not migrated immediately (but it did show up
> > after a while). The queue times were indeed resolved after the
> > migration.
> >
> > So, I'd like to propose to start migrating the projects under
> > SELinuxProject that use the Travis CI (selinux, refpolicy,
> > selinux-testsuite, setools) now, so that we are not affected by the
> > lack of workers.
> >
> > If there are no objections until next week, I'll migrate the
> > selinux-testsuite, for a start. The other projects I'll leave for the
> > other maintainers, unless they choose to mandate me to do so :)
> 
> Sounds good to me.
> 

Please do it for selinux too. Thank you!

Petr

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [Travis/GitHub] Migrating SELinuxProject projects to travis-ci.com (vs. travis-ci.org)

[Ondrej Mosnacek]

On Tue, Oct 27, 2020 at 5:37 PM Petr Lautrbach <plautrba@redhat.com> wrote:
> On Mon, Oct 26, 2020 at 07:04:52PM -0400, Paul Moore wrote:
> > On Mon, Oct 26, 2020 at 9:54 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> > > Hello everyone (mainly the maintainers of projects on GH, but to avoid
> > > a huge cc list, I'm sending this to the ML),
> > >
> > > As you may or may not know, Travis is migrating open-source projects
> > > to their main site [1][2] (to .com from .org, where they have been
> > > until now). AFAIK, the functionality stays pretty much the same, they
> > > just want to have open-source and private projects under the same
> > > infrastructure to unify things.
> > >
> > > Recently, they started migrating runners away from the .org site [3],
> > > resulting in new builds being queued for a very long time. [4]
> > >
> > > I tried to migrate some of my forks (selinux-testsuite and selinux) to
> > > the new site and it went smoothly. The only downside seems to be that
> > > the build history is not migrated immediately (but it did show up
> > > after a while). The queue times were indeed resolved after the
> > > migration.
> > >
> > > So, I'd like to propose to start migrating the projects under
> > > SELinuxProject that use the Travis CI (selinux, refpolicy,
> > > selinux-testsuite, setools) now, so that we are not affected by the
> > > lack of workers.
> > >
> > > If there are no objections until next week, I'll migrate the
> > > selinux-testsuite, for a start. The other projects I'll leave for the
> > > other maintainers, unless they choose to mandate me to do so :)
> >
> > Sounds good to me.
> >
>
> Please do it for selinux too. Thank you!

Apparently I would need to be an admin/owner in the SELinuxProject
group to do anything... So either one of the owners will have to do it
or make me an owner :)

--
Ondrej Mosnacek
Software Engineer, Platform Security - SELinux kernel
Red Hat, Inc.

Re: [Travis/GitHub] Migrating SELinuxProject projects to travis-ci.com (vs. travis-ci.org)

[Paul Moore]

On Mon, Nov 2, 2020 at 3:04 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> On Tue, Oct 27, 2020 at 5:37 PM Petr Lautrbach <plautrba@redhat.com> wrote:
> > On Mon, Oct 26, 2020 at 07:04:52PM -0400, Paul Moore wrote:
> > > On Mon, Oct 26, 2020 at 9:54 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> > > > Hello everyone (mainly the maintainers of projects on GH, but to avoid
> > > > a huge cc list, I'm sending this to the ML),
> > > >
> > > > As you may or may not know, Travis is migrating open-source projects
> > > > to their main site [1][2] (to .com from .org, where they have been
> > > > until now). AFAIK, the functionality stays pretty much the same, they
> > > > just want to have open-source and private projects under the same
> > > > infrastructure to unify things.
> > > >
> > > > Recently, they started migrating runners away from the .org site [3],
> > > > resulting in new builds being queued for a very long time. [4]
> > > >
> > > > I tried to migrate some of my forks (selinux-testsuite and selinux) to
> > > > the new site and it went smoothly. The only downside seems to be that
> > > > the build history is not migrated immediately (but it did show up
> > > > after a while). The queue times were indeed resolved after the
> > > > migration.
> > > >
> > > > So, I'd like to propose to start migrating the projects under
> > > > SELinuxProject that use the Travis CI (selinux, refpolicy,
> > > > selinux-testsuite, setools) now, so that we are not affected by the
> > > > lack of workers.
> > > >
> > > > If there are no objections until next week, I'll migrate the
> > > > selinux-testsuite, for a start. The other projects I'll leave for the
> > > > other maintainers, unless they choose to mandate me to do so :)
> > >
> > > Sounds good to me.
> > >
> >
> > Please do it for selinux too. Thank you!
>
> Apparently I would need to be an admin/owner in the SELinuxProject
> group to do anything... So either one of the owners will have to do it
> or make me an owner :)

Done :)

Originally I think the initial list of folks were all added as
"owners", but as we added maintainers to the various projects it seems
the new additions defaulted to "members".  You should be all set as an
owner now Ondrej, and if any of the other current maintainers would
also like to have their roles adjusted feel free to ping me off-list.

-- 
paul moore
www.paul-moore.com

Re: [Travis/GitHub] Migrating SELinuxProject projects to travis-ci.com (vs. travis-ci.org)

[Ondrej Mosnacek]

On Mon, Nov 2, 2020 at 3:46 PM Paul Moore <paul@paul-moore.com> wrote:
> On Mon, Nov 2, 2020 at 3:04 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> > On Tue, Oct 27, 2020 at 5:37 PM Petr Lautrbach <plautrba@redhat.com> wrote:
> > > On Mon, Oct 26, 2020 at 07:04:52PM -0400, Paul Moore wrote:
> > > > On Mon, Oct 26, 2020 at 9:54 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> > > > > Hello everyone (mainly the maintainers of projects on GH, but to avoid
> > > > > a huge cc list, I'm sending this to the ML),
> > > > >
> > > > > As you may or may not know, Travis is migrating open-source projects
> > > > > to their main site [1][2] (to .com from .org, where they have been
> > > > > until now). AFAIK, the functionality stays pretty much the same, they
> > > > > just want to have open-source and private projects under the same
> > > > > infrastructure to unify things.
> > > > >
> > > > > Recently, they started migrating runners away from the .org site [3],
> > > > > resulting in new builds being queued for a very long time. [4]
> > > > >
> > > > > I tried to migrate some of my forks (selinux-testsuite and selinux) to
> > > > > the new site and it went smoothly. The only downside seems to be that
> > > > > the build history is not migrated immediately (but it did show up
> > > > > after a while). The queue times were indeed resolved after the
> > > > > migration.
> > > > >
> > > > > So, I'd like to propose to start migrating the projects under
> > > > > SELinuxProject that use the Travis CI (selinux, refpolicy,
> > > > > selinux-testsuite, setools) now, so that we are not affected by the
> > > > > lack of workers.
> > > > >
> > > > > If there are no objections until next week, I'll migrate the
> > > > > selinux-testsuite, for a start. The other projects I'll leave for the
> > > > > other maintainers, unless they choose to mandate me to do so :)
> > > >
> > > > Sounds good to me.
> > > >
> > >
> > > Please do it for selinux too. Thank you!
> >
> > Apparently I would need to be an admin/owner in the SELinuxProject
> > group to do anything... So either one of the owners will have to do it
> > or make me an owner :)
>
> Done :)

Thanks, I've just migrated selinux and selinux-testsuite:
https://travis-ci.com/github/SELinuxProject

I can also migrate refpolicy and setools if Chris gives me a thumbs-up.

-- 
Ondrej Mosnacek
Software Engineer, Platform Security - SELinux kernel
Red Hat, Inc.

Re: [Travis/GitHub] Migrating SELinuxProject projects to travis-ci.com (vs. travis-ci.org)

[Chris PeBenito]

On 11/2/20 10:18 AM, Ondrej Mosnacek wrote:
> On Mon, Nov 2, 2020 at 3:46 PM Paul Moore <paul@paul-moore.com> wrote:
>> On Mon, Nov 2, 2020 at 3:04 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
>>> On Tue, Oct 27, 2020 at 5:37 PM Petr Lautrbach <plautrba@redhat.com> wrote:
>>>> On Mon, Oct 26, 2020 at 07:04:52PM -0400, Paul Moore wrote:
>>>>> On Mon, Oct 26, 2020 at 9:54 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
>>>>>> Hello everyone (mainly the maintainers of projects on GH, but to avoid
>>>>>> a huge cc list, I'm sending this to the ML),
>>>>>>
>>>>>> As you may or may not know, Travis is migrating open-source projects
>>>>>> to their main site [1][2] (to .com from .org, where they have been
>>>>>> until now). AFAIK, the functionality stays pretty much the same, they
>>>>>> just want to have open-source and private projects under the same
>>>>>> infrastructure to unify things.
>>>>>>
>>>>>> Recently, they started migrating runners away from the .org site [3],
>>>>>> resulting in new builds being queued for a very long time. [4]
>>>>>>
>>>>>> I tried to migrate some of my forks (selinux-testsuite and selinux) to
>>>>>> the new site and it went smoothly. The only downside seems to be that
>>>>>> the build history is not migrated immediately (but it did show up
>>>>>> after a while). The queue times were indeed resolved after the
>>>>>> migration.
>>>>>>
>>>>>> So, I'd like to propose to start migrating the projects under
>>>>>> SELinuxProject that use the Travis CI (selinux, refpolicy,
>>>>>> selinux-testsuite, setools) now, so that we are not affected by the
>>>>>> lack of workers.
>>>>>>
>>>>>> If there are no objections until next week, I'll migrate the
>>>>>> selinux-testsuite, for a start. The other projects I'll leave for the
>>>>>> other maintainers, unless they choose to mandate me to do so :)
>>>>>
>>>>> Sounds good to me.
>>>>>
>>>>
>>>> Please do it for selinux too. Thank you!
>>>
>>> Apparently I would need to be an admin/owner in the SELinuxProject
>>> group to do anything... So either one of the owners will have to do it
>>> or make me an owner :)
>>
>> Done :)
> 
> Thanks, I've just migrated selinux and selinux-testsuite:
> https://travis-ci.com/github/SELinuxProject
> 
> I can also migrate refpolicy and setools if Chris gives me a thumbs-up.

Sure, go ahead. Thanks Ondrej!

-- 
Chris PeBenito

Re: [Travis/GitHub] Migrating SELinuxProject projects to travis-ci.com (vs. travis-ci.org)

[Ondrej Mosnacek]

On Thu, Nov 5, 2020 at 12:51 PM Chris PeBenito <pebenito@ieee.org> wrote:
> On 11/2/20 10:18 AM, Ondrej Mosnacek wrote:
> > On Mon, Nov 2, 2020 at 3:46 PM Paul Moore <paul@paul-moore.com> wrote:
> >> On Mon, Nov 2, 2020 at 3:04 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> >>> On Tue, Oct 27, 2020 at 5:37 PM Petr Lautrbach <plautrba@redhat.com> wrote:
> >>>> On Mon, Oct 26, 2020 at 07:04:52PM -0400, Paul Moore wrote:
> >>>>> On Mon, Oct 26, 2020 at 9:54 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> >>>>>> Hello everyone (mainly the maintainers of projects on GH, but to avoid
> >>>>>> a huge cc list, I'm sending this to the ML),
> >>>>>>
> >>>>>> As you may or may not know, Travis is migrating open-source projects
> >>>>>> to their main site [1][2] (to .com from .org, where they have been
> >>>>>> until now). AFAIK, the functionality stays pretty much the same, they
> >>>>>> just want to have open-source and private projects under the same
> >>>>>> infrastructure to unify things.
> >>>>>>
> >>>>>> Recently, they started migrating runners away from the .org site [3],
> >>>>>> resulting in new builds being queued for a very long time. [4]
> >>>>>>
> >>>>>> I tried to migrate some of my forks (selinux-testsuite and selinux) to
> >>>>>> the new site and it went smoothly. The only downside seems to be that
> >>>>>> the build history is not migrated immediately (but it did show up
> >>>>>> after a while). The queue times were indeed resolved after the
> >>>>>> migration.
> >>>>>>
> >>>>>> So, I'd like to propose to start migrating the projects under
> >>>>>> SELinuxProject that use the Travis CI (selinux, refpolicy,
> >>>>>> selinux-testsuite, setools) now, so that we are not affected by the
> >>>>>> lack of workers.
> >>>>>>
> >>>>>> If there are no objections until next week, I'll migrate the
> >>>>>> selinux-testsuite, for a start. The other projects I'll leave for the
> >>>>>> other maintainers, unless they choose to mandate me to do so :)
> >>>>>
> >>>>> Sounds good to me.
> >>>>>
> >>>>
> >>>> Please do it for selinux too. Thank you!
> >>>
> >>> Apparently I would need to be an admin/owner in the SELinuxProject
> >>> group to do anything... So either one of the owners will have to do it
> >>> or make me an owner :)
> >>
> >> Done :)
> >
> > Thanks, I've just migrated selinux and selinux-testsuite:
> > https://travis-ci.com/github/SELinuxProject
> >
> > I can also migrate refpolicy and setools if Chris gives me a thumbs-up.
>
> Sure, go ahead. Thanks Ondrej!

Done. The currently running build is still running on the old server,
future builds should already run on the new one.

Also, you'll want to read Bill's email, which unfortunately doesn't
contain good news :(
https://lore.kernel.org/selinux/CAFftDdo-jFy4anQaVvQqtYgjRvG8w-TNNLOUU5JL11gQF_rCpQ@mail.gmail.com/
(I'm not sure if I didn't make thing worse with the early migration,
since the linked announcement only mentions travis-ci.com, but I'm
sure they'd come for us sooner or later, anyway...)

--
Ondrej Mosnacek
Software Engineer, Platform Security - SELinux kernel
Red Hat, Inc.