-
Notifications
You must be signed in to change notification settings - Fork 581
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
Task schedule is not using the version defined in the properties file #5705
Comments
Which versions of which app are registered?
AND then for non-default versions
|
Any update for this case ? I deploy in k8s and meet same problem ? |
@corneil shell
curl app version
|
no response.. so sad.. :( |
Apologies for not following up on this. I'll start taking a peak at it. |
This update allows user to specify version.label=<version.number> Tests were also updated because the original settings assumed that the appregistry was real instance instead of being mocked. Thus the find would always return null. And in this case the tests returned a false positive. Now that the mocks are in place it excercises all the code. Also added explicit test if user does not set the version number. Some of the tests do this, but wanted an explicit test to verify this. resolves spring-cloud#5705
This update allows user to specify version.label=<version.number> Tests were also updated because the original settings assumed that the appregistry was real instance instead of being mocked. Thus the find would always return null. And in this case the tests returned a false positive. Now that the mocks are in place it excercises all the code. Also added explicit test if user does not set the version number. Some of the tests do this, but wanted an explicit test to verify this. resolves spring-cloud#5705
@cppwfs |
Description:
A schedule task is not using the version defined in the properties file. Whereas a launch using the same properties file is well using the app version.
Tested using the scdf shell.
Release versions:
Steps to reproduce:
Schedule a task with a specific version
Describe the cronjob, the container image is not using the version.
The text was updated successfully, but these errors were encountered: