Maintains historic versions of artifacts in multiple environments, but the database deployment needs to be more flexible
What is our primary use case?
We use UrbanCode Deploy for storing the artifacts of the environment. In both our production and non-production environments, we rely on UrbanCode as an artifact repository. For example, if we want to deploy something in production then we take our usual steps, such as stopping what needs to be stopped, then we deploy using UrbanCode, and then we restart to make our production environment available again. This solution is also useful for maintaining different versions of the artifacts because it has the capability of maintaining snapshots.
Pros and Cons
"The most valuable feature is the snapshot functionality, which allows us to access previous versions of the artifacts."
"I would like to have the agent up and running at all times, as opposed to only while it is in the DevOps pipeline."
What other advice do I have?
This is a solution that I recommend but I think that for anybody who is interested in implementing it, I would suggest that they start by reviewing the resources that IBM has online. It is not complicated, and they will be comfortable with how the variables are used and that kind of thing. I would rate this solution a seven out of ten.