We are building our own Docker file that pulls in the Ignition Official Docker image. When we kick off a deployment of our docker image, the cloud environment we use builds the image using Looper. Now they are going to start forcing us to use a .looper.yml file that also integrates "static testing" with SonarQube. Does IA have a basic .looper.yml file configuration?
Who is "they" and what is Looper?
@kcollins @kcollins1 you familiar with this?
The only references I can find are this: GitHub - fawind/looper: Test runner for functional testing of dockerized microservices, which has no mention of YAML config files, and some .looper.yml
files in some public Walmart repositories... I think you might be asking about something that is specific to your org.
The "They" would be the corporate policy makers that control our cloud environment. Looper is their "Continuous Integration" build system.
Here is an example of a looper.yml file and what it does.
I didn't know if IA had something similar to this.
No, sorry. We're using Jenkins for our CI.
Looper seems to be your orgs own home grown thing: Concord | Case Study - Continuous Deployment
Looper was built to replace Enterprise Jenkins here.