|
| 1 | +--- |
| 2 | +title:"Release Notes: June 2023" |
| 3 | +description:"Release Notes for Codefresh Pipelines and GitOps" |
| 4 | +--- |
| 5 | + |
| 6 | +##Features & enhancements |
| 7 | + |
| 8 | + |
| 9 | +###Global Search & Navigation |
| 10 | +Boost your Codefresh experience with our latest feature, Global Search & Navigation! Be it navigation, actions such as switching accounts, or finding entities such as projects or pipelines, Global Search & Navigation lets you get to what and where you need without extra clicks. |
| 11 | + |
| 12 | + {% include |
| 13 | +image.html |
| 14 | +lightbox="true" |
| 15 | +file="/images/whats-new/june23/rel-notes-june23-command-bar.png" |
| 16 | +url="/images/whats-new/june23/rel-notes-june23-command-bar.png" |
| 17 | +alt="Global Search & Navigation in Codefresh" |
| 18 | +caption="Global Search & Navigation in Codefresh" |
| 19 | +max-width="60%" |
| 20 | +%} |
| 21 | + |
| 22 | +**Search & find** |
| 23 | +With Global Search & Navigation, you can easily monitor and find resources in your projects and pipelines, with frequently used entities organized into categories for quick search. Easily find a specific project, or pipeline, or browse them all. |
| 24 | +We’ll be adding applications to our entity list, so stay tuned for the announcement. |
| 25 | + |
| 26 | +In addition, Global Search & Navigation pulls up links to relevant information from our documentation that may be useful within your current context, making it even easier to find what you need. |
| 27 | + |
| 28 | +**Switch accounts** |
| 29 | +Global Search & Navigation allows you to switch accounts without needing to navigate to your avatar drop-down menu in the toolbar. Simply search for the account, select the Switch Account action, and then choose the account you wish to switch to. |
| 30 | + |
| 31 | +**Keyboard shortcuts** |
| 32 | +We have also added keyboard shortcuts to save time and get things done even faster. You can quickly bring up Global Search & Navigation, and get to the entities you need in Projects and Pipelines. |
| 33 | + |
| 34 | + |
| 35 | +For details, see[Global Search & Navigation]({{site.baseurl}}/docs/getting-started/command-bar/). |
| 36 | + |
| 37 | + |
| 38 | +###Gerrit as Git provider for Pipelines and GitOps |
| 39 | +We are excited to announce the integration of Gerrit, the open-source web-based code review tool for Git repositories, with Codefresh. |
| 40 | + |
| 41 | +**Gerrit and Codefresh Pipelines** |
| 42 | +By integrating Gerrit as a Git provider for Codefresh Pipelines, you can leverage its capabilities to trigger builds and tests automatically whenever a new change is pushed to Git repositories hosted in Gerrit. The integration allows you to closely monitor the status of builds and tests within the Gerrit environment itself, providing you with a comprehensive view of your development process. |
| 43 | +With Codefresh’s`CF_PULL_REQUEST` group of environment variables, you can achieve similar functionality to Gerrit’s`Changes` directly within Codefresh. |
| 44 | + |
| 45 | +For details, see[Pipeline integrations - Git providers]({{site.baseurl}}/docs/integrations/git-providers/#gerrit). |
| 46 | + |
| 47 | +**Gerrit and Codefresh GitOps** |
| 48 | +By configuring Gerrit as the primary Git provider for your Hosted GitOps Runtime, you can integrate Gerrit information into your third-party CI tools or platforms for image enrichment and reporting in Codefresh. |
| 49 | +If you are interested in using Gerrit for Hybrid GitOps Runtimes, please contact us. |
| 50 | + |
| 51 | +For details, see[GitOps Gerrit Git provider integration]({{site.baseurl}}/docs/gitops-integrations/gerrit-integration/). |
| 52 | + |
| 53 | +###Pipelines: Pipeline Dashboard enhancements |
| 54 | +Review the latest enhancements in the Pipelines Dashboard. |
| 55 | + |
| 56 | + {% include |
| 57 | +image.html |
| 58 | +lightbox="true" |
| 59 | +file="/images/whats-new/june23/rel-notes-june23-pipeline-dashboard-updates.png" |
| 60 | +url="/images/whats-new/june23/rel-notes-june23-pipeline-dashboard-updates.png" |
| 61 | +alt="Favorites filter and Last Update in Pipelines Dashboard" |
| 62 | +caption="Favorites filter and Last Update in Pipelines Dashboard" |
| 63 | +max-width="60%" |
| 64 | +%} |
| 65 | + |
| 66 | +**Filter by favorite pipelines** |
| 67 | +The Pipelines Dashboard now has a Favorites filter. If you starred any projects or pipelines as favorites, you can easily view your favorite pipelines, both by projects or individual pipelines. |
| 68 | + |
| 69 | +**Recent update indication** |
| 70 | +The Last Update timestamp on the top right of the Pipelines Dashboard, refreshes automatically to show you the exact time the data was retrieved. |
| 71 | + |
| 72 | +**Full path display for pipelines in filter** |
| 73 | +Previously, in the Pipelines filter, it was challenging to identify the correct pipeline, when multiple pipelines shared the same name across different projects. |
| 74 | +Now, when you mouse over a pipeline name in the list, the tooltip displays the full path, including the name of the project to which the pipeline belongs, followed by the name of the pipeline. With this update, you can easily identify and select the correct pipeline in the Pipelines filter, even when multiple pipelines share the same name across different projects. |
| 75 | + |
| 76 | +For details, see[Pipelines Dashboard]({{site.baseurl}}/docs/dashboards/home-dashboard/#pipelines-dashboard). |
| 77 | + |
| 78 | +###Pipelines: New icons for pipeline build statuses |
| 79 | +Pipeline builds have new status icons. With distinct icons for each status, you can easily differentiate between builds, bringing clarity and saving time. Previously, both terminated and failed builds had the same icon for example, causing confusion. |
| 80 | + |
| 81 | +Here are the icons and the build statuses they represent: |
| 82 | +***Running**: {::nomarkdown}<imgsrc="../../../../../images/whats-new/june23/pipeline-build-running.png"display=inline-block/> {:/} |
| 83 | +***Completed**: {::nomarkdown}<imgsrc="../../../../../images/whats-new/june23/pipeline-build-successful.png"display=inline-block/> {:/} |
| 84 | +***Delayed**: {::nomarkdown}<imgsrc="../../../../../images/whats-new/june23/pipeline-build-delayed.png"display=inline-block/> {:/} |
| 85 | +***Pending approval**: {::nomarkdown}<imgsrc="../../../../../images/whats-new/june23/pipeline-build-pending-approval.png"display=inline-block/> {:/} |
| 86 | +***Denied approval**: {::nomarkdown}<imgsrc="../../../../../images/whats-new/june23/pipeline-build-denied.png"display=inline-block/> {:/} |
| 87 | +***Terminating**: {::nomarkdown}<imgsrc="../../../../../images/whats-new/june23/pipeline-build-terminating.png"display=inline-block/> {:/} |
| 88 | +***Terminated**: {::nomarkdown}<imgsrc="../../../../../images/whats-new/june23/pipeline-build-terminated.png"display=inline-block/> {:/} |
| 89 | +***Failed**: {::nomarkdown}<imgsrc="../../../../../images/whats-new/june23/pipeline-build-failed-error.png"display=inline-block/> {:/} |
| 90 | + |
| 91 | +For details, see[Viewing status for pipeline builds]({{site.baseurl}}/docs/pipelines/monitoring-pipelines/#viewing-status-for-pipeline-builds). |
| 92 | + |
| 93 | +###GitOps: Helm-based Hybrid Runtimes |
| 94 | +As part of our ongoing commitment to improving efficiency and simplifying installations, we have transitioned from the previous CLI-based installation method to native Kubernetes installation using Helm charts. This change simplifies the installation process and aligns with industry-standard practices for Kubernetes deployments. |
| 95 | + |
| 96 | +**Helm installation for Hybrid GitOps** |
| 97 | + Moving forward, we are deprecating the CLI-based installation method for Hybrid GitOps Runtimes. Helm provides better control and ensures compatibility, enabling you to seamlessly manage GitOps Runtimes deployments across various clusters. |
| 98 | + For details, see[Hybrid GitOps Runtime installation]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/). |
| 99 | + |
| 100 | +<!--- |
| 101 | +* On-Premises version of Codefresh GitOps Runtime |
| 102 | + We also introduced an on-premises version of the GitOps Runtime, allowing you to deploy and manage your Codefresh infrastructure within your private network. |
| 103 | + The on-premises version gives you greater control over your environment, ensuring data security and compliance while leveraging the powerful features and integrations of Codefresh GitOps and Argo CD. |
| 104 | + For details, see [On-premises GitOps Runtime installation]({{site.baseurl}}/docs/installation/gitops/on-prem-gitops-runtime-install/). |
| 105 | +--> |
| 106 | + |
| 107 | +##Bug fixes |
| 108 | +**General** |
| 109 | +* Unable to add users to Codefresh via team sync for Okta. |
| 110 | + |
| 111 | + |
| 112 | +**Pipelines** |
| 113 | +* Pipeline builds terminate with error message:`Pipeline could not be executed because retry attempts limit has been exceeded...`. |
| 114 | +* Discrepancy in list of builds returned when running`GET {{baseUrl/workflow?pipeline=[pipeline-id]}}` query. |
| 115 | +* Shallow clone for a specific revision with`depth` argument results in error:`pathspec 'test' did not match any file(s) known to git`. |
| 116 | +* Composition stops randomly with error:`Could not get status for container <container-name>`. |
| 117 | +* Unable to define CRON triggers for pipelines. |
| 118 | +* Cross-account ECR pull in`freestyle` step fails with`(HTTP code 500) server error...`. |
| 119 | +* In the Builds page, steps are grayed out, and the Output tab for a step displays`loading` instead of the step logs. |
| 120 | +* Creating a Git trigger for a repo name containing spaces fails with error:`Failed to create trigger...fails to match the required pattern...`. |
| 121 | +* Unable to set`requiredAvailableStorage` programmatically for Hybrid Pipeline Runtimes. |
| 122 | +* 404 errors on clicking documentation links in Build > Triggers. |
| 123 | + |
| 124 | +**GitOps** |
| 125 | +* Unable to delete Argo CD application from Git Source. |
| 126 | +* Same application shows different statuses in the**Home > GitOps Dashboard** and in the**GitOps Apps** dashboard. |
| 127 | +* Images not displayed in Images dashboard for GitLab Git provider (Denis) |
| 128 | +* (On premises) Rollouts Reporter for managed cluster uses SaaS instead of on-premises URL. |
| 129 | + |
| 130 | + |
| 131 | + |
| 132 | + |