Known issues
You can find the known issues that are identified in any version of HCL DevOps Velocity (Velocity).
Known issues in Velocity
| S. No. | Applicable version | Description |
|---|---|---|
| 1 | 5.3.0 |
When pod multiplexing is enabled, multiple integrations can run in the same pod. Pod multiplexing performs a collective execution of all grouped integrations, which results in plugin logs not being segregated across different integrations. Currently, there is no workaround for this problem. A fix for this log segregation issue is planned for future releases. |
| 2 | 5.3.0 |
When multiple integrations share the same plugin type and version and run in multiplexed mode, you cannot configure different sync intervals for individual integrations. To work around this issue, you perform the following steps:
|
| 3 | 5.2.6 | If you create a pull request synchronization
before the corresponding work item, the AppScan 360 integration
cannot link them retrospectively. Consequently, Velocity fails to
associate the Pull Request ID, Work Item ID, and Commit SHA. To work around this problem, you must synchronize the work item before triggering the pull request synchronization. |
| 4 | 5.2.5 | The user interface is enhanced, which might result in temporary
visual inconsistencies across some screens. Currently, there is no work around for this problem. The user interface enhancement is planned for future releases. |
| 5 | 5.2.5 | The Jenkins data is not available in the Deployment by
Environment Name chart in Analytics
Dashboards. Currently, there is no work around for this problem. This issue will be addressed in upcoming releases. |
| 6 | 5.2.3 | Auto promotion of DevOps Deploy applications without gates is not
working in the Pipeline. Currently, there is no work around for this problem. This issue will be addressed in upcoming releases. |