Hi,
We working on automated deployment for our changes in OneIdentity using Azure DevOps. Right now we have a working pipeline but one of the bottlenecks we are having is the compiler.
High-over we currently have the following workflow:
- We create a (we call it) a package directory where all transports packages will be placed in for the item we are working at
- Sometimes we create different transport packages for different changes in our system. E.g. a package for Scripts, a package for Processes.
- We do this to have a better overview of our work.
- Developer does change in the DEV environment and puts the change in a change label
- The change label get exported to a transport package and will be saved in the so called package directory
- The package directory with all the transport packages is commited to our Azure DevOps GIT repository
- An automatic pipeline creates an artifact of the directory and moves it to the TEST environment
- The package directory will install all the transport packages inside the package directory using the DBTransporterCmd
- After installing all the transport packages the system gets compiled
- We know that it is possible to do a compile after a transport but i will get to that later.
- All is done in the TEST environment
- Our tester will test the changes made
- We are working on automated testing aswell but are not relying on that yet.
- Once testing is done the Tester will approve the post-approval step in Azure before moving it to the UAT environment.
- etc.
Now the issue here is that the DBCompilerCmd takes a long time doing the compile, sometimes up to 5 minutes per compile, this is also the reason why we do a compile after all the transport packages have been transported (if it is possible, sometime a compile is necessary inbetween transport packages).
Also I know it is possible to add modules to the blacklist for the DBCompilerCmd but then we need to find out based on what is inside each of the transport packages what can be excluded which is not easy.
To get to the point:
The DBCompilerCmd and the DBTransportCmd both take a very long time to compile while if you would do it using the Transporter or Designer the compile is almost instant. We are looking for a way to efficiently auto deploy our work but the long compile times are blocking the efficiency of the auto deployment because it is faster to just do it manually than using the CMD functionality.
I hope there is a solution to speed this up.
Thanks,
Patrick
