Just had a question about this feature, is deployment_id is generated automatically? Any way to control (or supply) the value?
The reason I ask is, we use multiple contexts (each context represents a single schema in Oracle DB) and we always run for all contexts (about 7-8) that we have.
If I could control deployment_id, i could use that for all contexts, so i can easily track all changesets for a given deployment (aka release).
I searched in docs but there is no mention of that yet, hence this question.
Thanks
Yes, the deployment_id is automatically generated, and there is currently no way to control or supply that value.
Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/
What exactly is that used for?
The deployment ID is used to support a new rollback type ‘rollback last update’. All the changesets that are applied to a database in a single update operation are given the same deployment id. Prior to this change that feature would need to be based on the deployment timestamp, which was not reliable.
Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/
