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 Sep 21, 2022. It is now read-only.
Hello,
i think use/set token in pipeline call is not working as expected.
I don't want to set in Jenkins global configuration the ACLToken for Consul.
Then I tried to set the Token via pipeline wrapper call itself.
But the token is not taken from the pipeline call it throws a 403 and in the output the url don't have the part ?token=my-nice-token
this is my call
`node {
stage('wraper'){
script{
TEST_KEY = ''
Hello,
i think use/set token in pipeline call is not working as expected.
I don't want to set in Jenkins global configuration the ACLToken for Consul.
Then I tried to set the Token via pipeline wrapper call itself.
But the token is not taken from the pipeline call it throws a 403 and in the output the url don't have the part ?token=my-nice-token
this is my call
`node {
stage('wraper'){
script{
TEST_KEY = ''
}`
and output is this:
[Pipeline] wrap Consul READ URL: http://myconsul:8500/v1/kv/path/path/path/test<here is something missing> Response Headers: Content-Type=text/plain; charset=utf-8 Vary=Accept-Encoding Date=Fri, 13 Sep 2019 07:06:45 GMT org.apache.http.client.ClientProtocolException: Unexpected response status: 403
The text was updated successfully, but these errors were encountered: