Not specifying a repo platform results in "Invalid Platform Flag" error

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: repo-plugin
    • None
    • Environment:
      Jenkins 2.204.1 Repo Plugin 1.12.0

      When creating a new REPO project, leaving the platform field blank should result in no -p flag being passed to the repo init command. However, the following command is generated, resulting in a failure:
      repo init -u ssh://xxx/yyy -b master -p --depth=1 --current-branch
      An empty -p is generated, causing --depth=1 to be interpreted as the platform value.

      Manually specifying the value 'auto' will work as a work-around, but this is NOT the expected behavior.

      This is a new regression issue, as this used to work as expected.

       

            Assignee:
            Unassigned
            Reporter:
            Jeff Lange
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: