Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jenkins-plone-org assumes same repo name for forks #368

Open
Faakhir30 opened this issue Sep 8, 2024 · 0 comments
Open

Jenkins-plone-org assumes same repo name for forks #368

Faakhir30 opened this issue Sep 8, 2024 · 0 comments

Comments

@Faakhir30
Copy link

Jenkins assumes the same repo name for forks for running tests.

For reference, I created a PR in Products.CMFPlone, from my forked repo with the name Products.CMFPlone-repo, running

@jenkins-plone-org please run jobs

Jenkin Jobs are getting its assuming I also cloned with the same name:

image

Steps to reproduce

  1. Create a fork of Products.CMFPlone or any other repo supporting the above please run jobs comment.
  2. Make sure the fork is with a different name than the upstream repo name.
  3. Create a PR and run the above-mentioned command, then view build logs.

NOTE: I've worked around this by renaming my clone to the exact upstream name, however, solving this would be an enhancement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant