![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Praqma Support
|
|
Components:
|
pretested-integration-plugin |
|
Created:
|
11/Nov/14 2:45 PM
|
|
Description:
|
With multiple git repositories, the post-build step is not using them correctly and several situations have been seen where one repo is tried to be integrated into another and pushed.
This mixes up repositories and is fatal for the plugin.
Reproduce:
- using git scm plugin (not multiscm)
- configure it to two repositories
- repo1, explicitly named origin in the git scm configuration
- repo2, explicitly not named in the git scm configuration
- branch specifier that triggers on both repos if they change
- pretested integration configuration: master + origin
- both repo must be able to checkout into same folder, without filename clashes (this is not normal wanted behavior, but it doesn't matter for this test)
- make a commit on a ready branch in {{repo2}, with a new file that doesn't exist in either of the repo
Result: **The file get integrated into origin (repo1) instead of of not at all.
|
|
Environment:
|
2.2.0-snapshot build
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Blocker]() Blocker
|
|
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
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
