Closed nichtraunzer closed 3 years ago
Does the token you entered have enough permissions to create repos in Bitbucket?
AFAIK the issue happens within the script, if one tries to run the steps outside it works, so there is something bad formatted or not properly handled within the bash script...
I believe the root cause is that the specific Bitbucket instance is no longer allowing password based authentication. If we change the script to use Bitbucket token instead, then the script works as intended. The token needs to be created in the web UI, with Projects:Admin permission.
Describe the bug the script fails https://github.com/BIX-Digital/ods-contrib/blob/master/quickstart-with-jenkins/run.sh when trying to deploy a quickstarter (inf-terraform-aws) into an EDP project.
To Reproduce
Expected behavior The script shall create an EDP component (component ID test, project ID age, inf-terraform-aws qs).
Affected version (please complete the following information):
Log Output (ensure to remove any confidential information like tokens, project names, etc.
Additional context It fails at the curl statements which create the repository and the WebHook. PS: run.sh succeeds when curl commands are removed and an empty repo will be created upfront !!!
PPS: when changing the parameter (because i want to get the latest version of the QS)
to the latest 4.x branch the jenkins pipline will fail (but maybe i am using it here in the wrong way)