According to the company, the main benefit of this new CircleCI releases feature is that it can give developers greater confidence in their releases and reduce mean-time-to-recovery for issues. 

Key capabilities that will come with CircleCI releases include the ability to connect CI/CD with customer experiences, automated rollbacks, real-time service validation, and performance degradation prevention.

The releases dashboard shows a timeline of releases for all components (with details on each), a list of release environments, and a list of components and their associated projects. 

“If you look at every other deploy and release vendor on the market, they’re built to service centralized release and operations teams who want tighter control over deploys,” said Rob Zuber, CTO of CircleCI. “But this doesn’t reflect the reality of elite software teams who depend on developers to drive and deliver fast innovation. Our approach to CircleCI releases provides a developer-centric workflow that enables them to ship faster and monitor new features in production coupled with the safety net of quickly rolling back releases if something goes wrong.”

This feature is now available for all CircleCI customers at no additional cost. It currently supports Kubernetes, Amazon SageMaker, and Argo Rollouts. 

The company also plans to add support for Blue-Green deployments later this year.

The post CircleCI enables automated rollbacks in latest offering: CircleCI releases appeared first on SD Times.

With this new model, JetBrains has noticed a few issues that it wanted to address. To start, some questions that JetBrains’ users have are what exactly a version number represents, what the tools provide, how they impact a developer’s work, and their availability to the developer.

JetBrains said that given its IDEs share common functionality through the IntelliJ platform, many customers have questions regarding what feature or bug fix from one product is included in another. Customers should clearly see when a common platform functionality or fix will be available in the individual products. The other problem, according to JetBrains, is that its management of versioning given the amount of product releases it has per year might needs to be increased.

(Related: The results of JetBrains’ database survey)

JetBrains is moving to a single versioning scheme for all its products under the JetBrains Toolbox—specifically, all its IDEs as well as its .NET tools. JetBrains is also introducing a new versioning scheme that will follow the “YYYY.R” format where YYYY represents the year and R the release within that year.

Because of these changes, all JetBrains Toolbox products currently available in early access will be released as version 2016.1.

This change aligns the company’s releases, meaning that all products in the JetBrains Toolbox will have the same number of releases throughout the year and will be released within a certain timeframe from each other.

For developers using JetBrains, the following benefits can be found from these proposed changes:

• Frequent product updates
• Yearly based versioning
• Aligned versioning
• Availability

Internally, JetBrains said that it is easier if all of its tools follow a single versioning scheme. The complete build numbers for each product are aligned with the branches and the actual build number. JetBrains said that the intention is not to “compromise on quality, and we will not move from version-driven development to deadline-driven-development,” according to the company.

The post JetBrains Toolbox introduces new versioning and release changes appeared first on SD Times.