Do I need Root Access to setup an atlassian/trigger-pipeline?

Christopher Hahn October 29, 2020

My first attempt is using two repos created under my Personal Workspace.

There is driving-repo and target-repo.

The driving-repo pipeline looks like this:

  script:
- echo Running the trigger
- pipe: atlassian/trigger-pipeline:4.2.1
variables:
BITBUCKET_USERNAME: 'myusername'
BITBUCKET_APP_PASSWORD: 'llllllllllllllllllll'
REPOSITORY: 'target-repo'
PIPELINE_VARIABLES: >
[{
"key": "VERSION",
"value": "999.999.999"
},
{
"key": "SERVICE",
"value": "specific-service-name",
}
]
WAIT: 'true'
CUSTOM_PIPELINE_NAME: 'update-pipeline.yml'
DEBUG: 'true'

(it just attempts to invoke the target-repo and pass it vars)

The target-repo has the custom pipeline file "update-pipeline.yml":

pipelines: 
default:
-
step:
name: Test the trigger
script:
-
git status
- echo $SERVICE
- echo $VERSION

 

But it complains about some other file name:

✖ Error: {"error": {"message": "Bad request", "detail": "bitbucket-pipelines.yml not found.", "data": {"key": "result-service.pipeline.yml-not-found", "arguments": {}}}}Build teardown<1s

Well, this Q sucks....but any pointers will be appreciated!   

2 answers

1 accepted

0 votes
Answer accepted
Christopher Hahn October 29, 2020

It is confirmed.

I can add that that error came from the CUSTOM_PIPELINE_NAME setting.  

0 votes
Christopher Hahn October 29, 2020

Well, I simplified the driver project down to just the target repo name and credentials and it worked fine:

✔ Build started successfully. Build number: 5.

So that is that.  I must have an issue with my passed parameters....

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events