Drawbacks while creating content packusing oosha.bat utility

Idea ID 1677958

Drawbacks while creating content packusing oosha.bat utility

Hi ,

We are using using oosha.bat utility for creating CP , we are able to create a content pack but the utility is not able to find if there are any transition errors or dependency errors which will lead to problem at the time of deployment as content packs created are getting deployed even though there are errors .
We would like to know if there is any possibility to check for these dependent error at the time creating the content packs of flows.

2 Comments
Outstanding Contributor.
Outstanding Contributor.
Status changed to: Waiting for Votes
 
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

I agree.. This is important to have when create CP in CI/CD mindset. It should give option to  include  dependencies 

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.