OurNovember release offers two groundbreaking features in the world of GitOps: Environments and Products

For ourNovember release, we are starting with GitOps, introducing two groundbreaking features: Environments and Products!

Welcome to the first ever GitOps dashboard for Environments! If you are familiar with our wide range of dashboards for Argo CD applications in Codefresh, you are also aware of theunique insights thesedashbpards offer into Argo CD applications and their deployments. These dashboards don't inherently reveal the relationships between different but interconnected Argo CD Applications.

Welcome to the first ever GitOps dashboard for Environments! If you are familiar with our wide range of dashboards for Argo CD applications in Codefresh, you are also aware of the unique insights thesedashboards offer into Argo CD applications and their deployments.

Enter the GitOps Environments dashboard! A game-changer adding a new dimension to your GitOps experience with Argo CD applications.

What these dashboards don't inherently reveal is the relationships between different but interconnected Argo CD Applications.

Enter the GitOps Environments dashboard! A game-changer that changes your GitOps experience with Argo CD applications.

SCREENSHOT

* Contextual visbility: Argo CD applications are within the context of their Environments, providing a comprehensive view of their journey through the software development and deployment lifecycle.

What do you get?

* Contextual visbility: Argo CD applications are displayed within the context of their Environments, providing a comprehensive view of their journey through the software development and deployment lifecycle.

* Version identification: Unified visibility across Environments allows you to track deployed versions effortlessly, ensuring users always access the latest or most appropriate version. You can also discern which services were rolled out in specific versions and view detailed commit information.

* Enhanced insights: Beyond contextual visibility, you can delve into the deployment history of individual applications and take actions such as synchronization and refresh, among others.

**How to start?**

You start by creating Environments. An Environment is a custom resource in Codefresh comprising one or more pairs of clusters and namespaces.

You start by creating Environments. An Environment is a custom resource in Codefresh comprising one or more pairs of clusters and namespaces.Our user-friendly UI simplifies Environment creation, allowing you to define Environments by criteria meaningful to your organization and applications – from development cycles to deployment regions.

Our user-friendly UI simplifies Environment creation, allowing you to define Environments by criteria meaningful to your organization and applications – from development cycles to deployment regions.

Once clusters are defined for an Environment, Codefresh automatically populates them with the applications deployed to those clusters and namespaces, showcasing them in the Environments dashboard.

Once you create an Environment, Codefresh automatically populates them with the applications deployed to clusters and namespaces that are mapped to it, and showcases them in the GitOps Environments dashboard.

**Working with Environments**

Interacting with Environments is straightforward and intuitive:

From this point, interacting with Environments is straightforward and intuitive:

* Reorder Environments effortlessly through drag-and-drop

* Edit settings or delete Environments as needed

**Working with Argo CD Applications in Environments**

Managing Argo CD applications within Environments is just as simple:

* View modes that allow you to decide the extent of information to see

* All the options in the GitOps Apps dashboard to manage individual applications are available here as well through the app's context menu.

* Clicking an application takes you to the deployment timeline tracing all releases for the application, identifying any issues or failures that require attention. From there a link takes you to the full Timeline view in the GitOps Apps dashboard.

* View modes that allow you to decide the extent of information to track

* Deployment timeline tracing all releases for the application, identifying issues or failures that require attention

* Access to the full Timeline view in the GitOps Apps dashboard in parallel

* Options to manage individual applications available through the app's context menu

For details, see ???

GitOps Products is yet another groundbreaking concept in GitOps from Codefresh! It introduces a new dimension to Environments, providing transparency in application promotion and deployment processes.

GitOps Products is yet another groundbreaking concept in GitOps from Codefresh!

A Product represents a cohesive unit of Argo CD applications, enabling you to define and treat sets of applications as a unified entity.

A Product represents a cohesive unit ofArgo CD applications, enabling you to define and treat sets ofapplicationsas a unified entity. You can define exactly which applications are part of a Product.

Products bridge the gap betweenArgo CD applications and Environments. They allow you to group Argo CDapplicationsthat seem different, but are essentially the same application, promoted and deployed to different Environments.

This unified view of multiple applications not only helps track technical aspects of the releases, but more importantly, correlate the view with additional layers of information that artiaffect theM

* Artifacts created, updated, removed Deployments (Kubernetes)

* Changes that caused the deployment, when, and by whom (Git commits and committers)

* Features released in the deployment (Jira)facts, Git commits and Pull Requests, Jira issues and more, all in the same view.

It helps answer technical and questions:

* what

**where are the artifats deployed, which release is impacting production, and which services are being rolled out?

So yu have Git, Jira

**How to start?**

Similar to Environments, you start by creating Products. A Product, also a custom resource in Codefresh, connects one or more Argo CD applications.

Again, our intuitive UI makes it simple to create a Product. You can connect applications using Codefresh's default annotation orbu=y addingcustom annotations to the Product'sdefinitons.

Codefreshalsogives you the flexibility tocreate Products andlaterassign applications directly from the Products dashboard.

Again, our intuitive UI makes it simple to create a Product. You can connect applications usingK8s-native annotations, eitherCodefresh's default annotation or custom annotationsthat you addto the Product'sdefinitions.

You canalso create Products and assign applications to them later directly from the Products dashboard.

Once you create Products and connect applications, Codefreshdoes all the work. Codefresh identifies assigned applications, organizes thembased on theirdeployedEnvironments, andshowcases them in the Products dashboard.

Once you create Products and connect applications, Codefreshcompletes what needs to be done, from identifying applications assigned to Products, organizing themin the Environments they aredeployedto, andshowcasing them in the Products dashboard.

**Working with Products**

After creating Products,you can edit settings, and remove Products.

You can also assign unassigned applications

you can edit settings for existing Products, or remove Products.

You can also assign unassignedArgo CDapplicationsto existing Products.

**Working with Argo CD applications in Products**

It's also easy to workwithArgo CD applicationsin Environments.

Working with Argo CD applications in Products is as intuitive as workingwiththem in Environments. First of all, you have similar functionality asintheEnvironments dashboard to remain in the same view. So you have the release timeline and options to manage individual applications here as well.

???

We are happy to announce a new field for pipeline steps, the`timeout` flag, which enhances control over your pipelines!

The`timeout` flag, when assigned to a step prevents that step from running beyond a specific duration if so required.

We are happy to announce a new field for pipeline steps, the`timeout` flag to further enhance control over your pipelines!

The`timeout` flag, when assigned to a step, prevents that step from running beyond a specific duration if so required.

Add the`timeout` flag with the <duration> and <units> to any of these step types:`git-clone`,`freestyle`,`build`,`push`,`composition`,`pending-approval`.