Does Automic offer source control software (for software developmen) or can a product like UC4 just integrate with a product like TFS and Subversion?
Hi welcome to the Automic Community!
To try and answer your question, it depends on the use case. For the ONE Automation engine, Version Control and Centralized Script Management is part of the basic functionality. And then we also have solutions that integrate with Subversion, TFS, Perforce, etc.
There's quite a few options on how to integrate with other Applications.
Hi Jennifer. thank you for answering my question. Where can I find more information regarding the product of "ONE Automation engine"? My company bought Application Manager Version 8 is the the "One Automation Engine"?
It’s not clear to me what facet of source control you are asking about. Is it:
1. Can UC4 directly control the development of non-UC4 objects of other systems, such as programs, executables and shell scripts?
2. Can UC4 schedule, execute, etc., products such as you mentioned to promote the source and executables from, for example, development, test, AQ and production?
3. Does UC4 support source control for its own objects such as jobs and flows?
4. Do you wish to replace your existing source control product with UC4's versioning capability?
5. Something else?
I am a user of UC4's Operations Manager under V8 and cannot directly speak to the AM component. I am aware that the two products (AM and OM) are merging in V9 and above so I can only address what OM under V8 is capable of now. I have heard that there may be improvements in future releases but I am not aware of any substantive details. The only reference that I have seen is in this forum thread - http://community.automic.com/discussion/comment/1042/#Comment_1042 .
While there is object versioning, as Jennifer states, for OM it could hardly be described as a robust development environment for its own components. For example it does not support such basic functionality that I would expect such as: check-out, concurrent development and version comparison to display differences (delta). It is only capable of executing the most current version of an object in a Client. Restoring a previous version just makes it the "next" version of the object resulting in two identical versions though with different modified dates.
There are many other shortcomings and the most notable missing functionality in automating the promotion activities of UC4 objects from one Client or System to the next. I would not consider that UC4's own limited capabilities could be used to replace all of the functional richness that one finds in a commercial grade Source Control system, if that is your intent.
I am a firm supporter of the UC4 product and its capabilities. However, it is sorely lacking in its current ability to support a true development environment for its own objects. I attended an Application Release Automation (ARA) presentation at the last Innovate conference. While it appears to answer most of the pure promotion aspects it apparently still falls short in addressing the other parts of a complete development life cycle.
I sure hope I'm wrong and would love to be corrected, but I doubt it. ;)
I agree that there is opportunity for additional functionality
here. From Automic's viewpoint though, I can fully understand that it is
(and should be) secondary to automated scheduling.
We are using TFS with Automic V9 and homegrown integration.
Our homegrown solution captures and tracks approvals, and when a deploy has
been fully authorized, it schedules it to run in Automic via the
I attended a regional (Portland Oregon) Automic meeting recently
where I gained more confidence that ARA sounds like it is headed in the
right direction. The flip side of that coin is it might be targeting the
needs of the largest datacenters, and I work for a small datacenter that might
not be able to justify the setup/integration expense. I will certainly be
exploring the possibilities that ARA creates though.
I was always a bit perturbed that an automation product such as UC4 did not include automation for its own components and if you wanted something you needed to "roll your own". The Best Practice Guide has a nicely presented Dos & Don'ts topic regarding Test and Production systems but provides nothing within the product to support it in an automated manner.
We have written, as have you, tools to support this functionality. It appears that ARA is probably going to address the basic cross Client and System promotions and that's a good thing. It is just too bad that it does little to support the actual requirements for a fully functional object development life cycle that one has come to expect with even the most basic source development tools.
Given my limited understanding of its basic architecture and implementation I don't hold much hope for significant product improvement in this particular area. Even as it exists today, it does not significantly inhibit the ability to support a reasonable development cycle; it would just be really nice to have a better one.
Retrieving data ...