[Bug] - Cross REPO connection is not happening

[saivamsibodavulaTR]

Hello Team.

Firstly I would like to appreciate for this Work Action., that would enable integration from Github actions and ADO Pipelines.

I do have a concern, in fact it throwed me a limitation. my scenario is: I have N number of Microservices{ Facets}, where they are holding respective repos in the Github ( MS1, MS2 ,MS3 ,MS4 and repos are MS1, MS2, MS3, MS4) and i have single azure pipeline where all these microservices are passed as parameters.

but in this action, i have observed, a limitaion that , the ADO pipeline connection is happening only, if the github repo and Azure Pipeline Repo are SAME. what if I have a single file in ADO Pipeline that work for all the REPOS.

its throwing the following error:

[debug]pipeline is not linked to same Github repo

[debug]Input: {

[debug] "definition": {

[debug] "id": 2334

[debug] },

[debug] "project": {

[debug] "id": "66e74794-9916-410b-b624-07d49748bbff"

[debug] },

[debug] "sourceBranch": null,

[debug] "sourceVersion": null,

[debug] "reason": 1967,

[debug] "parameters": "{\"servicename\": \"hybrid\", \"appversion\": \"needs.build.outputs.build_version\", \"branchname\": \"Vamsi_Feature/Scaleset\"}"

I am just giving the project URL and Pipeline name. it should be working on irrespective of the REPOS.

please suggest me if i am missing something.

Thanks.

[catoa]

I am also receiving the same error when I believe that this should work. I see a similar output to @saivamsibodavulaTR

##[debug]pipeline is not linked to same Github repo
##[debug]Input: {
##[debug]    "definition": {
##[debug]        "id": 87
##[debug]    },
##[debug]    "project": {
##[debug]        "id": "f41c5b76-47de-4297-9faa-5d36abe535d7"
##[debug]    },
##[debug]    "sourceBranch": null,
##[debug]    "sourceVersion": null,
##[debug]    "reason": 1967,

[tjcorr]

Those are just debug level logs that shouldn't actually create any error and can safely be ignored. Are you receiving some other error farther down in the logs? I can confirm that you can use this action to call any ADO pipeline that your PAT has access to regardless of what project/repo the pipeline is defined.

[saivamsibodavulaTR]

Those are just debug level logs that shouldn't actually create any error and can safely be ignored. Are you receiving some other error farther down in the logs? I can confirm that you can use this action to call any ADO pipeline that your PAT has access to regardless of what project/repo the pipeline is defined.

This is not expected i think so., And even in Debug Logs., It shows pipeline is not linked to same Github repo, this only occurs while trying to connect with cross repo scenario, even with a PAT key with full rights and access levels...

Could you consider this to rectify this.

[saivamsibodavulaTR]

@tjcorr ., By chance any update on this !.