When you are performing transports in Figaf it would be nice to get input from automated validation. It could be CPILint, JUnit tests or some static code checks.
In Figaf we do have the manual approval of artifacts and give the architect everything needed to approve the change:
- Graphical view of differences
- Source code difference
- Mapping diff
- Changes in Externalized parameters
- Sanity checks if everything is fine
But if you want to include much more checks into the process you can create a pipeline that checks each time Figaf updates an iflow.
When you then try to create a transport with that iflow you will get an error. At the moment, you cannot approve the transport.
It is one of the services that require more effort to work with since you need to set up a Git repository and build the validation pipeline. We have a template for GitHub Actions that you can use as the basis.
You can see the setup here.
Watch on YouTube Validate SAP Cloud Integration in your pipelines or actions
You can read the manual and the example here.
