Issue Type: Bug Bug
Assignee: Praqma Support
Components: pretested-integration-plugin
Created: 08/Dec/14 2:55 PM
Description:

_Initial job configuration_

  • Four repositories in MultiScm configuration - one svn, three git
  • Two git repositories in one MultiScm SCM configurations:
  • *repo1*, named so it becomes default named `repo1`
  • *repo2*, named so it becomes default named `repo2`
  • branch specifier `*ready/*`
  • Checkout to sub-directory: repo1s
  • Prune stale remote-tracking branches
  • Wipe out repository & force clone
  • One git repository in one MultiScm SCM configurations:
  • *repo3*, named: `repo3`
  • branch specifier `*ready/*`
  • Checkout to sub-directory: repo3
  • Prune stale remote-tracking branches
  • Wipe out repository & force clone
  • One SVN repository in one MultiScm SCM configuration:
  • svn-repo checkout path
  • pretested integration configuration:
  • `master`
  • `repo3`
  • Accummulated strategy

_Observations_

  • Pushing a ready branch to `repo3`, but there is nothing to do reported with error `Nothing to do the reason is: The branch name (repo3/ready/dev_865487921) used by git, did not match a remote branch name. You might already have integrated the branch`

The problem is in the findSCM method, that just always return the first found SCM.

Project: Jenkins
Priority: Minor Minor
Reporter: Bue Petersen
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to