-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New strategy StrategyForceLatestVersions #271
Conversation
This property acts similar to the default strategy, but will throw if we try to import a version that is not the latest one. Signed-off-by: Stefan Genov <stefan.genov@ing.com>
Signed-off-by: Stefan Genov <stefan.genov@ing.com>
Signed-off-by: Stefan Genov <stefan.genov@ing.com>
Signed-off-by: Stefan Genov <stefan.genov@ing.com>
Will be needed for the new strategy Signed-off-by: Stefan Genov <stefan.genov@ing.com>
Will now force you to upload the same or newer version of an artifact, or the build will fail Signed-off-by: Stefan Genov <stefan.genov@ing.com>
Signed-off-by: Stefan Genov <stefan.genov@ing.com>
Signed-off-by: Stefan Genov <stefan.genov@ing.com>
This should be refactored to be a switch statement probably or better yet have a map of strategies and allow the user to set the one they want to use. But I fear I will break backwards compatibility if I do that. Signed-off-by: Stefan Genov <stefan.genov@ing.com>
e8c6a50
to
fab82f6
Compare
CHANGELOG.md
Outdated
@@ -1,3 +1,7 @@ | |||
### Enhancements | |||
|
|||
* [vro] Added new strategy StrategyForceLatestVersions that will force you to upload a newer or same version of artifacts, otherwise the build will fail. New property has been introduced `-Dvro.forceImportLatestVersions={{BOOLEAN}}` that is set by default to true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the release.md it says the strategy is by default to false: "It is by default set to false
." I think it looks as if false is the actual value but could you double check and update the changelog?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh... good catch 😆 should be by default to false
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, that would be great as it is also backwards compatible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that was the main philosophy 😮💨 even tho I think some improvements to the way strategies work are needed if we are to add more
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm if you have specific idea for that maybe we can try to implement and release together with Anton's typescript update as major version
The StrategyForceLatestVersions will now no longer upload the same version of the artifact if it's not a -SNAPSHOT Signed-off-by: Stefan Genov <stefan.genov@broadcom.com>
Signed-off-by: Stefan Genov <stefan.genov@broadcom.com>
Signed-off-by: Stefan Genov <stefan.genov@broadcom.com>
Signed-off-by: Stefan Genov <stefan.genov@broadcom.com>
It was incorrectly stating that the default forceImportLatestVersions is set to true, it is false for backwards compatability Signed-off-by: Stefan Genov <stefan.genov@broadcom.com>
Signed-off-by: Stefan Genov <stefan.genov@broadcom.com>
Signed-off-by: Stefan Genov <stefan.genov@broadcom.com>
Signed-off-by: Stefan Genov <stefan.genov@broadcom.com>
That check makes no sense Signed-off-by: Stefan Genov <stefan.genov@broadcom.com>
Signed-off-by: Alexander Kantchev <akantchev@vmware.com>
Signed-off-by: Alexander Kantchev <akantchev@vmware.com>
Signed-off-by: Alexander Kantchev <akantchev@vmware.com>
…stVersions, updated unit tests, added support for the package import flag in the installer Signed-off-by: Alexander Kantchev <akantchev@vmware.com>
Signed-off-by: Alexander Kantchev <akantchev@vmware.com>
Signed-off-by: Alexander Kantchev <akantchev@vmware.com>
Signed-off-by: Alexander Kantchev <akantchev@vmware.com>
Signed-off-by: Alexander Kantchev <akantchev@vmware.com>
would it be possible to just exclude the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we agreed, we can disable this strategy's default behavior. We are going to introduce new version 3 where this strategy will be enabled by default.
Description
This strategy will force you to upload the same or newer version of a package, otherwise it will fail the build, allowing us for
better CI/CD pipelines, where we can ensure that the latest versions are always used on the server.
Checklist
Fixed #XXX -
orClosed #XXX -
prefix to auto-close the issueTesting
Here are the outputs:
Release Notes
This strategy will force you to upload the same or newer version of a package, otherwise it will fail the build, allowing us for
better CI/CD pipelines, where we can ensure that the latest versions are always used on the server.
The new strategy can be triggered by passing
-Dvro.forceImportLatestVersions=true
. It is by default set totrue
.Example usage: