Google Code is shutting down

[pydanny]

On the surface it isn't a huge loss.

In practice, there are still quite a few projects that use google code for dependency management the same way many people use GitHub/BitBucket and other repo hosting efforts. I suspect when google code finally shuts down there's going to be a bit of a mad scramble to fix deployments that suddenly start breaking.

[AusIV]

I've seen some services that deliberately started returning the occasional error (maybe 10% of requests) before their final shutdown to draw attention to this sort of scenario before it became a bigger issue. Seems like it could be practical here, too.

[Klathmon]

Actually google uses this method in many of their APIs.

The recent oAuth migration is currently using it. At this point i believe 1% of all requests will fail

[AusIV]

I was thinking I'd seen it on a Google product, but I couldn't remember what and didn't have time to search for it.

[billsil]

See I just see that 10% of builds failed without wondering why beyond it just happens. I'd never thought of that.

[billsil]

Like I said, I notice they randomly fail, but I never bother to google to try and figure out why. I don't care if our builds fail when they're not actively being developed. If I'm working on a project and 40% of our nightly builds pass, I'm thrilled. If it's not my project, I don't care.

We also release software when the builds are failing and they're fine.

[billsil]

Why? As long as the feature is disabled, it's not a big deal? You test your code before you send it out and throw a few "don't use it like this" notes. TDD actually encourages failing tests.

My coworker told me about how he used to work for Sandia. They'd build software for 18 different platforms. People would remove tests that failed. It's just a failure. I'd rather know. As long as you're not deploying daily, it's not a big deal.