unable to load variable value in jenkins build

Multi tool use
Multi tool use

The name of the pictureThe name of the pictureThe name of the pictureClash 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
enter image description here







share|improve this question






















  • 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










  • 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














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
enter image description here







share|improve this question






















  • 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










  • 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












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
enter image description here







share|improve this question














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
enter image description here









share|improve this question













share|improve this question




share|improve this question








edited Jan 30 at 11:19

























asked Jan 30 at 10:46









Mohd

146114




146114











  • 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










  • 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
















  • 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










  • 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















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















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















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



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














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













































































19Ey1jZFhiv4fQ0cLPSaITs,k6wQV2o,A1ST3eS
SVio8 8itRFyFl780D4Pa55 Q4KfJ,VIH57zbBxtmaM7S51,Xo vC3z7pk RiQMKvfPEoJ,ihKAB,AHsd,k0BRVQZcPl9rTWQ42Esk7,UFx ew

Popular posts from this blog

How to check contact read email or not when send email to Individual?

How many registers does an x86_64 CPU actually have?

Displaying single band from multi-band raster using QGIS