7.1.1.2
- Replace tokens improvements
- Bug fixes
When you set out to define a permissions model for IBM UrbanCode Deploy it’s often a requirement to document the model for discussions/approvals… While UCD provides tools to build and maintain the permissions model it doesn’t give you a ‘single view’ that can be used in workshops and other forums to discuss the operation of
We heard from a number of clients that it could be hard to understand how much they were using each agent and for what. We updated the Agent view pages to make this a lot easier to understand. Check it out: Jobs Run column in Agents table: A new column ‘Jobs Run’ has been added
UrbanCode Build’s now offers the ability to rearrange and move workflows. This gives an option for moving the Project workflows between projects along with the complete Build history and data. This helps the user setup a test project workflow without affecting the main project. Once the test project workflow is completely setup as desired, the
UrbanCode Build’s Job-as-Code is an alternate approach to configure job steps, as a simple plain JSON or YAML files. It also avoids configuring the job steps manually in UrbanCode Build UI. The challenges that users face while configuring job steps is to track the changes done to the job steps. For this problem, UrbanCode Build
Logging onto, particularly production machines, is not a DevOps best practice, so how can we get logs to diagnose faults? Particularly with Production systems, it’s a poor DevOps practice to login to machines to make changes. Ideally, everything should happen through your automated systems so there is no need. This prevents little ‘tweaks’ being done
You may have noticed that there is no documented way of adding files to a UCD Component version. The only ways open to you seem to be either the udclient or using source plugins to import your component version assets. But there must be a way right? The udclient does it – so how can I do that from