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
Copy file name to clipboardExpand all lines: _posts/2024-05-30-may-release-notes.md
+69-16Lines changed: 69 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,45 +4,100 @@ description: "Release Notes for Codefresh Pipelines and GitOps"
4
4
---
5
5
##Features & enhancements
6
6
7
-
###Pipelines: ABAC for Runtimes
8
7
9
8
10
-
###Pipelines: Custom auto-sync intervals for SSO
9
+
###General: Custom auto-sync intervals for SSO
11
10
12
-
Previously,SSOintegration with different SSO providers allowed automatic user and team synchronization with Codefresh at fixed hourly intervals.
11
+
Previously, integration with different SSO providers allowed automatic user and team synchronization with Codefresh at fixed hourly intervals.
13
12
14
13
With our latest update, you can now customize the auto-sync intervals to better suit your organization’s needs.
15
-
The new options allow you to set the sync frequency in minutes or hours. Alternatively, you can enable auto-sync without defining a specific interval, and Codefresh will automatically perform the sycn every 12 hours.
14
+
The new options allow you to set the sync frequency in minutes or hours. Alternatively, you can enable auto-sync without defining a specific interval, and Codefresh will automatically perform the sync every 12 hours.
15
+
16
+
SCREENSHOT
16
17
17
18
This flexibility ensures more timely updates and improved efficiency in user and team management.
18
19
19
20
For details, see[Syncing teams in IdPs with Codefresh]({{site.baseurl}}/docs/administration/single-sign-on/team-sync/#syncing-teams-in-idps-with-codefresh).
20
21
22
+
###General: New platform IP addresses
21
23
22
-
###Pipelines: More GitHub triggers with Pull Request review events
24
+
We are preparing for an upgrade to our production cluster. While the upgrade is still a couple of months away, here's an early heads up about changes in IP addresses.
25
+
26
+
We've added new platform IP addresses as listed below:
27
+
* 54.86.228.102
28
+
* 54.221.236.3
29
+
* 54.235.42.99
30
+
* 23.21.197.195
31
+
* 34.238.37.0
32
+
* 107.22.212.247
33
+
34
+
Please make sure to add them at the earliest to your allowed list. You can also find these IPs listed in Codefresh docs.
23
35
36
+
For details, see[Codefresh IP addresses]({{site.baseurl}}/docs/administration/platform-ip-addresses/).
24
37
25
-
We have expanded the list of supported triggers for GitHub to include detailed Pull Request review events.
38
+
###Pipelines: More GitHub triggers with Pull Request review events
39
+
40
+
We have expanded the list of supported triggers for GitHub to include Pull Request review events.
26
41
These additional triggers enhance the functionality of your CI pipelines in Codefresh.
caption=""New Pull Request review triggers for GitHub"
55
+
max-width="50%"
56
+
%}
57
+
33
58
For details, see[GitHub trigger events]({{site.baseurl}}/docs/docs/pipelines/triggers/git-triggers/#github-trigger-events).
34
59
60
+
###GitOps: Rollout enhancements
61
+
62
+
#####Templated arguments in AnalysisTemplates
63
+
Codefresh now supports templated arguments declared in AnalysisTemplates for metric configurations in AnalysisRuns.
64
+
65
+
#####Rollout Player
66
+
To make Rollouts easier to manage, we added the Abort and Retry buttons to the Rollout Player. These options were previously available for the Rollout resource in the Current State tab.
67
+
68
+
For details, see[Manage rollouts for Argo CD application deployments]({{site.baseurl}}/docs/deployments/gitops/manage-application/#manage-rollouts-for-argo-cd-application-deployments).
69
+
70
+
35
71
36
72
37
73
###Usability enhancements
38
74
39
-
GitOps: Shared Configuration Repo in Ogranizaion Information
75
+
#####Global Search & Navigation
76
+
77
+
#####GitOps: Shared Configuration Repo in Organization Information
78
+
As a usability enhancement, we have made it easier to locate the Shared Configuration Repository used by GitOps Runtimes.
79
+
80
+
You can now find the link to your Shared Configuration Repository directly in the Organization Information page.