What's your experience with continuous delivery? On every push to the master, the complete current codebase goes to production.
Of course not visible to all the users, but hidden behind feature flags.

@Bitwise Me neither, we currently have a staging system. But I would like to go a step further, the philosophy behind continuous delivery is very intriguing.

You don't have the hassle of releases and you can get immediate feedback from your users and even make a/b-tests very easily. And you have the psychologic effect, that your daily work matters because it goes to prod.

@Bitwise It's indeed very critical to have the possibility to rollback as fast as possible.
We will try it out in our new project, and I'm very excited for it.

My previous employers didn't have automated tests too.
Luckily we have lot's of automated tests, at my current company.

I like staging systems too,but sometimes releasing can be a hassle..

We use it on most projects where I work.

When you submit code to master branch it builds the code and deploys it for you. As projects are getting bigger with different types of components then I'm not sure deploying manually is an option anymore

@Jonnyforgotten Will every user see all the new things your team developed?
Or what is your experience with feature flags?

Yes everyone sees the new changes. We've never really used feature flags (tbh I didn't know they existed until this rant and I looked them up)

I should probably mention our software is in house internal systems only so our use case is probably different to the average dev team

@Jonnyforgotten oh okay, it's in house. How do you lower the risk of breaking things? How are manual tests happening?

@plusgut As part of the build process it runs the unit tests. If the tests fail then the build fails and nothing gets deployed

It's not foolproof but having said that I can't think a deployment has really messed things up. Everything is backed up during deployment so we can roll back (manually).