Closed ninjaniels closed 9 months ago
Hi,
I don't really understand why this is going wrong on your end. We have been using this for years, and no issue :-/.
Here's a build from today: Setting: Result artifacts:
Though - is see yyyyww
, can you change that to yyyyWW
?
Happy New Year to you too!
You are correct; yyyyWW results in 202401. Thanks!
Describe the bug We use the template ?.?.[yyyyWW]. when assigning version number on our apps, as describes in the ALOps documentation. This is giving us a problem because we get a single digit week number 1 instead of expected 01. The version number on our new builds ..20241. are evaluated as lower than last year's ..202352.*. Is it possible to always get double digits week numbers when using the template [yyyyWW]?
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
OutputLog.txt
Expected behavior We were hoping that the version number would be evaluated as ..202401. and not ..20241..
Screenshots App upgrades fails because the version number is evaluated as lower than previous ..202352.*.
Thanks, and happy new year :)