Re: Ansible plugin 0.6 release date

[jcsirot]

Hi Laurent,

Sorry for the inconvenience :-( Since a couple of weeks I've started to 
integrate the github PR and I'm very close to release the 0.6 version. 
Unfortunately I am alone working on the plugin and I have to do it on my 
free time therefore the development is not as fast as I wish. However I'm 
sure I will release the 0.6 version before the end of December.

Best Regard

-- 
Jean-Christophe

Le vendredi 2 décembre 2016 02:49:32 UTC+1, Laurent Goujon a écrit :
>
> Hi,
>
> I'm also impacted by the ansible plugin issue where current environment is 
> not respected (https://issues.jenkins-ci.org/browse/JENKINS-38289), and I 
> was wondering when the next version of the plugin with the fix would be 
> released.
>
> Thanks in advance,
>
> Laurent
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7b520a6f-3b9e-463e-a98c-ba4a80d4b024%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ansible plugin problem in pipeline code

[jcsirot]

Hello Guy,

Do not hesitate to open a JIRA ticket with the ansible-plugin component:

https://issues.jenkins-ci.org/issues/?jql=project%20%3D%20JENKINS%20AND%20component%20%3D%20ansible-plugin

I'm going to look at this issue to understand what's going on.

-- 
Jean-Christophe

Le lundi 28 novembre 2016 20:42:10 UTC+1, Guy Knights a écrit :
>
> I'm trying to use the ansible plugin in a pipeline script, but it fails to 
> find ansible-playbook. I've used the "ansibleName" parameter to supply the 
> name of the Ansible version I want to use from Jenkins' global tool config 
> page, but it still fails. I get the following when trying to execute a 
> playbook from a pipeline:
>
> [workspace] $ ansible-playbook 
>> /opt/ansible-data/playbooks/client_deploy.yml -i 
>> /opt/ansible-data/inventory/prod/ -f 5 --private-key 
>> "/var/jenkins_home/jobs/Default/jobs/Client 
>> deploy/workspace/ssh7766033036773514652.key" -u ubuntu -e wl_name=default 
>> -e client_version=761c6f24
>>
>> FATAL: command execution failed
>> java.io.IOException: Cannot run program "ansible-playbook" (in directory 
>> "/var/jenkins_home/jobs/Default/jobs/Client deploy/workspace"): error=2, No 
>> such file or directory
>>
>>
> The path to the ansible binaries has been defined in the global config 
> page as /opt/ansible/ansible-2.2/bin, and this works for normal jenkins 
> (ie. not pipeline) jobs, using the "Invoke Ansible playbook" build task.
>
> The ansible call from my Jenkinsfile is as follows:
>
> ansiblePlaybook(
> ansibleName: 'stable-2.2',
> playbook: "${ANSIBLE_DATA_PATH}/playbooks/client_deploy.yml",
> inventory: "${ANSIBLE_DATA_PATH}/inventory/${ENVIRONMENT}/",
> credentialsId: '574fb47c-33df-4096-bd0c-0c44962b2546',
> extraVars: [
> wl_name: "${wlName}",
> client_version: "${gtpCommitId}"
> ],
> additionalParameters: '--vault-password-file 
> "/var/jenkins_home/.ansible/vault.pwd" --forks=10',
> colorized: true
> ) 
>
> "stable-2.2" is the name I've given to the version of Ansible defined on 
> the global tools config page.
>
> Does anyone know why this isn't working?
>
> Thanks,
> Guy
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ca90ac96-201d-4877-97ae-14a80b05226e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins ssh-agent ansible

[jcsirot]

Hello,

Ansible is launched as a subprocess of Jenkins server and is therefore 
using the same user. However I'm not really familiar with ssh-agent. I'm 
going to try to reproduce this issue and see if there is something I can do 
in the plugin code to help you.

Regards,

-- 
Jean-Christophe

Le mercredi 26 octobre 2016 20:16:37 UTC+2, AC a écrit :
>
> Hello,
>
> I have Ansible installed on my Jenkins master. The Jenkins Ansible plugin 
> was working and completing jobs until I switched over to using ssh-agent to 
> encrypt my private key. However, I can still run Ansible commands from the 
> Jenskins Master CLI but not from the Jenkins Ansible Plugin.
>
> Does Jenkins not run the jobs as the Jenkins user which has ssh-agent 
> running? Does anyone know if there is a way to do this?
>
> Thanks!
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4491ccff-697f-4293-8ac8-a070c93ae246%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accessing build environment variables from Playbook using Ansible Plugin

[jcsirot]

Hello,

Yes, the variables are available as env vars inside the process running 
ansible. If you want to access these env vars within an ansible playbook 
you should use the lookup plugin as showed here in the ansible 
FAQ: 
http://docs.ansible.com/ansible/faq.html#how-do-i-access-shell-environment-variables

You should then adapt your playbook (I tested and it works for me)

---
- hosts: all
  tasks:
- command: echo "{{ lookup('env','PATH') }}"
  register: default_path
- command: echo "{{ lookup('env','WORKSPACE') }}"
  register: jenkins_job_workspace

Hope it helps.

Le mardi 12 juillet 2016 18:15:47 UTC+2, Ricardo Hernandez a écrit :
>
> Hi,
>
> Starting from version 0.5 of the Ansible Plugin the build environment 
> variables are available during ansible execution. 
> I'm currently trying to get the job workspace path inside my playbook 
> (which I provide using job DSL) the following way:
>
> ---
> - hosts: all
>   tasks:
> - command: echo "$PATH"
>   register: default_path
> - command: echo "$WORKSPACE"
>   register: jenkins_job_workspace
>
>
> However, WORKSPACE doesn't seem to be defined, as shown in the output:
>
> TASK [command] 
> * 
> changed: [10.100.198.9] => {"changed": true, "cmd": ["echo", "$PATH"], 
> "delta": "0:00:00.002428", "end": "2016-07-12 10:49:02.252685", "rc": 0, 
> "start": "2016-07-12 10:49:02.250257", "stderr": "", "stdout": 
> "/usr/local/bin:/usr/bin", "stdout_lines": ["/usr/local/bin:/usr/bin"], 
> "warnings": []} 
> TASK [command] 
> * 
> changed: [10.100.198.9] => {"changed": true, "cmd": ["echo", "$WORKSPACE"], 
> "delta": "0:00:00.002479", "end": "2016-07-12 10:49:02.470880", "rc": 0, 
> "start": "2016-07-12 10:49:02.468401", "stderr": "", "stdout": "$WORKSPACE", 
> "stdout_lines": ["$WORKSPACE"], "warnings": []}
>
> Is this the correct way to access them?
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a79544db-0b9a-4d59-a03e-0aca1fc05f99%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Failed to connect to the host via ssh

[jcsirot]

Hello,

Is the host ssh key installed in the $HOME/.ssh dicrectory of the jenkins 
user?

-- 
Jean-Christophe

Le vendredi 8 juillet 2016 08:08:25 UTC+2, haza...@gmail.com a écrit :
>
> Hi ,
>
> I have installed Jenkins on AWS EC2 instance. I have created Maven Project 
> and added the settings to run "Ansibe Playbook" in post-builds section of 
> Jenkins.
>
> While Jenkins executing the "ansible-playbook" im getting the below error.
>
> [workspace] $ ansible-playbook /home/ubuntu/playbooks/petclinic.yml -i 
> /etc/ansible/hosts -s -U root -f 5
>
> PLAY [MavenServers] 
> 
>
> TASK [setup] 
> ***
> fatal: [54.169.xx.xx]: UNREACHABLE! => {"changed": false, "msg": "Failed to 
> connect to the host via ssh.", "unreachable": true}
>  [ERROR]: Could not create retry file 
> '/home/ubuntu/playbooks/petclinic.retry'.
> The error was: [Errno 13] Permission denied:
> '/home/ubuntu/playbooks/petclinic.retry'
>
> PLAY RECAP 
> *
> 54.169.xx.xx   : ok=0changed=0unreachable=1failed=0   
>
>
> Please help me.
>
>
> Thanks in advance.
>
>
> --Hazar.
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/32a4faa8-1438-41b6-b9d0-11332ab049ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ansible-plugin

[jcsirot]

Hi Ivan,

When using "inline content" for inventory Jenkins creates a temporary file. 
The dynamic inventory checkbox is used to indicate if the executable flag 
of that file must be set. This is how ansible distinguishes regular and 
dynamic inventories.

Can you post here the error from the console log?

Regards,

-- 
Jean-Christophe 

Le lundi 14 mars 2016 17:43:55 UTC+1, ivan farre Vicente a écrit :
>
> Hi,
>
> Anyone has experience using this plugin. We have troubles in order to 
> achive use dynamic inventories with AWS.
>
> I will apreciate If anyone give us some explanation about how we should 
> use this feature. I don't know how we should fill the 'content' box if i 
> check "Dynamic Inventory" check box.
>
> Many thanks
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b0657148-f476-481b-99a3-7a2e817f9831%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How do I get the Ansible plugin to work with Jenkins?

[jcsirot]

Hi Kiran,

The jenkins is not able to remotely execute the ansible command. The 
installation field in the global configuration must contain the path of the 
directory where the ansible binaries are installed. Note that in the last 
release of the plugin this configuration is not required anymore when 
ansible is available in the PATH environment variable.

There are two possible solutions: either you install ansible on your 
Jenkins server or you setup your Ansible server as a Jenkins slave.

Hope this helps.

-- 
Jean-Christophe

Le mercredi 3 février 2016 02:46:33 UTC+1, Kiran a écrit :
>
> My Ansible (version 1.9.5) server is on its own dedicated CentOS 7 
> server.  My Jenkins (version 1.6) server is on its own dedicated CentOS 7 
> server.  I installed the Ansible plugin for Jenkins.  I created a New Item 
> that invokes an ad-hoc Ansible command.  For the Ansible Installation 
> field, I enter the DNS name of the Ansible server.  For host pattern, I 
> chose the group of servers that I want the Ansible playbook to run again.  
> The group name was defined in the .../ansible/hosts file.
>
> The console output of this new Jenkins job that should invoke an ansible 
> command (on a separate server with Ansible installed) says this:
>
> "Building in workspace /var/lib/jenkins/jobs/... $ sshpass ** /ansible 
> ... DNSnameOfAnsibleServer -i ... FATAL: command execution failed 
> hudson.AbortException: Ansible Ad-Hoc command execution failed at 
> org.jenkinsci.plugins.ansible.AnsibleAdHocCommandBuilder.perform(AnsibleAdHocCommandBuilder.java:176
>  
> at ..."
>
> Does the Ansible server need sshpass? The Jenkins server has sshpass.
>
> How do I get Jenkins to invoke an ansible playbook on an Ansible server?  
> This error makes me think that something is wrong with sshpass.  I can view 
> the man page of sshpass.  Is there a certain version that I need?
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/355e9637-710d-475c-a7ea-e729bb6a597d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Get Jenkins Working with Private Repo

[jcsirot]

I faced the same issue and I decided to recompile the git plugin (actually 
the git-client plugin which is a dependency of the git plugin) with the 
patch submited in that Pull Request: 
https://github.com/jenkinsci/git-client-plugin/pull/180/files (Note I'm not 
the author of this patch)

It handles the single sub-case where all git submodules are using the same 
credentials (and this is probably why it has not been merged yet) but it 
works for me.

-- 
JC

Le lundi 24 août 2015 21:45:38 UTC+2, Pratik Dhandharia a écrit :
>
> Hi All,
>
> I am comparatively new to Jenkins and I am trying to troubleshoot a 
> Jenkins issue where we are trying to fetch a public repository which has 
> multiple private sub-modules. It is due to legal reasons we cannot keep the 
> private sub-modules public.
>
> So I have most of the plugin's installed in Jenkins. I have configured 
> Jenkins to store the jenkins user credential using the credential plugin. 
>
> What I am really trying to do is, fetching the private sub-modules using 
> credentials (username and password). I don't want to switch to using SSH 
> key of the jenkins user for pulling the private sub-modules. And here is 
> the error that I get:
>
>  > /usr/bin/git submodule sync # timeout=10
>  > /usr/bin/git config --get remote.origin.url # timeout=10
>  > /usr/bin/git submodule update --init --recursive
> FATAL: Command "/usr/bin/git submodule update --init --recursive" returned 
> status code 1:
> stdout: 
> stderr: fatal: Authentication failed
> Unable to fetch in submodule path
>
>
> Can someone please help point out if the Jenkins Git Client Plugin, work 
> with fetching private repositories using credentials(username and password)?
>
> Thanks
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6d414fb4-ddc5-443c-bda5-d34dfa08d5cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Strange slave provisioning behavior

[jcsirot]

Hi!

On my Jenkins instance I am using the docker plugin in order to spawn 
slaves on demand. In the docker cloud configuration, each image is bound to 
a label and every job is also configured with a label indicating the docker 
image it requires. On this instance I set the master executor count to 0 
and therefore I do not have any "permanent" executor. Moreover I do not 
have any unlabeled slave.

And now I have this unexpected behavior: when I start a job, two docker 
containers are started. According to the log hereunder, the first container 
is provisioned for the label "null" and the second container is provisioned 
for the label "wheezy64" (which is what I want since the job is actually 
configured with that label).

Mar 13, 2015 10:07:04 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud 
provision

Asked to provision 1 slave(s) for: null

Mar 13, 2015 10:07:04 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud 
provision

Will provision "jenkins:wheezy" for: null

Mar 13, 2015 10:07:04 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud 
addProvisionedSlave

Provisioning "jenkins:wheezy" number 0 on "docker.adm.qa.arkena.com"; Total 
containers: 0

Mar 13, 2015 10:07:04 AM FINE com.nirima.jenkins.plugins.docker.DockerTemplate

Launching jenkins:wheezy

Mar 13, 2015 10:07:04 AM FINE 
com.nirima.jenkins.plugins.docker.DockerTemplateBase

Provisioning new container for image jenkins:wheezy

Mar 13, 2015 10:07:04 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud 
provision

Asked to provision 1 slave(s) for: wheezy64

Mar 13, 2015 10:07:04 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud 
provision

Will provision "jenkins:wheezy" for: wheezy64

Mar 13, 2015 10:07:05 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud 
addProvisionedSlave

Provisioning "jenkins:wheezy" number 1 on "docker.adm.qa.arkena.com"; Total 
containers: 1

Mar 13, 2015 10:07:05 AM FINE com.nirima.jenkins.plugins.docker.DockerTemplate

Launching jenkins:wheezy



When i configure an unlabeled executor on the master the first provisioning 
request is never launched.

Is this a bug (and in that case I will open a Jira ticket) or did I miss 
something?

Thanks in advance.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f1c876ac-1ab5-4915-bd66-a0f42d9cab48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

NoClassDefFoundError: hudson.maven.reporters.MavenAbstractArtifactRecord

[jcsirot]

Hello,


I upgraded my Jenkins server from 1.509.2 to 1.509.3 but for each maven job I 
have this error when the artifacts are archived. This stacktrace is printed 
multiple times.


ERROR: Asynchronous execution failurejava.util.concurrent.ExecutionException 
:
 java.lang.NoClassDefFoundError: 
hudson.maven.reporters.MavenAbstractArtifactRecord
at hudson.remoting.Channel$4.adapt(Channel.java:705) 

at hudson.remoting.Channel$4.adapt(Channel.java:700) 

at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) 

at 
hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:185)
 

at hudson.maven.Maven3Builder.call(Maven3Builder.java:105) 

at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) 

at hudson.remoting.UserRequest.perform(UserRequest.java:118) 

at hudson.remoting.UserRequest.perform(UserRequest.java:48) 

at hudson.remoting.Request$2.run(Request.java:326) 

at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 

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:619) 

Caused by: java.lang.NoClassDefFoundError 
: 
hudson.maven.reporters.MavenAbstractArtifactRecord
at 
hudson.maven.reporters.MavenArtifactArchiver$2.call(MavenArtifactArchiver.java:138)
 

at 
hudson.maven.reporters.MavenArtifactArchiver$2.call(MavenArtifactArchiver.java:129)
 

at hudson.maven.MavenBuild$ProxyImpl.execute(MavenBuild.java:404) 

at hudson.maven.MavenBuild$ProxyImpl2.execute(MavenBuild.java:477) 

at sun.reflect.GeneratedMethodAccessor691.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at hudson.model.Executor$1.call(Executor.java:543)
at hudson.util.InterceptingProxy$1.invoke(InterceptingProxy.java:23)
at $Proxy82.execute(Unknown Source)
at 
hudson.maven.MavenBuildProxy$Filter$AsyncInvoker.call(MavenBuildProxy.java:270)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurr

Re: [1.509.1 LTS] Massive performance issues

[jcsirot]

Hello Steffen, 

Yes, I'm facing the same hanging issue. It seems that it appeared with the 
patch providing the lazy-loading build data (around 1.485). Like you I 
tried to look for the reason but I don't have much time to spend on this 
issue.

7 month ago, I opened a JIRA ticket 
https://issues.jenkins-ci.org/browse/JENKINS-15601. Unresolved so far :(

-- 
Jean-Christophe

Le jeudi 16 mai 2013 10:50:02 UTC+2, Steffen a écrit :
>
> Hi everyone!
>
> After updating to 1.509.1 LTS (from 1.480.3) we're facing massive 
> performance issues. Performance was OK before, but now loading pages takes 
> significantly longer than before. Certain jobs also have a way longer 
> runtime than before.
>
> Sometimes, Jenkins even won't respond any more. We're using Tomcat 6.0.36 
> as container. Tomcat itself still was responsive, but Jenkins was hanging 
> for about 10 minutes. This occurred twice so far. When this happens, load 
> and I/O on the machine itself are low, so we don't suspect issues with the 
> machine or the OS itself. There isn't something of significance in the 
> logs, either.
>
> We tried to get to the bottom of this issue, but we weren't successful 
> yet. Monitoring the JVM or the OS didn't bring up anything.
>
> Anyone noticed a similar behaviour yet?
>
> Regards
>   Steffen
>

-- 
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 start slaves anymore, ssh auth failing

[jcsirot]

You should also take a look at the tool locations on your slaves. My 
configurations were messed up with, for instance, maven configured with the 
JDK path and so on.

Le jeudi 2 mai 2013 17:43:09 UTC+2, CHAVANNE Robert a écrit :
>
> Hello Eric, 
> We had the same kind of problem. 
> I think you should take a look at "manage Credentials" in manage Jenkins. 
> We had to create credential to fix the issue. 
> I hope it can help. 
>
> Regards, 
> Robert 
>
>
>
>

-- 
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: Using subversion on a Mac OS X slave

[jcsirot]

Nice to see that this issue has been solved :-)

-- 
Jean-Christophe 

Le mardi 5 mars 2013 01:12:33 UTC+1, Stuart Whelan a écrit :
>
> Many thanks to Kutzi for the assistance in solving this problem: 
>
> There was an old svnkit-1.3.6.1-jenkins-2.jar in C:\Program Files 
> (x86)\Jenkins\plugins\subversion\WEB-INF\lib 
>
> Shutting down jenkins and deleting this file solved the issue. 
>
> Cheers! 
>
> On Tue, Mar 5, 2013 at 9:26 AM, Stuart Whelan 
> > wrote: 
> > I just set up a new repository, on another machine, using svnserve and 
> > no authentication. 
> > 
> > It failed with exactly the same problem. 
> > 
> > On Tue, Mar 5, 2013 at 8:52 AM, Stuart Whelan 
> > > wrote: 
> >> I can now report that I am getting the exact same error when using 
> >> subversion 1.6.17 on Ubuntu. 
> >> 
> >> On Tue, Mar 5, 2013 at 8:41 AM, Stuart Whelan 
> >> > wrote: 
> >>> Hi Jean-Christophe, 
> >>> 
> >>> Thanks you for looking at my issue, I appreciate it! 
> >>> 
> >>> I am using 1.45 of the Jenkins Subversion Plug-in, but I have also 
> >>> previously tried 1.44. 
> >>> 
> >>> The OSX and subversion project is the first OSX and first subversion 
> >>> project we have tried to migrate from CCNET, so I am unable to say if 
> >>> it works anywhere else. 
> >>> 
> >>> I have a ubuntu machine I will put subversion on just to see if it 
> works there. 
> >>> 
> >>> All my other projects are Windows with Source Gear Vault, or 
> Mercurial. 
> >>> 
> >>> Thanks again, 
> >>> Stuart. 
> >>> 
> >>> 
> >>> 
> >>> On Mon, Mar 4, 2013 at 11:24 PM, jcsirot > 
> wrote: 
> >>>> 
> >>>> Hello Stuart, 
> >>>> 
> >>>> What is your Jenkins and subversion plugin version ? Does this error 
> occurred only on an OSX slave? 
> >>>> 
> >>>> -- 
> >>>> Jean-Christophe 
>

-- 
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: Using subversion on a Mac OS X slave

[jcsirot]

Hello Stuart,

What is your Jenkins and subversion plugin version ? Does this error 
occurred only on an OSX slave?  

-- 
Jean-Christophe

Le mercredi 27 février 2013 20:52:40 UTC+1, Stuart Whelan a écrit :
>
> Hi Folks,
>
> I have a jenkins slave running OS X running subversion.
>
> When I try and checkout or update using the the jenkins subversion plugin.
>
> I can do a checkout manually, and am running the slave as the same user as 
> I did the test manual checkout.
>
> Can any suggest a next course of action?
>
> Building remotely on Mac OS Test Node 
>  in 
> workspace /Users/buildmachine/jenkins/xcode
> hudson.util.IOException2: remote file operation failed: 
> /Users/buildmachine/jenkins/xcode at hudson.remoting.Channel@1695eeb:Mac OS 
> Test Node
>   at hudson.FilePath.act(FilePath.java:861)
>   at hudson.FilePath.act(FilePath.java:838)
>   at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843)
>   at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781)
>   at hudson.model.AbstractProject.checkout(AbstractProject.java:1342)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683)
>   at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588)
>   at hudson.model.Run.execute(Run.java:1568)
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
>   at hudson.model.ResourceController.execute(ResourceController.java:88)
>   at hudson.model.Executor.run(Executor.java:237)
> Caused by: java.io.IOException: Remote call on Mac OS Test Node failed
>   at hudson.remoting.Channel.call(Channel.java:681)
>   at hudson.FilePath.act(FilePath.java:854)
>   ... 11 more
> Caused by: java.lang.NoSuchMethodError: 
> org.tmatesoft.svn.core.wc.SVNBasicClient.getOperationsFactory()Lorg/tmatesoft/svn/core/wc2/SvnOperationFactory;
>   at hudson.scm.SvnClientManager.wrapUp(SvnClientManager.java:46)
>   at hudson.scm.SvnClientManager.getUpdateClient(SvnClientManager.java:67)
>   at 
> hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:71)
>   at 
> hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153)
>   at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903)
>   at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884)
>   at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867)
>   at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348)
>   at hudson.remoting.UserRequest.perform(UserRequest.java:118)
>   at hudson.remoting.UserRequest.perform(UserRequest.java:48)
>   at hudson.remoting.Request$2.run(Request.java:326)
>   at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>   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:680)
> Finished: FAILURE
>
>

-- 
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: How to configure Linux Jenkins as not anonymous

[jcsirot]

Hello Michael,

You should have an "/etc/default/jenkins" file where are defined the 
Jenkins service configuration variables. I configured the JENKINS_USER and 
JENKINS_HOME in this file.

Regards
-- 
Jean-Christophe


Le mardi 26 février 2013 18:40:32 UTC+1, mwpowellhtx a écrit :
>
> Hello, I am sure this question has been asked in different forms before, 
> having some difficulty connecting the dots.
>
> I've got Jenkins more of the way installed, some owner and permissions 
> issues on a jenkins account better understood and resolved.
>
> I can now clone repositories on the command prompt using the jenkins 
> account. That's step one. Now I want to configure Jenkins service to run 
> not as the anonymous user but rather as the jenkins account.
>
> However, it's running as anonymous, trying to work with /var/lib, etc, 
> path to workspace. I want that workspace under the user's home directory 
> instead.
>
> I've been reading bits and pieces how to configure my jenkins start 
> command in a service environment, what configuration files to convey 
> running as the user name, but need a pointer to better understand and 
> resolve it.
>
> Regards,
>
> Michael
>

-- 
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: Setup Jenkins slave on another machine

[jcsirot]

For a windows slave I installed the jenkins slave as a windows service 
through the JNLP installer. The following links gives all details about 
this kind of installation:

https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice%28require.NET2.0framework%29

-- 
JC

Le jeudi 28 février 2013 11:17:13 UTC+1, Madhu a écrit :
>
> Hi All,
>
> I am trying to configure Jenkins. I configured one slave on my local 
> machine,I am able to run web driver scripts in master and slave (on same 
> machine). I am using Windows 7.
> Now, I want to set up slave in another machine which is connected to LAN. 
> Can anyone tell me what are the steps to set up slave in another machine 
> which is in LAN.
> My intention is to run scripts in master machine as well as slave machine 
> (another machine) .
>
>
> Thanks,
> Madhavi
>

-- 
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: jenkins/winstone running under https

[jcsirot]

Hello David;

As far as I known the JKS keystore format maintain a link between private 
keys and certificate chains. Maybe, when you imported your certificate, the 
link between the key and the previously created self-signed certificate was 
not updated. What does the command "keytool -list -v -keystore 
myKeyStore.jks" return?

To create a new keystore containing only the key and the CA signed 
certificate (and maybe additional sub-CA certificates if required) you 
should:

1. export you keystore the PKCS12 format:
keytool -importkeystore -srckeystore myKeyStore.keystore -destkeystore 
myKeyStore.p12 -deststoretype PKCS12 -srcstorepass myPassword 
-deststorepass myPassword

2. extract the key in PKCS8 format with openssl:
openssl pkcs12 -in myKeyStore.p12 -nodes

The private key in encoded with PEM (base64) starts with -BEGIN RSA 
PRIVATE KEY- and ends with -END RSA PRIVATE KEY-

3. create a new PKCS12 file with openssl

openssl pkcs12 -export -in jenkins-cert.pem -inkey jenkins-key.pem 
-name "friendly name" -out jenkins.p12


Optionally (I'm not sure whether Jenkins accepts PKCS12 encoded keystores) 
you can re-encode this PKCS12 file into JKS format with the 
"importkeystore" keytool command.

Hope this helps

-- 
JC

Le mardi 26 février 2013 09:14:38 UTC+1, David Doughty a écrit :
>
> hi JC,
>
> I created the keystore with the self certified key a couple of weeks ago 
> when I installed jenkins, and then generated a CSR. The root/intermediate 
> and private key for the machine have been loaded into the same keystore.
>
> Jenkins is currently started with the following command
>
> java $JAVA_OPTS -jar $JENKINS_HOME/jenkins.war --prefix=$JENKINS_PREFIX 
>  --controlPort=$JENKINS_CONTROL_PORT --httpPort=$JENKINS_HTTP_PORT 
> --ajp13Port=$JENKINS_AJP_PORT --httpsPort=$JENKINS_HTTPS_PORT 
> --httpsKeyStore=$KEYSTORE --httpsKeyStorePassword=$KEYSTORE_PASSWORD 
> --logfile=$LOGFILE &
>
> the variables are set as
>
> export JENKINS_PREFIX="/jenkins"
> export JENKINS_HOST="gbrpsr00408"
> export JENKINS_CONTROL_PORT="8001"
> export JENKINS_HTTP_PORT="-1"
> export JENKINS_HTTPS_PORT=8444
> export KEYSTORE=/opt/jenkins/keystore/scmrm.jks
> export KEYSTORE_PASSWORD="Key\$t0re"
> export JENKINS_AJP_PORT="-1"
> export LOGFILE=$JENKINS_HOME/logs/access_`date +"%Y%m-%d"`.log
> export JAVA_OPTS="-Djava.awt.headless=true -XX:PermSize=512M 
> -XX:MaxPermSize=2048M -Xmn128M -Xms1024M -Xmx2048M"
>
>
>
>
>
> On Monday, 25 February 2013 17:20:49 UTC, jcsirot wrote:
>>
>> Hello David, 
>>
>> Can you give us more details on how you installed your keystore? Did you 
>> have a single keystore containing both self-signed and CA issued 
>> certificates? What params did you pass to Jenkins at start-up?
>>
>> -- 
>> JC
>>
>> Le lundi 25 février 2013 17:11:24 UTC+1, David Doughty a écrit :
>>>
>>> I've beening running jenkins 1.466.12.1 as jenkins on RHEL6.2 (we don't 
>>> have root access), under https for a few weeks now, using a self signed 
>>> certificate, no problems, other than than the issues for end users and 
>>> their browsers. We have now been issued an offical certificate CA chain 
>>> root-intermediate-server from our security team.
>>>
>>> Now the fun begins...
>>>
>>> At the moment I don't seem to be able to get Jenkins to recognize the 
>>> official certificates at all; it only appears to start up with a keystore 
>>> with the self signed certificate present, which is the only certificate 
>>> presented to the client browser.
>>>
>>>
>>> https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins< 
>>> at the bottom of this article it states - If your keystore contains 
>>> multiple certificates (e.g. you are using CA signed certificate) Jenkins 
>>> might end-up using a incorrect one. In this case you can convert the 
>>> keystore to 
>>> PEM<http://stackoverflow.com/questions/7528944/convert-ca-signed-jks-keystore-to-pem>and
>>>  use following command line options.
>>>
>>> Yes, we use a CA signed certificate, and I'm not sure how it might 
>>> decide to use the incorrect one..
>>>
>>> So, I've tried the link, which takes me to stackoverflow, and get as far 
>>> as java ExportPriv> exported-pkcs8.key < 
>>> which falls over with a java nullpoint execption
>>>
>>> Does anyone else have a similar experience or is this something I have 
>>> to work though independently, and why does Jenkins have a problem with 
>>> keystores, and why cant it be fixed?
>>>
>>> thanks
>>>
>>> dD
>>>
>>>
>>>

-- 
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: jenkins/winstone running under https

[jcsirot]

Hello David, 

Can you give us more details on how you installed your keystore? Did you 
have a single keystore containing both self-signed and CA issued 
certificates? What params did you pass to Jenkins at start-up?

-- 
JC

Le lundi 25 février 2013 17:11:24 UTC+1, David Doughty a écrit :
>
> I've beening running jenkins 1.466.12.1 as jenkins on RHEL6.2 (we don't 
> have root access), under https for a few weeks now, using a self signed 
> certificate, no problems, other than than the issues for end users and 
> their browsers. We have now been issued an offical certificate CA chain 
> root-intermediate-server from our security team.
>
> Now the fun begins...
>
> At the moment I don't seem to be able to get Jenkins to recognize the 
> official certificates at all; it only appears to start up with a keystore 
> with the self signed certificate present, which is the only certificate 
> presented to the client browser.
>
> https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins< 
> at the bottom of this article it states - If your keystore contains 
> multiple certificates (e.g. you are using CA signed certificate) Jenkins 
> might end-up using a incorrect one. In this case you can convert the 
> keystore to 
> PEMand
>  use following command line options.
>
> Yes, we use a CA signed certificate, and I'm not sure how it might decide 
> to use the incorrect one..
>
> So, I've tried the link, which takes me to stackoverflow, and get as far 
> as java ExportPriv> exported-pkcs8.key < 
> which falls over with a java nullpoint execption
>
> Does anyone else have a similar experience or is this something I have to 
> work though independently, and why does Jenkins have a problem with 
> keystores, and why cant it be fixed?
>
> thanks
>
> dD
>
>
>

-- 
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: Very long load time for main dashboard since 1.486

[jcsirot]

Hi David,

I opened a ticket in Jenkins JIRA:

https://issues.jenkins-ci.org/browse/JENKINS-15601

Feel free to add details or comments to complete my short description of 
the issue.

-- 
J.-C. Sirot

Le mardi 23 octobre 2012 12:54:47 UTC+2, David Resnick a écrit :
>
> Hi Jean-Christophe,
>
> I can confirm that I have similar exceptions in my log too (you can find a 
> sample at http://pastebin.com/NEXWMMa3 ). I am not able though to 
> correlate the exceptions with the long loading times. Right now my main 
> dashboard loads very quickly (with a Jenkins instance that has been up for 
> over 5 days).
>
> - David
>
> On Tuesday, October 23, 2012 10:40:58 AM UTC+2, jcsirot wrote:
>>
>> Helle David, 
>>
>> I'm facing the same issue too.
>>
>> Looking at the log I noticed this exception. I don't know if it is linked 
>> but after this exception has been printed in the log trail the dashboard 
>> loads immediately.
>> Did someone have any unexpected exception in the log file?
>>
>> Oct 22, 2012 6:53:59 PM org.kohsuke.stapler.compression.CompressionFilter 
>> reportException
>> WARNING: Untrapped servlet exception
>> winstone.ClientSocketException: Failed to write to client
>> at winstone.ClientOutputStream.write(ClientOutputStream.java:41)
>> at 
>> winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:181)
>> at 
>> winstone.WinstoneOutputStream.flush(WinstoneOutputStream.java:219)
>> at 
>> winstone.WinstoneOutputStream.close(WinstoneOutputStream.java:229)
>> at 
>> java.util.zip.DeflaterOutputStream.close(DeflaterOutputStream.java:149)
>> at 
>> org.kohsuke.stapler.compression.FilterServletOutputStream.close(FilterServletOutputStream.java:36)
>> at java.io.FilterOutputStream.close(FilterOutputStream.java:143)
>> at sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:301)
>> at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:130)
>> at java.io.OutputStreamWriter.close(OutputStreamWriter.java:216)
>> at java.io.BufferedWriter.close(BufferedWriter.java:248)
>> at org.dom4j.io.XMLWriter.close(XMLWriter.java:286)
>> at 
>> org.kohsuke.stapler.jelly.HTMLWriterOutput.close(HTMLWriterOutput.java:70)
>> at 
>> org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:56)
>> at 
>> org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:107)
>> at 
>> org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
>> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
>> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
>> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:625)
>> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
>> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
>> at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
>> at 
>> winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
>> at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
>> at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
>> at 
>> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
>> at 
>> hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
>> at 
>> winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
>> at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
>> at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
>> at 
>> winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
>> at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
>> at 
>> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
>> at 
>> hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
>> at 
>> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>> at 
>> org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
>> at 
>> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
>> at 
>> org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
>

Re: Very long load time for main dashboard since 1.486

[jcsirot]

Helle David, 

I'm facing the same issue too.

Looking at the log I noticed this exception. I don't know if it is linked 
but after this exception has been printed in the log trail the dashboard 
loads immediately.
Did someone have any unexpected exception in the log file?

Oct 22, 2012 6:53:59 PM org.kohsuke.stapler.compression.CompressionFilter 
reportException
WARNING: Untrapped servlet exception
winstone.ClientSocketException: Failed to write to client
at winstone.ClientOutputStream.write(ClientOutputStream.java:41)
at 
winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:181)
at 
winstone.WinstoneOutputStream.flush(WinstoneOutputStream.java:219)
at 
winstone.WinstoneOutputStream.close(WinstoneOutputStream.java:229)
at 
java.util.zip.DeflaterOutputStream.close(DeflaterOutputStream.java:149)
at 
org.kohsuke.stapler.compression.FilterServletOutputStream.close(FilterServletOutputStream.java:36)
at java.io.FilterOutputStream.close(FilterOutputStream.java:143)
at sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:301)
at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:130)
at java.io.OutputStreamWriter.close(OutputStreamWriter.java:216)
at java.io.BufferedWriter.close(BufferedWriter.java:248)
at org.dom4j.io.XMLWriter.close(XMLWriter.java:286)
at 
org.kohsuke.stapler.jelly.HTMLWriterOutput.close(HTMLWriterOutput.java:70)
at 
org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:56)
at 
org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:107)
at 
org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:625)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at 
winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at 
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at 
winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at 
winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at 
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at 
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at 
winstone.FilterConfiguration.execute(Filte

Re: Maven Build on Slave Fails: NoClassDefFound error when parsing pom.xml

[jcsirot]

I'm also facing the same problem.

Jenkins version: 1.451
Jenkins master is running on a Linux Debian
Jenkins slave is a MacOSX Lion 10.7.3
Maven is the default Lion embedded maven 3.0.3
Java is the default Lion embedded JDK

The Log output:

Parsing POMs ERROR: Failed to parse POMs 
hudson.util.IOException2:
 
remote file operation failed: work/workspace/JAPI-test-mac at 
hudson.remoting.Channel@11cf4e5:Mac Mini 1 at 
hudson.FilePath.act(FilePath.java:784)at
 
hudson.FilePath.act(FilePath.java:770)at
 
hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:914)at
 
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:658)at
 
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470)at
 
hudson.model.Run.run(Run.java:1409)at
 
hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)at
 
hudson.model.ResourceController.execute(ResourceController.java:88)at
 
hudson.model.Executor.run(Executor.java:238)Caused
 by: 
java.io.IOException:
 
Remote call on Mac Mini 1 failed at 
hudson.remoting.Channel.call(Channel.java:690)at
 
hudson.FilePath.act(FilePath.java:777)...
 8 more Caused by: 
java.lang.NoClassDefFoundError:
 
Could not initialize class hudson.maven.MavenModuleSetBuild at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1180)at
 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1049)at
 
hudson.FilePath$FileCallableWrapper.call(FilePath.java:2099)at
 
hudson.remoting.UserRequest.perform(UserRequest.java:118)at
 
hudson.remoting.UserRequest.perform(UserRequest.java:48)at
 
hudson.remoting.Request$2.run(Request.java:287)at
 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)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:680)Finished:
 FAILURE 

any help will be appreciated.

-- 
Jean-Christophe