|
| 1 | +--- |
| 2 | +title:"Release Notes: January 2024" |
| 3 | +description:"Release Notes for Codefresh Pipelines and GitOps" |
| 4 | +--- |
| 5 | + |
| 6 | +##Features & enhancements |
| 7 | + |
| 8 | +###Pipelines: Empty variables |
| 9 | +We are happy to announce a highly-requested feature: the ability to use_empty variables_ in Codefresh pipelines. Now, you can add variables without any values to any entity in Codefresh, whether it's a project, pipeline, or trigger. The enhancement unlocks a myriad of possibilities that were previously unavailable. |
| 10 | + |
| 11 | +{% include |
| 12 | +image.html |
| 13 | +lightbox="true" |
| 14 | +file="/images/whats-new/jan24/rel-notes-jan-24-empty-variables.png" |
| 15 | +url="/images/whats-new/jan24/rel-notes-jan-24-empty-variables.png" |
| 16 | +alt="Empty variables in a Codefresh project" |
| 17 | +caption="Empty variables in a Codefresh project" |
| 18 | + max-width="60%" |
| 19 | +%} |
| 20 | + |
| 21 | + |
| 22 | +Remember that encryption is not supported for empty variables. The priority for variable overrides remains unchanged. |
| 23 | + |
| 24 | +For details, see[User-defined variables in pipelines]({{site.baseurl}}/docs/pipelines/variables/#user-defined-variables). |
| 25 | + |
| 26 | +###Pipelines: Share build run settings |
| 27 | +Our newest enhancement to pipeline builds is designed to increase collaboration and productivity! How? Instead of redefining build settings manually, you can effortlessly share pipeline build settings with colleagues who have access to the same account. |
| 28 | + |
| 29 | +**How does it work?** |
| 30 | +By sharing build settings, you enable colleagues to pre-populate build configurations without the need for redundant manual input. This feature is useful for various scenarios, whether it's for testing automation integration with third-party tools or triggering pipelines in specific situations. |
| 31 | + |
| 32 | +**Customizing build settings** |
| 33 | +You can override any existing setting - simulate a different trigger, select a different branch, modify existing or add new build variables, and even modify the build behavior. |
| 34 | + |
| 35 | +With a click of the**Share build settings** button, Codefresh generates a unique URL. The URL includes modified and new settings as query parameters. Encrypted variables are excluded to ensure data protection. |
| 36 | + |
| 37 | + {% include |
| 38 | +image.html |
| 39 | +lightbox="true" |
| 40 | +file="/images/whats-new/jan24/rel-notes-jan-24-share-run-configuration.png" |
| 41 | +url="/images/whats-new/jan24/rel-notes-jan-24-share-run-configuration.png" |
| 42 | +alt="Share build settings" |
| 43 | +caption="Share build settings" |
| 44 | + max-width="40%" |
| 45 | +%} |
| 46 | + |
| 47 | +For details, see[Share build run settings]({{site.baseurl}}/docs/pipelines/run-pipeline/#share-build-run-settings). |
| 48 | + |
| 49 | +###Pipelines: Restart from failed step |
| 50 | +At Codefresh, we highly value your feedback and are committed to continually enhancing your experience. In response to your feedback, we introduced the ability to configure the default restart behavior for failed steps in a pipeline at the account level. |
| 51 | + |
| 52 | + {% include |
| 53 | +image.html |
| 54 | +lightbox="true" |
| 55 | +file="/images/whats-new/jan24/rel-notes-jan-24-restart-failed-step.png" |
| 56 | +url="/images/whats-new/jan24/rel-notes-jan-24-restart-failed-step.png" |
| 57 | +alt="Restart from failed step in Pipeline Settings" |
| 58 | +caption="Restart from failed step in Pipeline Settings" |
| 59 | + max-width="50%" |
| 60 | +%} |
| 61 | + |
| 62 | +When enabled (the default), the user can restart the pipeline directly from the failed step. Otherwise, users can only restart the pipeline from the beginning. |
| 63 | +By default, individual pipelines are configured to inherit the account setting. |
| 64 | +Note that this does not impact existing pipelines. |
| 65 | + |
| 66 | +Being able to configure the restart behavior for failed steps centrally simplifies management and ensures consistency across pipelines, without the need for individual adjustments. |
| 67 | +Imagine a scenario where you’re onboarding a large team of developers. You can disable failed-step restart for the account, and have the pipelines use the account-level setting, saving valuable time and promoting a consistent experience. |
| 68 | + |
| 69 | +You can always change the behavior at any time based on evolving requirements. And users have the flexibility to override the account-level behavior for individual pipelines based on specific needs. |
| 70 | + |
| 71 | +For details, see[Restarting from failed steps]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#restarting-from-failed-steps). |
| 72 | + |
| 73 | +###Pipelines: Add tags during pipeline creation |
| 74 | +With this update, you can effortlessly add tags when you create a pipeline, further streamlining the pipeline creation process. Add tags as you usually do, and they are instantly available in both the General Settings and the Permissions panel. |
| 75 | + |
| 76 | + {% include |
| 77 | +image.html |
| 78 | +lightbox="true" |
| 79 | +file="/images/whats-new/jan24/rel-notes-jan-24-tags-in-create-pipeline.png" |
| 80 | +url="/images/whats-new/jan24/rel-notes-jan-24-tags-in-create-pipeline.png" |
| 81 | +alt="Add tags when creating pipeline" |
| 82 | +caption="Add tags when creating pipeline" |
| 83 | + max-width="40%" |
| 84 | +%} |
| 85 | + |
| 86 | + |
| 87 | +###Pipelines: Explicit versions for typed steps |
| 88 | +As you're aware, Codefresh is continually enhancing our typed step library in the Marketplace. |
| 89 | + |
| 90 | +When typed steps in pipelines lack a specified version, Codefresh automatically associates them with the latest version of the step. To avoid potential issues with breaking changes in typed steps, we now provide a warning if there are steps in your pipelines without an explicit version number. |
| 91 | + |
| 92 | +{% include |
| 93 | +image.html |
| 94 | +lightbox="true" |
| 95 | +file="/images/whats-new/jan24/rel-notes-jan-24-typed-step-warning.png" |
| 96 | +url="/images/whats-new/jan24/rel-notes-jan-24-typed-step-warning.png" |
| 97 | +alt="Warning for typed steps without version numbers" |
| 98 | +caption="Warning for typed steps without version numbers" |
| 99 | + max-width="60%" |
| 100 | +%} |
| 101 | + |
| 102 | +For details, see[Versioning for typed steps]({{site.baseurl}}/docs/pipelines/steps/#versioning-for-typed-steps). |
| 103 | + |
| 104 | + |
| 105 | + |
| 106 | +###GitOps: Tailored sync timeouts for Argo CD applications |
| 107 | + |
| 108 | +Tailor the timeout thresholds for sync operations for different applications, and receive instant alerts when the sync duration exceeds the threshold defined. |
| 109 | +Instead of waiting indefinitely for syncs to complete and then navigating through the GitOps Apps dashboard, Codefresh provides you with timely warnings to proactively investigate and resolve sync issues. |
| 110 | + |
| 111 | +Just include an annotation in the application's YAML, and either retain the default timeout of 30 minutes (also Argo CD's default for sync operations), or change it as needed. |
| 112 | +Codefresh will display a warning in the**Warnings/Errors** panel for the app when the sync operation exceeds the timeout. |
| 113 | + |
| 114 | + {% include |
| 115 | +image.html |
| 116 | +lightbox="true" |
| 117 | +file="/images/whats-new/jan24/rel-notes-jan-24-sync-timeout.png" |
| 118 | +url="/images/whats-new/jan24/rel-notes-jan-24-sync-timeout.png" |
| 119 | +alt="Sync timeout warning for Argo CD applications" |
| 120 | +caption="Sync timeout warning for Argo CD applications" |
| 121 | + max-width="70%" |
| 122 | +%} |
| 123 | + |
| 124 | +For details, see[Configure sync-timeout for Argo CD applications]({{site.baseurl}}/docs/deployments/gitops/manage-application/#configure-sync-timeout-for-argo-cd-applications). |
| 125 | + |
| 126 | +###GitOps: View/download logs for GitOps Runtime components |
| 127 | +We are glad to announce that you can now view and download logs for individual GitOps Runtime components! |
| 128 | +Previously available for legacy CLI Runtimes, this functionality is now back for Helm GitOps Runtimes, with online viewing in our smart terminal and offline downloads as you need. |
| 129 | + |
| 130 | +As a reminder, here's where you can find the**View logs** option: |
| 131 | + |
| 132 | + {% include |
| 133 | +image.html |
| 134 | +lightbox="true" |
| 135 | +file="/images/whats-new/jan24/rel-notes-jan-24-runtime-component-log.png" |
| 136 | +url="/images/whats-new/jan24/rel-notes-jan-24-runtime-component-log.png" |
| 137 | +alt="View logs for GitOps Runtime components" |
| 138 | +caption="View logs for GitOps Runtime components" |
| 139 | + max-width="70%" |
| 140 | +%} |
| 141 | + |
| 142 | +For details, see[View/download logs for GitOps Runtime components]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#viewdownload-logs-for-runtime-components). |
| 143 | + |
| 144 | +###GitOps: Argo Events upgrade |
| 145 | +We've recently upgraded Argo Events to its latest version, v1.9.0, ensuring you can leverage all enhancements. For detailed information about the changes in this version, please refer to the[Argo documentation](https://github.com/argoproj/argo-events/releases). |
| 146 | + |
| 147 | +Please be aware that this upgrade may introduce a potential breaking change for existing event sources that have defined`githubBaseUrl` without defining`githubUploadURL` which is required. In such cases, event sources will fail to sync, and the Git Source application will return a`..githubUploadURL is required when githubBaseURL is set` error. |
| 148 | + |
| 149 | +To address this, you'll need to edit the event source YAMLs and add`githubUploadURL` where required. |
| 150 | + |
| 151 | + |
| 152 | +##Bug fixes |
| 153 | + |
| 154 | +<br> |
| 155 | + |
| 156 | +**Pipelines** |
| 157 | +* For Bitbucket Cloud,`codefresh-report-image` step fails with errors to get Pull Requests (PRs) and branches. |
| 158 | +* Builds for Gerrit in Codefresh are triggered twice because of webhook data delivery request timeouts or connection issues. |
| 159 | +* Replaced misleading warning message "The security token included in the request is invalid" for successful builds. |
| 160 | + |
| 161 | + |
| 162 | +<br> |
| 163 | + |
| 164 | +**GitOps** |
| 165 | + |
| 166 | +* Codefresh UI unresponsive when clicking Warnings/Errors button in the**GitOps Apps** dashboard. |
| 167 | +*`Failed to create binary image error` from Image reporter for images exceeding 2GB. |
| 168 | +* Audit log missing manual actions executed in Rollouts Player. |
| 169 | +* Delay for new Argo CD applications to appear in Codefresh GitOps Apps dashboard. |
| 170 | +* For GitLab Actions,`codefresh-image-reporter` log displays actual values of encrypted secrets. |
| 171 | +* Codefresh UI not in sync with native Argo CD UI. |
| 172 | + |
| 173 | + |