Hacker News new | past | comments | ask | show | jobs | submit login

Congrats on shipping!

Sometimes new features appear straightforward but the implementation details can be complicated. For example,

https://gitlab.com/gitlab-org/gitlab-ce/issues/18157

Just off the top of my head: How do you feel about CI/CD for gitlab? I mean in the sense of a publicly available unstable.gitlab.com where we warn users that everything will can get deleted at any time without notice? Maybe it is already possible?




We are working on doing incremental rollout of new features on GitLab.com and on having an artificial load on our staging site.

There is a cookie setting you can use to get some features early on GitLab.com but I can't find a link right now.

We also test new features on dev.gitlab.org that runs a nightly build and is used by some of our team members.


> There is a cookie setting you can use to get some features early on GitLab.com but I can't find a link right now.

Andrew from the Infrastructure team at GitLab here: non-team members are welcome to use our canary service, provided they understand that service may at times we downgraded (they can always switch back to production when this happens).

Details of how to toggle the canary environment can be found in our handbook: https://about.gitlab.com/handbook/engineering/#canary-testin...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: