Dedicated report to zip and store zip operations is client cli #4620
Replies: 1 comment
-
|
Hi, I may not understand the situation exactly. If I understand correctly, there is a build server that runs "CodeChecker analyze". This machine doesn't have access to the CodeChecker server. So, the report folder needs to be moved to another machine which does have access to the CodeChecker server. This other machine will upload the reports with "CodeChecker store". Is this right? Is the motivation behind the question that it's easier to transfer a single file between machines than to transfer a directory? I assume, there will be some script or CI job that does this transfer. Couldn't that script also include the required compression step? Thank you! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
as I understand the code of the cli for store, currently, it creates a zip file, uploads it the server and removes the zip file in any case. This requires a direct connection between a worker machine having access to the repo and the code checker server. We, and I guess I am not the only one, having an environment, where the web servers are isolated from the usual CI workers.
So I either can
Ok contained information might be even the same. But first still seems a bit clunky with packing, copying, unpacking, packing, storing. So I can spare out at least one packing and unpacking.
Is my understanding of the code correct? Are there no options to do so at the moment.
It would look like, to create the report zip:
CodeChecker store --name Foo --to-file report.zip /data/converted_reportand, to upload:
If this is of interest and there is no implementation for such, I would implement this as options for
CodeChecker storeand contribute. Are you interested in such?Beta Was this translation helpful? Give feedback.
All reactions