Release Management Environment

Question

1C

Good afternoon

Are there typical release management environments for developing 1C solutions? In other words, what do 1C developers usually use to manage releases?

Thank you in advance for your attention

Answer 1

Who do you understand by 1C developers? Developers who work in Moscow at the 1C company under the leadership of Sergey Nuravlev (a large zoo of c, c++, java programmers; web programmers; android and iOS programmers)? PHP developers (customizers) who work with Bitrix sites (more likely, since you posted the question in the Bitrix hub)? Or programmers in the built-in language of the 1C-Enterprise platform?
Regarding the former, only what they themselves say is known: for example , here they say that they operate with 5 planning horizons and the release of new releases is subject to this ideology. Specifically, it is not known about software products, but I suspect that they use their own developments.
It’s hard to say something about Bitrix customizers… Do they have releases for management? I always thought that they have work to hand over to the customer (data exchange with external systems + unique design), and then the usual service.
Development teams on the 1C platform usually use configuration storage servers for versioning and obtaining release versions, as well as the “Automated configuration check” configuration to check their work for errors and compliance with generally accepted and corporate standards. In one of the projects where I participated, Itilium was used, and in the other, a self-written configuration. There were more exotic cases in practice ...
PS Do not focus on others. See what you need specifically and find the right tool for your unique needs.