• Type: Bug
• Resolution: Cannot Reproduce
• Priority: Major
• Component/s: robot-plugin
• Labels:

  None
• Environment:

  Robot Framework plugin 1.6.4
  Workspace Cleanup Plugin 0.32

1. 

   robot_root.PNG

   11 kB

   2017-02-08 23:47

2. 

   ws_cleanup_fail.PNG

   21 kB

   2017-02-08 23:48

[JENKINS-41866] Robot Framework creates artifacts owned by root user

Collapse comment: Aleksi Simell added a comment - 2017-12-01 11:15

Aleksi Simell added a comment - 2017-12-01 11:15

Can you verify that those permissions do come from the plugin? i.e. if you run the job without post-build action, are the log files still with permission 777?

 

Output.xml, report.html, and log.html are created by RF, not this plugin.

Expand comment: Aleksi Simell added a comment - 2017-12-01 11:15

Aleksi Simell added a comment - 2017-12-01 11:15 Can you verify that those permissions do come from the plugin? i.e. if you run the job without post-build action, are the log files still with permission 777?   Output.xml, report.html, and log.html are created by RF, not this plugin.

Collapse comment: Sorin Sbarnea added a comment - 2018-03-16 11:29

Sorin Sbarnea added a comment - 2018-03-16 11:29

This is clearly not a bug and a local configuration mistake on you Jenkins. Jenkins user should never be able to gain root access, or to create files owned by other user, and on correctly configured system it does not.

Expand comment: Sorin Sbarnea added a comment - 2018-03-16 11:29

Sorin Sbarnea added a comment - 2018-03-16 11:29 This is clearly not a bug and a local configuration mistake on you Jenkins. Jenkins user should never be able to gain root access, or to create files owned by other user, and on correctly configured system it does not.