Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

February release notes#929

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
NimRegev merged 10 commits intomasterfromfebruary-release-notes
Feb 29, 2024
Merged
Show file tree
Hide file tree
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
87 changes: 87 additions & 0 deletions_posts/2024-02-28-feb-release-notes.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
---
title: "Release Notes: February 2024"
description: "Release Notes for Codefresh Pipelines and GitOps"
---

## Features & enhancements

### Pipelines: Blobless Git clone

Here's an enhancement which contributes to workflow optimization - a new field in our `git_clone` step: the `exclude_blob` field.
Filter out blob files from the Git repository and further streamline your development process. Fewer unnecessary files to clone and faster cloning times!

For blobless cloning, simply set `exclude_blob` to `true`. To always include blob files, you can retain the default value of `false`.

For details, see [Fields in git-clone step]({{site.baseurl}}/docs/pipelines/steps/git-clone/#fields).

### GitOps: Argo CD application enhancements

We introduced a couple of usability enhancements for Argo CD applications in Codefresh.

##### Deployment record for Current Release
To more accurately represent the live deployment status of the selected application in the Timeline tab, we now clearly differentiate between current and historical deployments.

The Current Release is prominently displayed as a dedicated deployment record at the top of the Timelines tab, tagged as the Current Version. It is followed by the list of Previous Releases.

{% include
image.html
lightbox="true"
file="/images/whats-new/feb24/rel-notes-feb24-current-release-record.png"
url="/images/whats-new/feb24/rel-notes-feb24-current-release-record.png"
alt="Current Release deployment record in Timeline tab"
caption="Current Release deployment record in Timeline tab"
max-width="70%"
%}

* To prevent confusion with duplicate statuses, the application's health and sync statuses are now exclusively displayed and tracked within the Application Header.

* To validate that the current release as the live state, the release revision in the deployment record mirrors the sync revision displayed in Last Sync Result.

For details, see [Monitoring deployments for selected Argo CD application]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard/#monitoring-deployments-for-selected-argo-cd-application).

##### Quick links
The Configuration tab displays handy links to the application's GitOps Runtime, Git Source, and YAML manifest in the Git repo.

{% include
image.html
lightbox="true"
file="/images/whats-new/feb24/rel-notes-feb24-apps-quick-links.png"
url="/images/whats-new/feb24/rel-notes-feb24-apps-quick-links.png"
alt="Quick links for application in Configuration tab"
caption="Quick links for application in Configuration tab"
max-width="70%"
%}


### GitOps: Deprecation of GitOps CLI for Runtime installation

As we have transitioned to Helm-based Runtimes for GitOps, we have permanently deprecated the CLI-based installation for GitOps Runtimes.


## Bug fixes

##### General
* ABAC (Attribute-based access control) rules in GO not correctly resolved when multiple rules are configured for the same user.
<br>

<!-- ##### Pipelines
(On-premises) Unable to deploy Helm charts to Helm boards after upgrade to v2.2.4 -->

##### GitOps
* `Prune skipped` message for Argo CD applications after upgrading to GitOps Runtime v0.4.2.
* Unable to delete clusters in the Codefresh UI.
* Error on enabling Argo CD notifications in Helm chart `values.yaml` for Codefresh GitOps Runtime v0.4.2.
* When adding a Git Source and manually defining the branch, metacharacters are not encoded as HTML in the YAML.
* Renaming an ApplicationSet or GitSource removes all application's resources and then adds them again.
* Empty page on clicking **View Native Workflow** for the selected workflow in the Workflows tab.
* (On-premises) GitOps features not loaded on accessing Account Settings from the Admin Management panel with both GitOps and Pipeline modules.










View file
Open in desktop
Loading
Sorry, something went wrong.Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View file
Open in desktop
Loading
Sorry, something went wrong.Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

[8]ページ先頭

©2009-2025 Movatter.jp