tony707 Posted August 21, 2017 Report Share Posted August 21, 2017 Hi, Is there a way I can manually increment the next changeset id to a specific value ? Thank you, Link to comment Share on other sites More sharing options...
calbzam Posted August 21, 2017 Report Share Posted August 21, 2017 Hi Tony, Not sorry, the changeset id is a local identificator and it can't be configurable. If you replicate the branch to a different repo, the same changeset can have a different lcoal identificator number. For global changeset identification, please use the changed GUID value. Regards, Carlos. Link to comment Share on other sites More sharing options...
psantosl Posted August 22, 2017 Report Share Posted August 22, 2017 If you need to have something custom, why don't you attach an attribute to it? What is your use case? Link to comment Share on other sites More sharing options...
tony707 Posted August 22, 2017 Author Report Share Posted August 22, 2017 Originaly we used the changeset id as a version number. But as Carlos said we replicated only some branches to a new repository and got differents changeset ids (less than before). We'll use a different versionning scheme as for now. Thank you, Link to comment Share on other sites More sharing options...
psantosl Posted August 23, 2017 Report Share Posted August 23, 2017 Isn't the GUID good enough on that cases? What we do: increment a build number on each successful build: we published a series of blogs posts about it :-) Link to comment Share on other sites More sharing options...
tony707 Posted August 28, 2017 Author Report Share Posted August 28, 2017 We needed a incremental build number like you, thats why the GUID was not an option. Thanks for the link, this should solve our issue Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.