Bitbucket vs Transport Case

[Tina Hart]

Good Morning,
We've been using the Transport Case between our development and production environments and it's been working well.  As some teams start to use services like BitBucket now to ensure their scripts and code outside of Automic are updated, there has been some discussions if we should be moving to this for version control and transport management instead of the Transport Case.
One interesting thing while reading through the documentation on this, is that it makes a mention that everything in the client will be overwritten?  One use case have is that there are some dependencies on jobs across different systems which different teams are responsible for.  If we do this, do we risk overwriting information that perhaps should not be overwritten?  Is it best to segregate the teams that want to use BitBucket in to their own clients and then setup the connections to the service per client?

This might not be something that we do, but before we even test, I want to make sure we won't be breaking anything that already exists.

Thanks in advance for any feedback!
Tina

[Pete Wirfs]

UC4 objects are not overwritten if the version control feature is turned on.  This is set in variable UC_CLIENT_SETTINGS.  When turned on, the UC4 database maintains historical copies that are easily restored.

https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/12.3/Automic%20Automation%20Guides/help.htm#AWA/Variables/UC_CLIENT_SETTINGS/UC_CLIENT_VERSION_MANAGEMENT_Parameters.htm

EDIT:
I don't know Bitbucket

------------------------------
Pete Wirfs
SAIF Corporation
Salem Oregon USA
------------------------------

[Tina Hart]

Thanks for that!
This is what we currently have configured, and has worked as expected since we implemented it.  The one specific team that uses Bitbucket are hoping to also use that instead of or in addition to Automic's built-in features.  Their main reason is to use one tool to manage all versions across all of their systems.
It's an interesting concept though, but is really only for one group of users.  Personally, Version Management works just fine for the types of jobs that we're running, but for this group they are hoping to function more DevOps and have everything updated in the same pipeline.