unable to load variable value in jenkins build
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
ok i have situation my in current jenkins build.
Build steps are like this
sh new_script.sh $USER
helm package $USER
container_name=`helm install $USER-0.1.0.tgz | grep ContainerCreating | awk 'print $1'`
echo "$container_name"
password=`openssl rand -base64 14`
echo -e "$passwordn$password" | kubectl exec -i $container_name -- passwd
but when i run this job, it fails to load the variable container_name value.
How can we resolve this
jenkins
asked Jan 30 at 10:46
Mohd
146114
add a comment |Â
up vote
0
down vote
favorite
ok i have situation my in current jenkins build.
Build steps are like this
sh new_script.sh $USER
helm package $USER
container_name=`helm install $USER-0.1.0.tgz | grep ContainerCreating | awk 'print $1'`
echo "$container_name"
password=`openssl rand -base64 14`
echo -e "$passwordn$password" | kubectl exec -i $container_name -- passwd
but when i run this job, it fails to load the variable container_name value.
How can we resolve this
jenkins
asked Jan 30 at 10:46
Mohd
146114
Thegrepis obviously not finding the stringContainerCreatingin the output fromhelm install. You should run thathelmcommand and check what it's actually outputting.
– Kusalananda
Jan 30 at 10:54
@Kusalananda : u were right! i rectified that! there was some issue with environment! now there is a new issue! i have updated the snapshot again!
– Mohd
Jan 30 at 11:17
I don't know about the actual error that you now get, but ifpasswdis the standardpasswdprogram to change a password (the root password in this instance), I'd be surprised if it was able to read the password from its standard input. See e.g. stackoverflow.com/questions/714915/…
– Kusalananda
Jan 30 at 11:27
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
ok i have situation my in current jenkins build.
Build steps are like this
sh new_script.sh $USER
helm package $USER
container_name=`helm install $USER-0.1.0.tgz | grep ContainerCreating | awk 'print $1'`
echo "$container_name"
password=`openssl rand -base64 14`
echo -e "$passwordn$password" | kubectl exec -i $container_name -- passwd
but when i run this job, it fails to load the variable container_name value.
How can we resolve this
jenkins
asked Jan 30 at 10:46
Mohd
146114
ok i have situation my in current jenkins build.
Build steps are like this
sh new_script.sh $USER
helm package $USER
container_name=`helm install $USER-0.1.0.tgz | grep ContainerCreating | awk 'print $1'`
echo "$container_name"
password=`openssl rand -base64 14`
echo -e "$passwordn$password" | kubectl exec -i $container_name -- passwd
but when i run this job, it fails to load the variable container_name value.
How can we resolve this
jenkins
asked Jan 30 at 10:46
Mohd
146114
edited Jan 30 at 11:19
asked Jan 30 at 10:46
Mohd
146114
asked Jan 30 at 10:46
Mohd
146114
asked Jan 30 at 10:46
Mohd
146114
146114
Thegrepis obviously not finding the stringContainerCreatingin the output fromhelm install. You should run thathelmcommand and check what it's actually outputting.
– Kusalananda
Jan 30 at 10:54
@Kusalananda : u were right! i rectified that! there was some issue with environment! now there is a new issue! i have updated the snapshot again!
– Mohd
Jan 30 at 11:17
I don't know about the actual error that you now get, but ifpasswdis the standardpasswdprogram to change a password (the root password in this instance), I'd be surprised if it was able to read the password from its standard input. See e.g. stackoverflow.com/questions/714915/…
– Kusalananda
Jan 30 at 11:27
add a comment |Â
Thegrepis obviously not finding the stringContainerCreatingin the output fromhelm install. You should run thathelmcommand and check what it's actually outputting.
– Kusalananda
Jan 30 at 10:54
@Kusalananda : u were right! i rectified that! there was some issue with environment! now there is a new issue! i have updated the snapshot again!
– Mohd
Jan 30 at 11:17
I don't know about the actual error that you now get, but ifpasswdis the standardpasswdprogram to change a password (the root password in this instance), I'd be surprised if it was able to read the password from its standard input. See e.g. stackoverflow.com/questions/714915/…
– Kusalananda
Jan 30 at 11:27
The
grep is obviously not finding the string ContainerCreating in the output from helm install. You should run that helm command and check what it's actually outputting.– Kusalananda
Jan 30 at 10:54
The
grep is obviously not finding the string ContainerCreating in the output from helm install. You should run that helm command and check what it's actually outputting.– Kusalananda
Jan 30 at 10:54
@Kusalananda : u were right! i rectified that! there was some issue with environment! now there is a new issue! i have updated the snapshot again!
– Mohd
Jan 30 at 11:17
@Kusalananda : u were right! i rectified that! there was some issue with environment! now there is a new issue! i have updated the snapshot again!
– Mohd
Jan 30 at 11:17
I don't know about the actual error that you now get, but if
passwd is the standard passwd program to change a password (the root password in this instance), I'd be surprised if it was able to read the password from its standard input. See e.g. stackoverflow.com/questions/714915/…– Kusalananda
Jan 30 at 11:27
I don't know about the actual error that you now get, but if
passwd is the standard passwd program to change a password (the root password in this instance), I'd be surprised if it was able to read the password from its standard input. See e.g. stackoverflow.com/questions/714915/…– Kusalananda
Jan 30 at 11:27
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f420634%2funable-to-load-variable-value-in-jenkins-build%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
The
grepis obviously not finding the stringContainerCreatingin the output fromhelm install. You should run thathelmcommand and check what it's actually outputting.– Kusalananda
Jan 30 at 10:54
@Kusalananda : u were right! i rectified that! there was some issue with environment! now there is a new issue! i have updated the snapshot again!
– Mohd
Jan 30 at 11:17
I don't know about the actual error that you now get, but if
passwdis the standardpasswdprogram to change a password (the root password in this instance), I'd be surprised if it was able to read the password from its standard input. See e.g. stackoverflow.com/questions/714915/…– Kusalananda
Jan 30 at 11:27