Open inetshell opened 5 years ago
find any solution?
Having the same problem 😕 Anyone has the solution?
My solution was to stop using sidekick containers and replacing them with scheduling rules, host labels and host volumes.
On Tue, Jun 18, 2019 at 7:58 AM Selman notifications@github.com wrote:
Having the same problem 😕 Anyone has the solution?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jenkinsci/rancher-plugin/issues/44?email_source=notifications&email_token=AGE4RB34MRJL6B5AMFBRNJ3P3DLXPA5CNFSM4HA5E4Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX6QWVY#issuecomment-503122775, or mute the thread https://github.com/notifications/unsubscribe-auth/AGE4RB5PAWQQOOM4W2KE2SDP3DLXPANCNFSM4HA5E4ZQ .
I created another jenkins job only containing the RancherBuilder and tried to pass the values as parameters to trigger that job from another jobs but I could not be successful to pass parameters to the plugin(probably does not support). Alternatively, created a static one, and triggered it from the original pipeline :
stages {
...
...
stage('Upgrading rancher service') {
if ( BUILD_OPTION == 'deployImage' ) {
build job: 'XXX-rancher-deployer'
}
}
}
}
But this is a quick fix, not a good solution(extra one job for each). Need to create something like [https://github.com/cdrx/rancher-gitlab-deploy](Rancher Gitlab Deploy)
Hi,
While trying to use this plugin in Jenkins 2.164.1, I get this message in the "Pipeline Syntax" section:
Any thoughts?