On May 5, 2016, at 13:28, haosdent <[email protected]<mailto:[email protected]>> wrote:
>There is no explicit statement about what Mesos means when it runs a task as >some other user. I think this is just ensure the running user of the task is the user you given. In Mesos, it jus call the [setuid](http://linux.die.net/man/2/setuid) to change the user, It would not execute something like the bashrc script of user. Thanks. That makes it very clear and explains why I am having issue. On Thu, May 5, 2016 at 7:41 PM, DiGiorgio, Mr. Rinaldo S. <[email protected]<mailto:[email protected]>> wrote: Hi, Recently I noticed that the Mesos Jenkins plugin supports the setting of environment variables. Somewhere between 0.26 and 0.28.1, settings like USER= HOME= were required to get things to work the way they had worked. I have been able to set the environment this way but I have some concerns about it. There is no explicit statement about what Mesos means when it runs a task as some other user. Clearly it is not running some of the scripts normally run during login. This was a constant source of confusion with Jenkins. If one can state what exactly is done to create the user environment each platform and how it is different that others it will save countless hours of debugging IMO. I realize OSX is an odd system -- linux at times, Apple specific at times in areas that conflict with Linux but this will only get more complicated when Windows agents become available. Rinaldo -- Best Regards, Haosdent Huang
