Release Notes
The maintenance period for version v4.2.x is from 15 Aug, 2025 to 15 Aug, 2026.
TOC
Compatibility and support matrixv4.2.4New and Optimized FeaturesFixed IssuesKnown Issuesv4.2.3New and Optimized FeaturesFixed IssuesKnown Issuesv4.2.2New and Optimized FeaturesFixed IssuesKnown Issuesv4.2.1New and Optimized FeaturesFixed IssuesKnown Issuesv4.2.0New and Optimized FeaturesBreaking ChangesFixed IssuesProduct IssuesCommunity IssuesKnown IssuesCompatibility and support matrix
The following table shows the compatibility and support matrix between the Alauda DevOps Pipelines operator and ACP versions.
v4.2.4
New and Optimized Features
With this update, some vulnerabilities and security issues have been fixed, ensuring the stability and security of the system.
Fixed Issues
No issues in this release.
Known Issues
No issues in this release.
v4.2.3
New and Optimized Features
With this update, some vulnerabilities and security issues have been fixed, ensuring the stability and security of the system.
Fixed Issues
- Before this update, in MicroOS environments with strict SELinux enforcement, Tekton tasks that depend on Java-based tools (such as Maven and SonarQube) failed to start with the error “Error occurred during initialization of VM - Failed to mark memory page as executable”. With this update, the issue is resolved, and Java-based Tekton tasks now run normally in MicroOS environments.
Known Issues
No issues in this release.
v4.2.2
New and Optimized Features
With this update, some vulnerabilities and security issues have been fixed, ensuring the stability and security of the system.
Fixed Issues
No issues in this release.
Known Issues
No issues in this release.
v4.2.1
New and Optimized Features
With this update, some vulnerabilities and security issues have been fixed, ensuring the stability and security of the system.
Fixed Issues
- Before this update, Pipeline runs with resolver Tasks would intermittently fail when webhook validation requests to tekton-pipelines-webhook service timed out during Task retrieval, resulting in pipeline failure without automatic retry. With this update, the system now properly handles retryable errors during resolver Task validation and implements retry logic to ensure reliable pipeline execution despite temporary network connectivity issues.
- Before this update, when users configured the tekton-hub-api-ssh-crds Secret for Tekton Hub to clone private repositories using SSH keys, the configuration was not properly applied and code repositories could not be cloned successfully even after restarting the pods. With this update, the tekton-hub-api-ssh-crds Secret configuration is correctly processed and applied, allowing Tekton Hub to successfully clone code from private repositories using SSH authentication.
Known Issues
No issues in this release.
v4.2.0
With this update, Alauda DevOps Pipelines v4.2 is available on Alauda Container Platform v4.0 and later versions.
New and Optimized Features
Task and Pipeline Management
- Added
Tasklifecycle management capabilities in theTaskview, facilitating centralized control over the full lifecycle ofTasks. - Expanded
Tasktype support with newPython TaskandPytest Task. - Provided a generic
Python Pipelinetemplate to simplify the creation process of Python-relatedPipelines. - Added cache mounting capability to the
run-scriptTask, supporting cache storage configuration viaWorkspace. - Improved UI interaction experience: When creating
TasksorPipelinesvia the UI, there is no need to explicitly specify theNamespacein the YAML; the system will automatically handle namespace configuration.
Pipeline
Tekton Pipelinesnow supports the use of parameter substitution syntax (e.g.,$(params.strategy)) in theonErrorfield, enabling users to dynamically define error-handling strategies throughPipelineparameters, execution context, orTaskresults.- With this update, the
Gitresolver included in the remote resolution feature now uses the nativegitbinary instead of the pure Gogo-gitlibrary. This change reduces memory consumption and improves clone performance, especially for large repositories. This enhancement uses shallow-clone flags, for example--depth 1, to reduce resource usage. No changes toPipelinemanifests are required. - With this release,
StepActiondefinitions are updated fromalphatostableand are now enabled by default. Theenable-step-actionsflag used in the earlier versions is no longer used and will be removed in a future release. - With this update, the
Pipelinescheduler now correctly evaluates result references in fan-out/fan-in patterns. Previously, suchPipelinescould fail unpredictably when matrixTasksrelied on result refs.
Trigger
- Allowed users to configure custom
securityContextin theEventListenerresource specification to meet personalized security requirements.- Example of using
securityContextinEventListener:
- Example of using
- Added support for including the
imagePullSecretsfield inEventListenerobjects, simplifying the configuration of credentials for pulling images from private repositories.- Example of using
imagePullSecretsinEventListener:
- Example of using
Chains
- With this update, the
Tekton Chainscontroller usesStatefulSetordinals to improve high availability and workload distribution as an alternative to the leader election mechanism.- Example of using
StatefulSetordinals inTekton Chains: -
Note: The
StatefulSetordinals feature is analphafeature and is not enabled by default.
- Example of using
Results
- Added support for configuring custom database credentials in
TektonConfig. - New response field filtering and partial response features in the
Results API: Allows specifying fields to be included in API responses, reducing data transfer volume, optimizing response latency and I/O performance forListoperations, and improving network efficiency. - With this update, the
Tekton Resultswatcher usesStatefulSetordinals to improve high availability and workload distribution as an alternative to the leader election mechanism.- Example of using
StatefulSetordinals inTekton Resultswatcher: -
Note: The
StatefulSetordinals feature is analphafeature and is not enabled by default.
- Example of using
Breaking Changes
- ClusterTask Deprecation: Support for
ClusterTaskobjects has been removed in this release.- Environment Impact:
- New Deployments:
ClusterTaskresources cannot be created in newly deployed environments. - Upgraded Environments: While existing
ClusterTaskresources may still be created in upgraded environments, they will not be executed or used by the system. - Migration Required: Pipelines currently using
ClusterTaskresources must migrate to useTaskresources instead to ensure continued functionality.
- New Deployments:
- Additional Changes:
- The
ClusterTaskfunctionality is no longer available onTekton Hub. - The
tkn clustertaskandtkn task createcommands are no longer available.
- The
- Environment Impact:
Fixed Issues
Product Issues
- Before this update, when you removed ConfigMap keys from the execution parameters in Alauda Pipeline UI, the removed keys were still included in the actual pipeline execution, causing inconsistency between the UI display and the actual pipeline behavior. With this update, the removal of ConfigMap keys in the UI is now correctly applied to the actual pipeline execution, ensuring consistency between the interface and runtime behavior.
Community Issues
The following upstream issues from the Tekton community have been resolved in this release:
Tekton Pipelines
- Before this update, the cluster resolver lacked RBAC permissions to access StepAction resources, causing authorization failures when resolving remote StepActions. With this update, missing RBAC permissions have been added to allow the cluster resolver to get and list StepActions, enabling proper remote resolution functionality.
- Before this update, parameter references in default values and chained references in StepActions were not properly supported, leading to parameter resolution failures. With this update, the parameter resolution logic has been improved to support parameter references in default values and allow chained references in StepActions.
- Before this update, validating enum parameters with special matrix tasks could cause the pipeline controller to panic. With this update, the validation logic has been improved to avoid panic conditions when processing enum parameters in matrix task configurations.
- Before this update, parsing logic for empty results could cause unexpected failures in pipeline execution. With this update, the parsing logic has been improved to handle empty results gracefully, preventing pipeline failures due to empty result processing.
- Before this update, when conditions had lower priority than other execution conditions, leading to unexpected task execution behavior. With this update, when conditions have been moved to higher priority to ensure proper conditional execution logic.
- Before this update, CustomRun resources could cause panic issues in the pipeline controller, leading to controller instability. With this update, the panic issue in the pipeline controller caused by CustomRun has been resolved, improving controller stability.
- Before this update, remote task parameters with default-value substitution were not working correctly, causing parameter resolution failures. With this update, remote task parameter default-value substitution has been fixed to ensure proper parameter handling in remote tasks.
- Before this update, StepAction resources were not configured to use the conversion webhook, causing compatibility issues with different API versions. With this update, StepAction has been configured to use the conversion webhook, ensuring proper API version compatibility.
- Before this update, the hub resolver did not recognize StepAction as a valid resource kind, preventing resolution of remote StepActions from Tekton Hub. With this update, StepAction has been added as a valid kind in the hub resolver, enabling StepAction resolution from Tekton Hub.
- Before this update, fan-out matrix tasks could fail due to result reference issues, causing pipeline execution failures. With this update, the result reference handling has been improved to avoid fan-out matrix task failures due to result reference problems.
- Before this update, subPath directory creation errors could cause immediate PipelineRun failures without allowing time for recovery. With this update, subPath directory creation errors are handled gracefully with retry mechanisms, allowing Alauda Container Platform time to resolve directory creation issues automatically.
Known Issues
No issues in this release.