You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 29, 2018. It is now read-only.
Currently when the CDK is build the resulting zip file is just called cdk.zip. This makes it hard to distinguish between multiple versions. It would be nice if the zip bundle would contain a version identifier, eg cdk-2.2.zip (public/final releases) or cdk-.zip (for daily builds).
The text was updated successfully, but these errors were encountered:
Why not have something unique even for nightly builds? For example it could include the build id, e.g. cdk-2.3-45.zip. That way you could have a clear way of telling one cdk zip from another.
you mean for nightly builds we should have cdk-.zip right?
he he, I think you did the same mistake than me. What I wanted to write is cdk-.zip, but one has to obviously escape the pointy brackets. Date is the first thing which came to my mind, but a unique id works as well I guess.
Currently when the CDK is build the resulting zip file is just called cdk.zip. This makes it hard to distinguish between multiple versions. It would be nice if the zip bundle would contain a version identifier, eg cdk-2.2.zip (public/final releases) or cdk-.zip (for daily builds).
The text was updated successfully, but these errors were encountered: