.pct folder - store in Git or not

[lievendf]

The .pct folder contains metadata that is used for multiple purposes (dependency compilation, SonarQube analysis,...).
Should this data typically be stored in Git?
I would assume not, since it is generated, but it still has value to be kept.
Should it be kept as a separate build artifact?
We're looking at setting up SonarQube and I see the sonar-project.properties mentions:

sonar.oe.binaries: comma-separated list of build directories (where rcode can be found)
sonar.oe.dotpct: comma-separated list of .pct directories (if using a different directory in PCTCompile)
sonar.oe.dlc: OpenEdge installation directory

So I conclude that OpenEdge needs to be installed on the Sonar server and that the Sonar Scanner needs the r-code and .pct folder to operate as well.
Which means simply cloning the Git repo isn't enough if the .pct folder isn't in there (and binaries are obviously not in there either).
How do people typically set up an OpenEdge project (Git repo / artifact repository) for SonarQube analysis?

[stefandrissen]

Our build pipeline builds on a master agent, executes tests on lots of other agents, these agents publish their results (junit testsuites.xml + profiler output for code coverage) as artifacts which are then picked up in the final pipeline stage by the master agent which combines all and sends it to Sonar.

so no .pct in git
Sonar server does not need Progress OpenEdge installed, off the top of my head the installation directory is for ADE / web includes.

[gquerret]

• Sonar-scanner is always executed on one of your build agents, never on the SonarQube server side
  • For simple cases, you execute sonar-scanner right after the build / unit tests and on the same agent so it will have access to the .pct directory (for xref), rcode and profiler output.

[lievendf]

OK thanks, so if I understood it correctly, the sonar-project.properties "sonar.oe.dlc" setting is relative to where the sonar-scanner runs, which is typically the build agent?

which combines all and sends it to Sonar.
So it is sonar-scanner that sends data back to the server?
Still trying to fit the pieces together, but I'm starting to get the bigger picture I think...

[stefandrissen]

OK thanks, so if I understood it correctly, the sonar-project.properties "sonar.oe.dlc" setting is relative to where the sonar-scanner runs, which is typically the build agent?

So it is sonar-scanner that sends data back to the server?

Yes.