Bug #1965
git cr not supporting tags
Start date:
14.02.2017
Due date:
% Done:
100%
Estimated time:
origin:
Description
Currently it is not possible to run gitcr on a tag. When trying with a tag
As observed by Tracekey
02/14 11:45:48 [1]...entRepositoryImpl [800]: Using GIT-CR: component:com.zfabrik.boot.config/scenarioRepository,repo:com.zfabrik.boot.config/scenarioRepository,prio:550,mode:strict,checkDepth:1073741823,roots:{=fs-root:/disk_1/tracekey-pharmaceutical/z2-base.core/work/repos/com_zfabrik_boot_config_scenarioRe$
02/14 11:45:54 [1]...entRepositoryImpl [800]: Pulled deltas within 5566msec from GIT-CR: component:com.zfabrik.boot.config/scenarioRepository,repo:com.zfabrik.boot.config/scenarioRepository,prio:550,mode:strict,checkDepth:1073741823,roots:{=fs-root:/disk_1/tracekey-pharmaceutical/z2-base.core/work/repos/com_z$
02/14 11:45:54 [1]...entRepositoryImpl [800]: Branch has changed! Will switch GIT-CR: component:com.zfabrik.boot.config/scenarioRepository,repo:com.zfabrik.boot.config/scenarioRepository,prio:550,mode:strict,checkDepth:1073741823,roots:{=fs-root:/disk_1/tracekey-pharmaceutical/z2-base.core/work/repos/com_zfab$
02/14 11:45:54 [1]...entRepositoryImpl [900]: WARNING: Updating GIT-CR: component:com.zfabrik.boot.config/scenarioRepository,repo:com.zfabrik.boot.config/scenarioRepository,prio:550,mode:strict,checkDepth:1073741823,roots:{=fs-root:/disk_1/tracekey-pharmaceutical/z2-base.core/work/repos/com_zfabrik_boot_confi$
02/14 11:45:54 [1]...entRepositoryImpl [900]: WARNING: java.io.IOException: No such branch '2017.1-demo' inside Repository[/home/tracey/tracekey-pharmaceutical/z2-base.core/work/repos/com_zfabrik_boot_config_scenarioRepository/git/.git]!
02/14 11:45:59 [1]...entRepositoryImpl [800]: WARNING: 'dev.tracekey.com' IS NOT reachable!
02/14 11:45:59 [1]...entRepositoryImpl [800]: WARNING: 'pharmaceutical' will be ignored because it's an optional repository or running in relaxed mode
Idea:
- instead of creating local tracking branches to support gitcr for branches, uses directly the commit from the remote branch or tag. This way we can achieve a general way of addressing commits to check out for the local clone in z2.
- Furthermore, it would be sufficient to do a shallow clone and reduced to a single history line.
Updated by Henning Blohm almost 8 years ago
- Status changed from To Be Documented to Resolved
- % Done changed from 0 to 100
Applied in changeset internal:internal-office|r2594.