hi, The process looks excellent but wont it ask for bitbucket authentication on "git pull origin master" while running deploy.sh? Like it does on our git bash?
Cloud Native Engineer at Container Solutions. Co-organizer of Kubernetes Community Days. Creator of Get Going With Kubernetes. Lead maintainer of OSS project markdown-badges. Writer and Speaker.
Hi, thanks for your kind words.
I'm really sorry for my late response as I had forgotten that comment notifications are not sent to emails.
I do hope however that you have been able to solve this issue.
Nonetheless, here's my response.
At some points when I tried this, I did encounter the authentication issue like you mentioned, hence the debugging tips that I mentioned at the end of the article.
Adding the deploy key and SSH key should take care of authentication. Cloning the repo from the start handles the case of known hosts. Afterwards, things should go on smoothly and the pipeline commands should execute in a non-interactive mode.
hi, The process looks excellent but wont it ask for bitbucket authentication on "git pull origin master" while running deploy.sh? Like it does on our git bash?
Hi, thanks for your kind words.
I'm really sorry for my late response as I had forgotten that comment notifications are not sent to emails.
I do hope however that you have been able to solve this issue.
Nonetheless, here's my response.
At some points when I tried this, I did encounter the authentication issue like you mentioned, hence the debugging tips that I mentioned at the end of the article.
Adding the deploy key and SSH key should take care of authentication. Cloning the repo from the start handles the case of known hosts. Afterwards, things should go on smoothly and the pipeline commands should execute in a non-interactive mode.
Sounds great, thank you Ileriayo.