search

dmitryserbin / azdev-release-orchestrator

Azure DevOps extension to manage and orchestrate release pipelines
MIT License
23 stars 12 forks source link

Error after build 2.0.1846: Cannot read property 'trim' of undefined #86

Closed zhouwangzw closed 1 year ago

zhouwangzw commented 1 year ago

Starting from 10/31/2022 I got the following error in our release when calling Release Orchestrator with version 2.0.1846. [error]Cannot read property 'trim' of undefined

The same release worked the day before where the build version was 2.0.1663.

Is it a bug or do we need to update some configuration in the release?

Thanks, Zhou

2022-10-31T13:48:54.3870663Z ##[section]Starting: Release Orchestrator 2022-10-31T13:48:54.4047329Z ============================================================================== 2022-10-31T13:48:54.4047726Z Task : Release Orchestrator 2022-10-31T13:48:54.4048048Z Description : Manage and orchestrate Azure DevOps release pipelines 2022-10-31T13:48:54.4048320Z Version : 2.0.1846 2022-10-31T13:48:54.4048521Z Author : Dmitry Serbin 2022-10-31T13:48:54.4049005Z Help : For aditional information and support please refer to https://github.com/dmitryserbin/azdev-release-orchestrator project repository 2022-10-31T13:48:54.4049521Z ============================================================================== 2022-10-31T13:48:55.0261713Z ##[error]Cannot read property 'trim' of undefined 2022-10-31T13:48:55.0419919Z ##[section]Finishing: Release Orchestrator

zhouwangzw commented 1 year ago

It seems be caused by parameters which has an empty value.

dmitryserbin commented 1 year ago

Thanks for reporting this.

It looks like a bug to me. Please let me know the parameter or better run it in debug mode and share logs if you can.

dmitryserbin commented 1 year ago

I think I found it

dmitryserbin commented 1 year ago

Released in 3.1.1873

zhouwangzw commented 1 year ago

Thanks for the quick fix @dmitryserbin. Is this fix also available for 2.x versions? It seems that 3.x is not compatible with 2.x, and I am using 2.x in Azure DevOps.

dmitryserbin commented 1 year ago

Yea, V2 supports empty parameter value now. V3 doesn't by Azure DevOps design, so it will validate and throw error