Re: Reg cf-235 release


Amit Kumar Gupta
 

Don't run the update script the first time. git gets confused because the
remote URL for one of the recursive submodules has changed. I'm not sure
if there's a non-manual way for the script to deal with that case, but it's
easy to avoid:

$ rm -rf cf-release/
$ git clone git(a)github.com:cloudfoundry/cf-release
$ cd cf-release/
$ git checkout -b branchcf edc3e3c9
$ ./scripts/update


On Fri, Jul 15, 2016 at 1:33 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi



We are trying to use cf-235 release.

Following are the steps we have used for creating the release:



1. sudo git clone https://github.com/cloudfoundry/cf-release

2. cd cf-release/scripts

3. ./update

4. sudo git checkout -b branchcf edc3e3c9

5. cd cf-release/scripts

6. ./update



We get the following error while the checkout from the branch, due to
which I cannot create the cf-235 tar with some custom changes.



…………………………………………………………………………………………

……………………………………………………………………………………….

Submodule path 'src/loggregator/src/github.com/ugorji/go': checked out
'f1f1a805ed361a0e078bb537e4ea78cd37dcf065'

Submodule path 'src/smoke-tests': checked out
'f3092b9040bf93cb3a6a7670bf53be11b2d0f957'

Submodule path 'src/uaa-release': checked out
'68cf1f16843392b4f115719047eaf61ef4b67375'

Submodule path 'src/uaa-release/src/uaa': checked out
'616e8bcc58f9bc16f9d9ec806da1b0bf0f5dae85'

*Failed to recurse into submodule path 'src/consul-release'*



Regards

Nithiyasri

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.