[jrochkind1]

I've been worried about travis' lack of urgency in dealing with the fact that the existing travis-ci.org github hooks used for open source products are going to stop working in a week or two...

https://github.com/travis-ci/travis-ci/issues/9745

Now bought by a private equity firm, which usually doesn't indicate lots of innovation or an increase in quality on the way.

I wonder if I should be worried and start migrating my projects. I really liked travis for so long.

[DrTorte]

Hey there,

(Disclosure: Travis CI Employee)

The migration from GitHub hooks is actually just about complete. You can see the changelog entry here: https://changelog.travis-ci.com/migrating-from-github-servic...

Apologies for the lack of public updates on this!

[jrochkind1]

Thanks! Good to know.

Really kind of down to the wire though, eh?

It would be really disastrous if the deadline were to be missed, but even if it goes smoothly in the end, how it's been handled does not inspire confidence. One documentation page still says "The migration was planned to start at the end of Q2 2018, but has been pushed back. We will announce a new date as soon as we are able." --https://docs.travis-ci.com/user/open-source-on-travis-ci-com...

[DrTorte]

It's definitely not ideal, but it is less dangerous and close-to-the-wire than it sounds. It's actually separate from the migration to .com - which is something we haven't been great at communicating, and after talking it over yesterday, we're going to post something to clarify it a bit further. (Even working here, I was personally rather confused about it, and was running around yesterday chasing people down for answers.) The short of it as follows, though:

GitHub Services are going away. This is what .org relied on previously, and we are now mid process of getting everyone moved over to Webhooks instead. So, .org will rely on Webhooks instead.

In the meanwhile, we are still working on getting everyone migrated over to .com as well (which uses GitHub Apps), but that's unfortunately been a bit of a trickier beast than expected. We're still very much working on it, though. Hope that clears it up a bit!

EDIT: We are updating the docs to reflect this. :)

[jrochkind1]

Oh I see.

Yes, I thought the two migrations were the same thing. I think maybe y'all thought they were too until recently when you realized you weren't gonna get it done in time?

After all, if the migration to .com really _had_ started in Q2 2018, it probably would have been done long before Github Services went away, and you wouldn't have had to fix .org like you do now. Maybe that's what travis was assuming originally... if at some point that changed, it wasn't communicated clearly, as you acknowledge.

I also was thinking in terms of "the GH api that .org uses that's going away", and "the GH api that .com uses that isn't." I didn't realize there are actually THREE separate GH integration APIs involved? "Github Services", which .org used to use, and is going away. "Github Webhooks" which .org will use soon. And "Github App", which .com uses?

It's all very confusing.

But that's why it's incumbent on y'all to explain it. When we get a warning from Github some ~8 months ago that travis is using deprecated API's that will go away on Jan 31st, and travis is unable to tell us anything much about the schedule or plan for doing something about that until Jan 20th, and it's still pretty vague... that's either a failure of planning or failure of communication or both on travis' part. None of us, your customers, would wait until the week before drop-dead to remove a deprecated dependency in production software when we had 8 months notice... unless we were in some kind of crisis.

On Jan 31st we will see if travis.org hosted projects keep working without interruption...

(I also don't understand why I can't _choose_ to migrate my app from .org to .com at any time. _Some_ of my peers _have_ migrated their apps, with self-service web UI, but my projects it won't let me. NEW open source projects can be on .com for free. But my existing ones on .org are stuck there waiting on nobody knows what, I don't think I can even delete the project and create it anew on .com... If I'm explaining this unclearly, yes, right, exactly! I know I don't even understand what's going on, and don't want to have to, I just want it to work!

Anyway, I'm not blaming you personally, but trying to give you a flavor of one part of leading to loss of confidence in travis, which I historically have loved, for me personally. And part of that is I used to consider travis _really good_ at communicating what was going on, which as we all know is something developer-customers often value.)

[DrTorte]

Yep, totally agree that it is very confusing. Definitely appreciate all your feedback (and not taking it at all personally!) and it helps immensely. I'm gonna try to skip the PR speak, but I'm hoping we'll be able to regain that confidence when we make the right changes. :)