You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
* Update release notes for april 23Added content and screenshots for april 23 features* Update release notes with GitOps featuresAdded app rollback and static ECR integration to RN* Replace CI/CD with PipelinesReplaced instances of CI/CD with Pipelines* Update release-notes.mdFixed xref to app rollback and final content edits before publish* Update release-notes.md* Update release-notes.mdAdded missing curly brace for siteurl
Copy file name to clipboardExpand all lines: _docs/whats-new/release-notes.md
+171-1Lines changed: 171 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,177 @@ group: whats-new
5
5
toc:true
6
6
---
7
7
8
-
Welcome to our unified Release Notes, including Codefresh pipelines and Codefresh GitOps! If you missed online announcements, this is where you can find the new features, enhancements, and bug fixes.
8
+
9
+
Welcome to our unified Release Notes, including Codefresh pipelines and Codefresh GitOps!
10
+
If you missed any of our online announcements, you can find the latest features, enhancements, and bug fixes, here in the cumulative Release Notes!
11
+
12
+
##April 2023
13
+
14
+
###Features & Enhancements
15
+
16
+
####Pipelines: Annotations for builds
17
+
We are happy to introduce two cool features to annotations for pipeline builds! It’s now easier than ever to find the builds you’re looking for, and customize your build views.
18
+
19
+
First, you can configure an annotation as the build's_display_ annotation, from among the available annotations. Why would you do this? When configured, the annotation is displayed for the build in the Builds page, making it easy to see which builds share common properties like target environments.
For details, see[Configure display annotation for builds]({{site.baseurl}}/docs/pipelines/annotations/#configure-annotation-to-display-for-build).
32
+
33
+
Second, as an obvious extension, you can filter builds by annotations. Filter builds by any annotation added for the build, whether it’s a display annotation or any other annotation with the Annotation filter in the Builds page.
34
+
For details, see[Applying filters to build views]({{site.baseurl}}/docs/pipelines/monitoring-pipelines/#applying-filters-on-the-build-view).
Here's an example of builds filtered by`display` annotations.
47
+
48
+
<br>
49
+
50
+
####Pipelines: Project-based RBAC
51
+
52
+
We are excited to announce project-level Attribute-Based Access Control (ABAC) in this month's release. ABAC for projects saves a lot of effort without compromising security, as now you can control access to the project entity and to pipeline entities based on project tags.
53
+
54
+
How can you do this?
55
+
First by creating projects and by assigning tags to projects and then creating rules.
56
+
57
+
* Project access to teams with project-tags
58
+
Decide which teams have access to which projects, and at which level. By adding tags to projects, you can define rules for different teams who can create, update, delete, and view projects. For example, you may decide that the DevOps team has full access to all projects with all tags, but the Users team has view-only access to projects with`Shared` tag.
59
+
Also, read the next feature description,[Pipelines: Auto-create projects for teams](#pipelines-auto-create-projects-for-teams).
60
+
61
+
* Pipeline access to teams with project-tags
62
+
Create rules for pipeline entities by project tags instead of pipeline tags. Define access to pipelines on the basis of the projects that house the pipelines. Instead of tagging each pipeline, you add tags to the project, and define rules that determine the teams who can access the pipelines which share the project tags.
63
+
64
+
Builds now honor the permissions of the pipelines. If you don't have access to the pipeline, you will not have access to its builds.
65
+
This also means fewer email notifications, as these are only sent for builds you have access to.
alt="Example of rules for pipelines with project tags"
73
+
caption="Example of rules for pipelines with project tags "
74
+
max-width="50%"
75
+
%}
76
+
77
+
For details, see[ABAC for entities with tags and rules]({{site.baseurl}}/docs/administration/account-user-management/access-control/#abac-for-entities-with-tags-and-rules).
78
+
79
+
<br>
80
+
81
+
####Pipelines: Auto-create projects for teams
82
+
Simplify access control and setup with`Auto-create projects for teams`. Enabled by default, this global pipeline setting automatically creates projects whenever you create teams in your account.
alt="Auto-create projects for teams in Pipeline settings"
90
+
caption="Auto-create projects for teams in Pipeline settings"
91
+
max-width="50%"
92
+
%}
93
+
94
+
In addition to automatically creating a project for the team, it also automatically creates a Project rule, and a Pipeline rule for the same team, with basic permissions.
95
+
For details, see[Auto-create projects for teams]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#auto-create-projects-for-teams).
96
+
97
+
<br>
98
+
99
+
####Pipelines: Multi-platform builds in Codefresh
100
+
Build and push Docker images, including multi-platform images in Codefresh with BuildX.
101
+
102
+
We have extended the capabilities of our`build` step with the new`buildx` field. Leverage Docker’s support for multi-architecture/multi-platform support right here in Codefresh. Build an image once and reuse it on multiple architectures/platforms.
103
+
We also support custom`buildx` configurations with QEMU and Builder, giving you all the options you may need.
104
+
105
+
For details, see[Build step field descriptions]({{site.baseurl}}/docs/pipelines/steps/build/#fields).
106
+
107
+
<br>
108
+
109
+
####Pipelines: (On-premises) Custom root CA for services
110
+
On-premises installations can now configure custom Root CA for volumes and containers.
111
+
Reference the K8s secret containing the root CA in`config.yaml`. Define the volume or volumes with the K8s secret objects, and then the volume mounts for the container.
112
+
113
+
For details, see[Configure custom Root CA for volumes and containers]({{site.baseurl}}/docs/installation/codefresh-on-prem/#configure-custom-root-ca-for-volumes-and-containers).
114
+
115
+
<br>
116
+
117
+
####GitOps: Rollback GitOps applications
118
+
We now have the Rollback feature for GitOps applications! With just a click of a button, you can rollback any new or active version of an application directly from the GitOps Apps dashboard in Codefresh.
119
+
120
+
Like Argo CD, Codefresh allows you to rollback to any of the ten previous deployment versions.
For details, see[Rollback GitOps applications]({{site.baseurl}}/docs/deployments/gitops/manage-application/#rollback-gitops-applications).
133
+
134
+
<br>
135
+
136
+
####GitOps: Static integration option for Amazon ECR
137
+
We extended the integration options for Amazon Elastic Container Registry (ECR) in GitOps to include static integrations with Access keys.
138
+
139
+
You can now set up the integration with Amazon ECR using an access key and secret (static integration). Unlike IAM roles, access keys are long-term credentials, without a default expiration date.