My team (7 devs) has a shared development environment on a remote server. A Jenkins pipeline will watch the development branch in Github for changes. When a change is made, it will run a build, unit tests, and publish the changes to the development server as long as there are no failures.
When we are ready to move changes to production, we have to sift through commits to cherry-pick features / functionality that we want to move into production. Being that some releases could be months of work, this process can be fairly tedious and prone to human error.
Currently, there is no option for nightly builds or local development environments. Possible solutions we are thinking of are: More frequent releases, feature flags, or adding rollback functionality to our check-ins.
If you have a similar situation, what changes can be made to improve our release cycle?