Skip to content

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

@Faakhir30

Description

@Faakhir30

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions