[Pulp-dev] Moving to travis-ci.com

Tue May 5 12:14:28 UTC 2020

Thank you! +1 for pulp_rpm to migrate.

Tanya

On Tue, May 5, 2020 at 1:38 PM David Davis <daviddavis at redhat.com> wrote:

> I migrated over pulp_ansible, pulp-smash, and pulp-ci. I think at this
> point, these are the only pulp 3 repos still on travis-ci.org:
>
> - pulp_rpm
> - pulp_python
> - pulp_gem
>
> If any of the plugins want me to migrate these over, please let me know.
>
> David
>
>
> On Mon, May 4, 2020 at 7:12 AM Ina Panova <ipanova at redhat.com> wrote:
>
>> +1 to move pulp3 projects.
>> Thank you for taking care of this.
>>
>>
>> --------
>> Regards,
>>
>> Ina Panova
>> Senior Software Engineer| Pulp| Red Hat Inc.
>>
>> "Do not go where the path may lead,
>>  go instead where there is no path and leave a trail."
>>
>>
>> On Fri, May 1, 2020 at 9:22 PM Brian Bouterse <bmbouter at redhat.com>
>> wrote:
>>
>>> Thank you for porting these! I'm +1 to moving all Pulp3 projects with an
>>> ack from each plugin team first.
>>>
>>> I can ack for pulp_ansible, if it's possible to move that one please.
>>> Let me know how I can help also.
>>>
>>> On Wed, Apr 29, 2020 at 6:43 AM David Davis <daviddavis at redhat.com>
>>> wrote:
>>>
>>>> Out of curiosity this morning I tried migrating pulp_file over to
>>>> travis-ci this morning and it worked. So then I went back and tried
>>>> pulp-certguard and that worked as well. So now both projects are on
>>>> travis-ci.com.
>>>>
>>>> I think these are the main projects still on travis-ci.org:
>>>> - pulp_ansible
>>>> - pulp_rpm
>>>> - pulp
>>>> - pulp_python
>>>> - pulp_gem
>>>> - pulp-smash
>>>> - pulp-ci
>>>> - Pulp-2-Tests
>>>> - pulp_ostree
>>>> - crane
>>>>
>>>> Should we move these projects over as well? Maybe just the Pulp 3 ones?
>>>> I'd also like confirmation from plugin teams though before we move their
>>>> repos over.
>>>>
>>>> David
>>>>
>>>>
>>>> On Thu, Apr 23, 2020 at 11:01 AM Daniel Alley <dalley at redhat.com>
>>>> wrote:
>>>>
>>>>> I kid, but it is a funny situation
>>>>>
>>>>> On Thu, Apr 23, 2020 at 10:01 AM David Davis <daviddavis at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> LOL.
>>>>>>
>>>>>> To answer your question though, we're kind of in a holding pattern
>>>>>> right now. There are some missing features like sharing jobs between
>>>>>> workflows and restarting jobs within workflows that we're hoping Github
>>>>>> Actions adds. Maybe we can revisit though at our next CI meeting.
>>>>>>
>>>>>> David
>>>>>>
>>>>>>
>>>>>> On Thu, Apr 23, 2020 at 9:46 AM Daniel Alley <dalley at redhat.com>
>>>>>> wrote:
>>>>>>
>>>>>>> travis-ci.org is broken
>>>>>>>>
>>>>>>> migrating away from travis-ci.org is also broken
>>>>>>>>
>>>>>>>
>>>>>>> So, uh, when will github actions be ready xD
>>>>>>>
>>>>>>> On Thu, Apr 23, 2020 at 8:40 AM David Davis <daviddavis at redhat.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I wrote to Travis support yesterday and they responded (below). I
>>>>>>>> tried again this morning and it's still broken. I'll wait a few more days
>>>>>>>> unless anyone objects.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *Thank you for reaching out! We are sorry about the issue that you
>>>>>>>> are having.We are currently aware of a bug related to migrating
>>>>>>>> repositories from travis-ci.org <http://travis-ci.org> to travis-ci.com
>>>>>>>> <http://travis-ci.com> and our Engineering Team is working on this issue to
>>>>>>>> be solved as soon as possible.Until the fix is deployed, we would kindly
>>>>>>>> suggest you build your projects on travis-ci.org
>>>>>>>> <http://travis-ci.org>.Thank you for your patience and once again we are
>>>>>>>> extremely sorry about the issue.*
>>>>>>>>
>>>>>>>> David
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Apr 23, 2020 at 8:34 AM Brian Bouterse <bmbouter at redhat.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Apr 22, 2020 at 3:48 PM David Davis <daviddavis at redhat.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Ok, I agree. I tried to migrate certguard to travis-ci.com and
>>>>>>>>>> hit a 500 error. Looks like we're not alone both in status updates not
>>>>>>>>>> being reported from travis-ci.org and having problems trying to
>>>>>>>>>> migrate:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> https://travis-ci.community/t/github-status-not-posted-on-commits-on-repositories-using-legacy-service-integration/7798/16
>>>>>>>>>>
>>>>>>>>>> I'll wait a day for Travis support to respond but I think we
>>>>>>>>>> could also just enable the repos and start from scratch in
>>>>>>>>>> travis-ci.com. I think we'd lose past build information and
>>>>>>>>>> settings though if we don't migrate.
>>>>>>>>>>
>>>>>>>>> This also sounds good to me. If you want to tag-team via irc or
>>>>>>>>> video we can do that.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> David
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Apr 22, 2020 at 3:21 PM Brian Bouterse <
>>>>>>>>>> bmbouter at redhat.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> OK now more than an annoyance, travis-ci.org not notifying
>>>>>>>>>>> github is preventing certguard from merging without me disabling the CI
>>>>>>>>>>> check  :(
>>>>>>>>>>>
>>>>>>>>>>> I think we need to do this asap.
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Apr 22, 2020 at 9:21 AM Brian Bouterse <
>>>>>>>>>>> bmbouter at redhat.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I don't know the answer to your question about capacity, but
>>>>>>>>>>>> I've been hitting this "not-updating-github" issue a lot recently. +1 to
>>>>>>>>>>>> moving everything to travis-ci.com.
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Apr 15, 2020 at 1:55 PM David Davis <
>>>>>>>>>>>> daviddavis at redhat.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> A week or two ago, build statuses for repos whose Ci is hosted
>>>>>>>>>>>>> on travis-ci.org failed to be reported back to Github. This
>>>>>>>>>>>>> thread in the Travis support forum about the issue[0] seems to recommend
>>>>>>>>>>>>> that we migrate off travis-ci.org. My one question is whether
>>>>>>>>>>>>> we'd experience more congestion if we had all our repos on
>>>>>>>>>>>>> travis-ci.com I know this has been an issue in the past.
>>>>>>>>>>>>>
>>>>>>>>>>>>> [0]
>>>>>>>>>>>>> https://travis-ci.community/t/github-status-not-posted-on-commits-on-repositories-using-legacy-service-integration/7798/14
>>>>>>>>>>>>>
>>>>>>>>>>>>> David
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> Pulp-dev mailing list
>>>>>>>>>>>>> Pulp-dev at redhat.com
>>>>>>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>> Pulp-dev mailing list
>>>>>>>> Pulp-dev at redhat.com
>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>>>>>>
>>>>>>> _______________________________________________
>>> Pulp-dev mailing list
>>> Pulp-dev at redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>
>> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20200505/c4bbb225/attachment.htm>