The Pipeline Parameter Referenced by the Task Does Not Exist
Background
Pipeline parameters can be transferred to each task using the ${parameter name} format. If a parameter associated by using ${parameter name} is not on the pipeline parameter list, a message is displayed, indicating that the parameter is not specified.
Symptom
After you edit a pipeline and click Save, a message indicates that a pipeline parameter referenced by the task does not exist.
Root Cause
- Click the name of the task for which the error is reported. On the task orchestration page, view the task parameter settings.
- Access and view Parameter Configuration page.
The releaseversion parameter referenced by the task parameter is not configured on the pipeline parameter list. As a result, this exception is reported.
Solution
Use either of the following methods to add a referenced parameter (for example, releaseversion) to the pipeline parameter list:
- On the Parameter Configuration page of the pipeline, click Create now to add a parameter.
- Click the name of the failed task. On the task orchestration page, hover over releaseversion, and click Set as Pipeline Parameter to add a parameter.
Troubleshooting FAQs
- The Pipeline Parameter Referenced by the Task Does Not Exist
- Test Suite Was Running
- Failed to Obtain Tenant Information During Code Check Task Execution
- The Pipeline That Does Not Listen to the Push Event Is Triggered When the Code Is Committed
- Scheduled Task of a Pipeline Was Not Triggered
- Run Button Was Unavailable
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore