I'm just a bit biased (I work for Replicated), but yeah, this is exactly what Replicated does.

https://www.replicated.com/

I don't want to get all salesy here, but I'm happy to answer any questions you have, or connect you with folks for a demo, etc.

So that's what they've been doing with all the Heroku people they've been hiring.

http://hashiroku.com/

Hi HN,

We (Replicated) are getting ready to launch a new open source project, Troubleshoot, and I'd like your early feedback. It's basically a set of two `kubectl` plugins that provide the ability to run preflight checks before installing an application and generate support bundles after installing an application.

It's been part of Replicated's products, but now we're making it available as a separate open source project in hopes that others may find it useful for their own projects, or even just for debugging your own Kubernetes clusters.

I'd suggest a name that's a bit more unique than that.

Thanks for the suggestion. It spun out of a feature in our main product, but I admit that as a standalone project, it's a bit too broad of a name. It's already caused some confusion in the Kubernetes Slack.

Thanks for bringing this up. As mentioned in our blog post on the subject (https://about.gitlab.com/blog/2019/07/30/gitlab-acquisitions...), we'll consider other types of acquisitions, but this is a streamlined process specifically for soft-landings. I've opened an issue to clarify this on the handbook page. https://gitlab.com/gitlab-com/corporate-development/issues/4

FWIW, if you disable Pipelines and push another commit to the repo, you'll clear the failed icon from the project page. The project page only shows the last commit and the failed status is associated with the specific commit, not the project as a whole.

The profile page, however, doesn't seem to update. My guess is that it's a caching problem. I've logged https://gitlab.com/gitlab-org/gitlab-ce/issues/52780 for this.

Also created https://gitlab.com/gitlab-org/gitlab-ce/issues/52779 to discuss not making Auto DevOps pipelines show failure at all.

That is weird behavior. Here's an issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/52778

Maven repository is coming in 11.3!

Definitely not. Presumably the gold subscription would be associated with a group for your open source projects, and your personal private projects would be completely separate (and free, just with Core functionality).

FWIW, if you created the connection between GitLab and GitHub for your project before 10.6, you'll have to remove the connection and then re-add it to get the push-based mirroring to happen. Otherwise, yes, it will still poll.

How do you do this?

It seems like you should be able to do this, but there may need to be an update to work with already-mirrored repos since the feature was designed to have a flow that expects a new project to be created.

I've logged an issue to track down the process: https://gitlab.com/gitlab-org/gitlab-ce/issues/44552

Thanks for pointing this out. Changed with https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/....

Advancedness is not a criteria in open sourcing or not open sourcing. There are advanced features that are open source, such as Review Apps[0]. There are basic features that are proprietary, such as File Locking[1]. The criteria we use to decide which version the features go in are documented on our stewardship page[2].

[0] https://about.gitlab.com/features/review-apps/ [1] https://about.gitlab.com/features/file-locking/ [2] https://about.gitlab.com/stewardship/#what-features-are-ee-o...