Hello,
I'm running a Jenkins master which should use different projects and
different user groups. The authentification is used a LDAP but the LDAP
groups should not be used for Jenkins.
I'm testing
the https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin plugin
to create roles wit
On 15.03.2014, at 13:33, Markus KARG wrote:
> Update: I have manually downloaded and installed the very same JDKs at the
> same location without any problem. So it is definitively a bug in Jenkins.
Did you install them using the same silent install, suppress reboot, etc.
command line?
Is the
Update: I have *manually *downloaded and installed the very same JDKs at
the same location without any problem. So it is definitively a bug in
Jenkins.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop re
I see. The problem definitively only happens with the "Windows server"
launch method. JNLP agent is working well, even when installed as a service
itself.
Am Samstag, 15. März 2014 08:27:06 UTC+1 schrieb Richard Bywater:
>
> I think Daniel is trying to help ascertain whether the problem is just
I am writing a jenkins plugin. In the plugin I have a class that extends
Builder which has a method that checks if a given project is a
MavenModuleSet:
if (workerProject instanceof MavenModuleSet) {
MavenModuleSet mavenModuleSet = (MavenModuleSet) workerProject;
mavenModuleSet.se
I think Daniel is trying to help ascertain whether the problem is just with
the "Windows service" launch method or all the launch methods in a bid to
try and track down where the problem may lie.
Richard.
On Sat, Mar 15, 2014 at 8:21 PM, Markus KARG wrote:
> It is rather obvious that the messa
It is rather obvious that the message does not appear for JNLP slaves. But
what does that help? I don't want to use JNLP.
Am Samstag, 15. März 2014 01:11:10 UTC+1 schrieb Daniel Beck:
>
>
> On 14.03.2014, at 23:52, Markus KARG >
> wrote:
>
> > at
> hudson.os.windows.ManagedWindowsServi
