Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Specify location of generated temporary post-processor files

#1
Hello all,

We have been using RoboDK in a GitLab CI pipeline, and after the pipeline finishes, all Post*.py files locates in AppData/Local/Temp are left and cannot be deleted from the pipeline. Over time, quite an amount of these Post*.py files gathered and will fill up the disk. The CI job cannot delete those files directly because they are outside of the context accessible by the job, which is why I would like to know:

Is there a way to specify where these temporary files are stored to? We've observed that for Windows, this seems to always be the AppData/Local/Temp folder, while for Linux (Ubuntu) it is always the /tmp folder.

I could not find a way to change the location where to store these temporary files, only the location of the generated robot program when executing that Post*.py file can be set.

Thank you all!
#2
Thank you for your feedback, RoboDK generates temporary PY files in the temporary directory of your computer. These files always follow the same pattern: "Post" + [programname] + ".py"). So you could delete these files after your program is generated.

In the near future we'll make sure the Post intermediate file is deleted automatically (right after generation or when closing RoboDK). I agree it would be better if RoboDK cleaned up these files to make sure the size used by temporary files doesn't keep growing.
#3
Thank you Albert!

It would be indeed good if these can be deleted automatically, currently we need to manually delete them from the GitLab runner machine, which is supposed to handle everything automatically.

Looking forward to the update!
#4
We just published an update that automatically deletes the temporary files when you generate programs.

If you want to see the intermediate temporary file you can run RoboDK in debug mode, this won't delete the temporary files.

You can take the latest version here: https://robodk.com/download.
#5
That's great news, thank you very much! Thank you again!
  




Users browsing this thread:
1 Guest(s)