Updating a Bosh release

[Arunabha Ghosh]

Hi, I'm trying to update a bosh release using the following

1) Make local change to the local release files (say some .yml.erb)

2) Commit the change

3) Update the release yml file to increment the version number

4) Bosh upload release.

After these steps, bosh releases shows the new release version, however the commit hash of each release version is the same and the new template does not seem to be used. 

bosh releases

.

.

 cf-services-contrib | 2*       | 59465dc6+   |

|                            | 2.1*     | 59465dc6+   |

|                            | 2.2*     | 59465dc6+   |

|                            | 2.3      | 59465dc6+   |

How do I upload a release which uses the modified template file ?

Thanks

[Dr Nic Williams]

I think you're missing the "bosh create release" step. Was this what you're doing in step 3?

Nic

[Arunabha Ghosh]

Hmm, yes I was. I just did a create release followed by an upload release, however the results are the same, the has of the release is the same as before.

 cf-services-contrib | 2*       | 59465dc6+   |

|                     | 2.1*     | 59465dc6+   |

|                     | 2.2*     | 59465dc6+   |

|                     | 2.3*     | 59465dc6+   |

|                     | 2.4      | 59465dc6+   |

[Ferran Rodenas]

I'm confused about step 3 (Update the release yml file to increment the version number). Are you incrementing the version number manually? Bosh create release should increment it automatically.

- Ferdy

2013/10/26 Arunabha Ghosh <aruna...@gmail.com>

To unsubscribe from this group and stop receiving emails from it, send an email to bosh-users+...@cloudfoundry.org.

[Arunabha Ghosh]

Yes, I had to edit the release manifest to update the version number. Does create release generate a new release manifest ? if so, where is the file kept ?

[Ferran Rodenas]

Yes, it creates a new release manifest. Look at the dev_release dir (assuming you're not creating a final release).

- Ferdy

2013/10/29 Arunabha Ghosh <aruna...@gmail.com>

[Chris Brown]

I think you are both talking about different manifests. Ferdy is talking about the release manifest in dev_releases directory inside the root release directory and Arunabha is talking about the deployment manifest for the actual deployment of a release. As an aside, to avoid having to increment the version number each time you create a release you can use the value "latest" for the version number which the BOSH director will semantically interpret as the highest version number of the release requested.