|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Hmmmh, no sysadmin background ... I suppose ? (no offense here !)
BUT: Why should one run a program that is supposed to provide a service function (this is where the name is coming from
) under the expectation that it has access to the Desktop?
Jenkins is not meant to be run as a desktop program !!!
Obviously you seem to have got the idea fundamentally wrong !?
And: If there should be plugins for a service(and this is, what Jenkins is all about: a service!) which behave differently under such conditions they are implemented faulty. No discussion about that ...
Maybe you're mixing things like "running under system account vs. running under a user account" ?