[jbosstools-issues] [JBoss JIRA] (JBIDE-12993) Cleanup/create plain checkout.sh script for jbosstools repos from github
[
https://issues.jboss.org/browse/JBIDE-12993?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12993:
------------------------------------
checkout.sh doesn't recover well from a failure:
{code}
$ ./checkout.sh -n -u nickboldt jbpm
Cloning into /home/nboldt/tru/jbosstools-jbpm...
remote: Counting objects: 11754, done.
remote: Compressing objects: 100% (3547/3547), done.
fatal: read error: Connection reset by peer
fatal: early EOF
fatal: index-pack failed
./checkout.sh: line 137: cd: /home/nboldt/tru/jbosstools-jbpm: No such file or directory
fatal: Not a git repository (or any parent up to mount parent )
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
/home/nboldt/tru/jbosstools-jbpm not found
{code}
Maybe if EOF is encountered or after clone the dir doesn't exist, the script should
loop back and try again?
Cleanup/create plain checkout.sh script for jbosstools repos from
github
------------------------------------------------------------------------
Key: JBIDE-12993
URL: https://issues.jboss.org/browse/JBIDE-12993
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Reporter: Max Rydahl Andersen
Assignee: Max Rydahl Andersen
Fix For: 4.0.0.CR1
nick have done some work on the checkout script at:
https://github.com/jbosstools/jbosstools-build/blob/master/scripts/checko... but it is
assuming a bit too much IMO, at least more than we can currently assume.
I suggest:
cleanup to checkout as if you just did clones (i.e. no removal of jbosstools- prefix)
allow to do it to a directory
don't setup branches (not something that you necessarily want to do on all repos and
can be done better by custom/specific scripting)
fix bootstrap profiles to use full names not the names done in this script.
--
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