I have a different repo for all jenkins jobs and in there a pipeline to notify if a pull request (PR) is created. The PR is however in an other repo. At the moment, I have to specify both repos, with the one to listen to the PR being the last one.
That whoever is a problem, because the path where the repos are fetched into gets a very long name (ca. \workspace\jobname@script\e5a434ffe1804583e5f35a45144731c8cfd98697f97bf0850116deb24dbc70e8)
that cases git to fail:
stderr: error: unable to create file ...: Filename too long
It also is not practical to pull a repo to just send notes that there is a PR.
I have a different repo for all jenkins jobs and in there a pipeline to notify if a pull request (PR) is created. The PR is however in an other repo. At the moment, I have to specify both repos, with the one to listen to the PR being the last one.
That whoever is a problem, because the path where the repos are fetched into gets a very long name (ca.\workspace\jobname@script\e5a434ffe1804583e5f35a45144731c8cfd98697f97bf0850116deb24dbc70e8)
that cases git to fail:
stderr: error: unable to create file ...: Filename too long
It also is not practical to pull a repo to just send notes that there is a PR.
I looked into the old bitbucket-plugin there is the possibility to set an alternative URL (https://github.com/jenkinsci/bitbucket-plugin/commit/d7a8bda42db51ed178e835211db269beaaa39e6e).
Is it possible to implement something like that here too?
Thank you very much