forked from yunlzheng/rancher-plugin
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Start First Always Fales #22
Comments
is there a way to use |
Currently no, but if you set a port it will be set to false. Is there a reason why you would want it set to false? |
We have a stack which requires to be stopped before start otherwise service discovery is having trouble resolving IP. Anyways I submitted a PR for the Feature. Link for PR : Adds Start before stop Option |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is no default value and I don't see a way to pass in an option to set startFirst to true.
rancher-plugin/src/main/java/jenkins/plugins/rancher/action/InServiceStrategy.java
Line 11 in 9f1386f
The logic below looks correct, if a port is set it would cause a confect if it's on the same server using start first.
rancher-plugin/src/main/java/jenkins/plugins/rancher/RancherBuilder.java
Line 155 in dac5143
The text was updated successfully, but these errors were encountered: