[jenkins 1.456] Can't acess security view
Hi everyone, I installed jenkins 1.456 and i'm getting a 404 error when i try to access http://jenkins-server/jenkins/configureSecurity or http://jenkins-server/configureSecurity So i tried to enable security by adding the following configuration true hudson.model.Computer.Configure:admin hudson.model.Computer.Delete:admin hudson.model.Hudson.Administer:admin hudson.model.Hudson.Read:admin hudson.model.Hudson.Read:anonymous hudson.model.Item.Build:admin hudson.model.Item.Configure:admin hudson.model.Item.Create:admin hudson.model.Item.Delete:admin hudson.model.Item.Read:admin hudson.model.Item.Read:anonymous hudson.model.Item.Workspace:admin hudson.model.Run.Delete:admin hudson.model.Run.Update:admin hudson.model.View.Configure:admin hudson.model.View.Create:admin hudson.model.View.Delete:admin hudson.scm.SCM.Tag:admin http://my-security-realm-server The security configuration worked, but i still can't access the security view in jenkins (from URLs or from Admin view) even with an administrator account. Does any one have a clue about this behaviour ? Thanks in advance. Regards, Raouf. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Can't launch 2 slaves (having two different masters) on the same machine
i was logged with another account (let's call it myAccount) however, when i shut down the slave from the jenkins nodes interface, it showed the previous message i never said i was running a different jar, i said i was running a different java process. do you have any documentation about jenkins slaves ? I'd like to know more about the default behaviour in that kind of situation 2013/10/4 Les Mikesell > On Fri, Oct 4, 2013 at 2:51 AM, Raouf wrote: > > Of course i'm using a specific account when using ssh, however, when i > > disconnect (with the same account logged in) a slave from jenkins's > > interface, i get "Disconnected by anonymous" displayed > > I think that refers to the user logged into the jenkins interface. > Did you log in and authenticate as some other user in the session > where you did the disconnect? > > > Concerning the FS, i was running the same version (1.456) for both > masters > > and slaves, and it always worked well since each one launches a > independent > > java process (some it doesn't matter whether they run from the same jar > or > > not) > > How is running a different jar possible? The server should > automatically download the current version of the jar files when > starting via ssh. > > > But when i moved to 1.518, it looks like there is some conflict (and i > > suspect the default port) when i launch two slaves, even with two > different > > masters > > I thought you said it only happens when you start with your custom ssh > script, not the internal ssh support. The ports used shouldn't > change. > > -- >Les Mikesell > lesmikes...@gmail.com > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/sP31OAOj9k0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Can't launch 2 slaves (having two different masters) on the same machine
Of course i'm using a specific account when using ssh, however, when i disconnect (with the same account logged in) a slave from jenkins's interface, i get "Disconnected by anonymous" displayed Concerning the FS, i was running the same version (1.456) for both masters and slaves, and it always worked well since each one launches a independent java process (some it doesn't matter whether they run from the same jar or not) But when i moved to 1.518, it looks like there is some conflict (and i suspect the default port) when i launch two slaves, even with two different masters Le jeudi 3 octobre 2013 22:24:27 UTC+2, LesMikesell a écrit : > > On Thu, Oct 3, 2013 at 1:52 PM, Raouf Abdelhamid > > wrote: > > when not specified, jenkins seems to use an account called anonymous to > > communicate with slaves > > That doesn't make any sense to me in the context of ssh which is going > to need a specific matching account as a login on the target node. > > > What's the problem with using the same file system ? can you explain > please > > ? > > Where do the slave jar, etc., and other supporting files live? Not to > mention the potential conflicts if you happen build the same job > concurrently. > > > ps: i'd like to remind you that it was working pretty well under 1.456, > so > > what has changed since then ? > > How many different versions of the slave.jar were you running then? > > -- > Les Mikesell > lesmi...@gmail.com > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Can't launch 2 slaves (having two different masters) on the same machine
when not specified, jenkins seems to use an account called anonymous to communicate with slaves What's the problem with using the same file system ? can you explain please ? ps: i'd like to remind you that it was working pretty well under 1.456, so what has changed since then ? 2013/10/3 Les Mikesell > On Thu, Oct 3, 2013 at 9:32 AM, Raouf wrote: > > By the way, i also noticed when using the built in ssh plugin, the slaves > > are launched by the anonymous account even if i created them with a > specific > > admin user. > > > > What is an anonymous account? > > And are you trying to run in the same FS root? I wouldn't expect > that to work at all, at least not concurrently. > > -- >Les Mikesell > lesmikes...@gmail.com > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/sP31OAOj9k0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Can't launch 2 slaves (having two different masters) on the same machine
By the way, i also noticed when using the built in ssh plugin, the slaves are launched by the anonymous account even if i created them with a specific admin user. Le jeudi 3 octobre 2013 10:26:11 UTC+2, Raouf a écrit : > > What i don't understand is that my scripts worked well when i was using > 1.456, i could use as many test slaves as i wanted without having conflicts > with the main slaves > > The issue occurs only since i moved my test instances to a 1.5xx version, > so i'd like to know what happened exactely, and how to get things back to > normal. > > Regards, > Raouf. > > Le mardi 1 octobre 2013 17:42:12 UTC+2, LesMikesell a écrit : >> >> On Tue, Oct 1, 2013 at 10:18 AM, Raouf Abdelhamid >> wrote: >> > Actually i did try it and it worked well. But i don't know exactly wich >> > slave jar was lanched, and i can't just abandon the scripts since >> they're >> > doing some other stuff (logging, restarting on fail ...etc.) >> >> The built in support should take care of getting the right jar in the >> right place for you - and probably doing everything else jenkins >> needs... >> >> In any case, I'd run under different users with different home >> directories so the jars and other files don't clobber each other. >> >> -- >>Les Mikesell >> lesmi...@gmail.com >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Can't launch 2 slaves (having two different masters) on the same machine
What i don't understand is that my scripts worked well when i was using 1.456, i could use as many test slaves as i wanted without having conflicts with the main slaves The issue occurs only since i moved my test instances to a 1.5xx version, so i'd like to know what happened exactely, and how to get things back to normal. Regards, Raouf. Le mardi 1 octobre 2013 17:42:12 UTC+2, LesMikesell a écrit : > > On Tue, Oct 1, 2013 at 10:18 AM, Raouf Abdelhamid > > wrote: > > Actually i did try it and it worked well. But i don't know exactly wich > > slave jar was lanched, and i can't just abandon the scripts since > they're > > doing some other stuff (logging, restarting on fail ...etc.) > > The built in support should take care of getting the right jar in the > right place for you - and probably doing everything else jenkins > needs... > > In any case, I'd run under different users with different home > directories so the jars and other files don't clobber each other. > > -- >Les Mikesell > lesmi...@gmail.com > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Can't launch 2 slaves (having two different masters) on the same machine
Actually i did try it and it worked well. But i don't know exactly wich
slave jar was lanched, and i can't just abandon the scripts since they're
doing some other stuff (logging, restarting on fail ...etc.)
2013/10/1 Les Mikesell
> On Tue, Oct 1, 2013 at 9:30 AM, Raouf wrote:
> > Hi everybody,
> >
> > Ii'm using two servers, one for jenkins master, and one for the slave
> > instance
> >
> > I'm using Jenkins 1.456 as a main stream version, and was trying to
> prepare
> > an upgrade to 1.518, so i just installed another jenkins master for
> testing
> > puropose, and defined different ports for each one (the main master and
> the
> > test master)
> >
> > then i added a slave node to the test-master, and i had already a slave
> node
> > for the main master.
> >
> > i launch each slave by calling a script through ssh, something like
> >
> > ssh me@my-slaves-server '/home/me/ slave_test.ksh start'
> >
> > and the script is calling slaves that way
> >
> > nohup /.../JAVA-6/bin/java -Xms512m -Xmx1024m -Djava.io.tmpdir=/tmp -jar
> > /.../hudson_slave/jar/${HUDSON_VERSION}/slave.jar -jnlpUrl
> > http://
> ${MASTER_HOST}:${MASTER_PORT}/computer/${SLAVE_HOST}/slave-agent.jnlp
> >
> > The problem is, each time i launch the test-slave the main-slave goes
> > offline and i have this stack trace
> >
> > ERROR: Unable to launch the slave agent for my-slaves-server
> > java.io.EOFException: unexpected stream termination
> > at hudson.remoting.Channel.(Channel.java:408)
> > at hudson.remoting.Channel.(Channel.java:366)
> > at hudson.remoting.Channel.(Channel.java:327)
> > at hudson.remoting.Channel.(Channel.java:323)
> > at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:313)
> > at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122)
> > at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200)
> > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> > at java.lang.Thread.run(Thread.java:662)
> >
> >
> >
> > Any ideas about this issue ?
>
> What happens if you use the built-in ssh support instead of your own
> script? And for testing, I'd start the slave as a different user for
> the 2nd instance.
>
> --
>Les Mikesell
> lesmikes...@gmail.com
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/sP31OAOj9k0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Can't launch 2 slaves (having two different masters) on the same machine
Hi everybody,
Ii'm using two servers, one for jenkins master, and one for the slave
instance
I'm using Jenkins 1.456 as a main stream version, and was trying to prepare
an upgrade to 1.518, so i just installed another jenkins master for testing
puropose, and defined different ports for each one (the main master and the
test master)
then i added a slave node to the test-master, and i had already a slave
node for the main master.
i launch each slave by calling a script through ssh, something like
ssh me@my-slaves-server '/home/me/ slave_test.ksh start'
and the script is calling slaves that way
nohup /.../JAVA-6/bin/java -Xms512m -Xmx1024m -Djava.io.tmpdir=/tmp -jar
/.../hudson_slave/jar/${HUDSON_VERSION}/slave.jar -jnlpUrl
http://${MASTER_HOST}:${MASTER_PORT}/computer/${SLAVE_HOST}/slave-agent.jnlp
The problem is, each time i launch the test-slave the main-slave goes
offline and i have this stack trace
ERROR: Unable to launch the slave agent for
my-slaves-serverjava.io.EOFException
<http://stacktrace.jenkins-ci.org/search?query=java.io.EOFException>:
unexpected stream termination
at hudson.remoting.Channel.(Channel.java:408)
<http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Channel.%3Cinit%3E&entity=method>
at hudson.remoting.Channel.(Channel.java:366)
<http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Channel.%3Cinit%3E&entity=method>
at hudson.remoting.Channel.(Channel.java:327)
<http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Channel.%3Cinit%3E&entity=method>
at hudson.remoting.Channel.(Channel.java:323)
<http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Channel.%3Cinit%3E&entity=method>
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:313)
<http://stacktrace.jenkins-ci.org/search/?query=hudson.slaves.SlaveComputer.setChannel&entity=method>
at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122)
<http://stacktrace.jenkins-ci.org/search/?query=hudson.slaves.CommandLauncher.launch&entity=method>
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200)
<http://stacktrace.jenkins-ci.org/search/?query=hudson.slaves.SlaveComputer$1.call&entity=method>
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
<http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.FutureTask$Sync.innerRun&entity=method>
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
<http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.FutureTask.run&entity=method>
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
<http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.ThreadPoolExecutor$Worker.runTask&entity=method>
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
<http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.ThreadPoolExecutor$Worker.run&entity=method>
at java.lang.Thread.run(Thread.java:662)
<http://stacktrace.jenkins-ci.org/search/?query=java.lang.Thread.run&entity=method>
Any ideas about this issue ?
Thanks in advance !
Regards,
Raouf.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: strange heap space
Many thanks ! that solved my problem. I was actually using the default HTTP wagon, so i moved to DAV wagon and now everythings is working fine. Thanks to everyone for your help. Regards, Raouf. 2013/7/19 Vincent Latombe > Hi, > > See [1] for a possible workaround (this is the one I use). Basically > when using maven 3, you just have to prefix your deployment url with > dav: (ex. dav:http://yourmavenserver). It will use the dav wagon > instead of the default http one, which has the bad habbit of loading > the full file in memory before sending it away. > > HTH, > > Vincent > > |1] > http://maven.40175.n5.nabble.com/Heap-overflow-in-deploy-deploy-td3211324.html > Vincent > > > 2013/7/19 Raouf Abdelhamid : > > Okay thanks guys, i'll check the activity of maven-deploy and give you > some > > feedback > > > > > > 2013/7/19 Daniel Beck > >> > >> IIRC a few years ago I experienced an issue with very large artifacts > >> being uploaded to an artifact repository. maven-deploy-plugin couldn't > >> handle files larger than one third of the available heap space. > >> > >> On 19.07.2013, at 12:09, Raouf wrote: > >> > >> > Hi there, > >> > > >> > I'm getting a java heap space that i can't really explain. i tried to > >> > increase the memory allocated to jenkins, but that doesn't change a > thing > >> > > >> > The most strange thing, is that i configured jenkins to not launch > sonar > >> > analysis if the build fails, but sonar analysis is launched anyway, > goes > >> > sucessful, and then the build is red ! > >> > > >> > I even tryied to montir the execution of this build with visual VM > >> > remotely connected to jenkins, but didn't see any heap space error at > any > >> > moment. > >> > > >> > here's the corresponding log > >> > > >> > Uploading: > >> > > http://server/archiva/repository/snapshot/project-SNAPSHOT/project-SNAPSHOT-bin.tar.gz > >> > > >> > [JENKINS] Archiving /basepath/hudson/workspace/ > >> > project/package/pom.xml to > >> > > /basepath/hudson/jobs/project/modules/package$module/builds/2013-07-18_14-08-50/archive/package/module/version-SNAPSHOT/module-version- > >> > SNAPSHOT.pom > >> > [JENKINS] Archiving /basepath/hudson/workspace/ > >> > project/package/targetproject-version-SNAPSHOT.jar to > >> > > /basepath/hudson/jobs/project/modules/package$module/builds/2013-07-18_14-08-50/archive/package/module/version-SNAPSHOT/project-version- > >> > SNAPSHOT.jar > >> > [JENKINS] Archiving /basepath/hudson/workspace/ > >> > project/package/target/project-version-SNAPSHOT-bin.tar.gz to > >> > > /basepath/hudson/jobs/project/modules/package$module/builds/2013-07-18_14-08-50/archive/package/module/version-SNAPSHOT/project-version- > >> > SNAPSHOT-bin.tar.gz > >> > [INFO] -- > >> > -- > >> > > >> > > >> > [ERROR] FATAL ERROR > >> > > >> > [INFO] > >> > > >> > [INFO] Java heap space > >> > [INFO] -- > >> > -- > >> > > >> > [INFO] Trace > >> > java.lang.OutOfMemoryError: Java heap space > >> > at java.util.Arrays.copyOf( > >> > Arrays.java:2786) > >> > at java.io.ByteArrayOutputStream. > >> > write(ByteArrayOutputStream. > >> > java:94) > >> > at sun.net.www.http. > >> > PosterOutputStream.write( > >> > PosterOutputStream.java:61) > >> > at org.apache.maven.wagon. > >> > AbstractWagon.transfer( > >> > AbstractWagon.java:338) > >> > at org.apache.maven.wagon. > >> > AbstractWagon.transfer( > >> > AbstractWagon.java:305) > >> > at org.apache.maven.wagon. > >> > AbstractWagon.transfer( > >> > AbstractWagon.java:267) > >> > at org.apache.maven.wagon. > >> > AbstractWagon.putTransfer( > >> > AbstractWagon.java:238) > >> > at org.apache.maven.wagon. > >> > StreamWagon.put(StreamWagon. > >> > java:143) > >> >
Re: strange heap space
Okay thanks guys, i'll check the activity of maven-deploy and give you some feedback 2013/7/19 Daniel Beck > IIRC a few years ago I experienced an issue with very large artifacts > being uploaded to an artifact repository. maven-deploy-plugin couldn't > handle files larger than one third of the available heap space. > > On 19.07.2013, at 12:09, Raouf wrote: > > > Hi there, > > > > I'm getting a java heap space that i can't really explain. i tried to > increase the memory allocated to jenkins, but that doesn't change a thing > > > > The most strange thing, is that i configured jenkins to not launch sonar > analysis if the build fails, but sonar analysis is launched anyway, goes > sucessful, and then the build is red ! > > > > I even tryied to montir the execution of this build with visual VM > remotely connected to jenkins, but didn't see any heap space error at any > moment. > > > > here's the corresponding log > > > > Uploading: > http://server/archiva/repository/snapshot/project-SNAPSHOT/project-SNAPSHOT-bin.tar.gz > > > > [JENKINS] Archiving /basepath/hudson/workspace/ > > project/package/pom.xml to > /basepath/hudson/jobs/project/modules/package$module/builds/2013-07-18_14-08-50/archive/package/module/version-SNAPSHOT/module-version- > > SNAPSHOT.pom > > [JENKINS] Archiving /basepath/hudson/workspace/ > > project/package/targetproject-version-SNAPSHOT.jar to > /basepath/hudson/jobs/project/modules/package$module/builds/2013-07-18_14-08-50/archive/package/module/version-SNAPSHOT/project-version- > > SNAPSHOT.jar > > [JENKINS] Archiving /basepath/hudson/workspace/ > > project/package/target/project-version-SNAPSHOT-bin.tar.gz to > /basepath/hudson/jobs/project/modules/package$module/builds/2013-07-18_14-08-50/archive/package/module/version-SNAPSHOT/project-version- > > SNAPSHOT-bin.tar.gz > > [INFO] -- > > -- > > > > > > [ERROR] FATAL ERROR > > > > [INFO] > > > > [INFO] Java heap space > > [INFO] -- > > -- > > > > [INFO] Trace > > java.lang.OutOfMemoryError: Java heap space > > at java.util.Arrays.copyOf( > > Arrays.java:2786) > > at java.io.ByteArrayOutputStream. > > write(ByteArrayOutputStream. > > java:94) > > at sun.net.www.http. > > PosterOutputStream.write( > > PosterOutputStream.java:61) > > at org.apache.maven.wagon. > > AbstractWagon.transfer( > > AbstractWagon.java:338) > > at org.apache.maven.wagon. > > AbstractWagon.transfer( > > AbstractWagon.java:305) > > at org.apache.maven.wagon. > > AbstractWagon.transfer( > > AbstractWagon.java:267) > > at org.apache.maven.wagon. > > AbstractWagon.putTransfer( > > AbstractWagon.java:238) > > at org.apache.maven.wagon. > > StreamWagon.put(StreamWagon. > > java:143) > > at org.apache.maven.wagon. > > providers.http.LightweightHttpWagon.put( > > LightweightHttpWagon.java:148) > > at org.apache.maven.artifact. > > manager.DefaultWagonManager.putRemoteFile( > > DefaultWagonManager.java:244) > > at org.apache.maven.artifact. > > manager.DefaultWagonManager.putArtifact( > > DefaultWagonManager.java:160) > > at org.apache.maven.artifact. > > deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java: > > 80) > > at org.apache.maven.plugin. > > deploy.DeployMojo.execute( > > DeployMojo.java:169) > > at org.apache.maven.plugin. > > DefaultPluginManager.executeMojo( > > DefaultPluginManager.java:451) > > at hudson.maven.agent. > > PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java: > > 182) > > at org.apache.maven.lifecycle. > > DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: > > 558) > > at org.apache.maven.lifecycle. > > > DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java: > > 499) > > at org.apache.maven.lifecycle. > > DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: > > 478) > > at org.apache.maven.lifecycle. > > > DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java: > > 330) > > at org.apache.maven.lifecycle. > > > DefaultLifecycleExecutor.
strange heap space
] Final Memory: 352M/995M [INFO] Waiting for Jenkins to finish collecting data channel stopped ... [INFO] Building PROJECT [INFO]task-segment: [org.codehaus.mojo:sonar-maven-plugin:1.0:sonar] (aggregator-style) [INFO] [INFO] [sonar:sonar] [INFO] Sonar host: http://vd2260:20506 [INFO] Sonar version: 2.9 [INFO] Execute: org.codehaus.sonar:sonar-maven-plugin:2.9:sonar [INFO] [sonar:sonar] . at the end of sonar analysis [INFO] Database optimization done: 15599 ms [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 8 minutes 25 seconds [INFO] Finished at: Thu Jul 18 14:28:04 CEST 2013 [INFO] Final Memory: 93M/733M [INFO] Finished: FAILURE Thanks in advance for your help ! Regards, Raouf. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
