![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Nicolas De Loof
|
|
Components:
|
git |
|
Created:
|
28/Mar/13 11:38 PM
|
|
Description:
|
We have the use case where one git remote always contains what is released and only what is released. So all development is done in a development remote. At the point of release we want to merge the development remote into this release remote and then run a maven release build. Those on the development remote are expected to merge from the release into the development remote. Hence when using jenkins to do the work of merging from the development remote to the release remote the pre build merge should be a fast forward only merge.
That way we know all the work to test and certify the code has been completed. Should a non fast forward merge take place from development to remote it represents an integration case that should under go testing on the development remote.
Right now almost all of this can be done with the git plugin. However when doing prebuild merge the plugin won't fail if it is a fast forward merge. Thus it will go head and merge and push an integration case.
I would like to see the pre build merge support the option for fast forward merges only.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Mike Power
|
|
|
|
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/groups/opt_out.
