Re: Jenkins 1.514 successfully uses explicitly told ANT version to build, but fails to find ANT when asking to use "Standard".

[karg]

It would be great if there would simply be a "Standard: [ANT 1.9]" 
selection box in Jenkins' ANT installations section, so I could avoid 
manually installing it! :-)

Am Dienstag, 22. Oktober 2013 16:08:01 UTC+2 schrieb Daniel Beck:
>
> I used the tool whose version is least significant in most of my jobs as 
> example, but as you're facing the exact same situation with Ant, it applies 
> as well. 
>
> That's basically the use case: You install Ant system-wide (e.g. from your 
> Linux distro's repository), it's put into your PATH (possibly 
> automatically), and that'll get used by Jenkins as the default version. No 
> matter what node you build on, it uses the system-wide default Ant 
> installation. 
>
> If you still want Jenkins to install it, but still don't care about the 
> version, just define an installation, call it 'Any Ant', and select _any_ 
> of the auto-installer choices, configure your jobs to use it, and be done 
> with it. Or redefine PATH (or even just ANT_HOME?) on the node level. 
>
> On 22.10.2013, at 12:24, ka...@quipsy.de  wrote: 
>
> > Are you sure you are talking about ANT? It sounds like you talk about 
> JDK. 
> > 
> > Am Freitag, 18. Oktober 2013 18:55:22 UTC+2 schrieb Daniel Beck: 
> > The 'default' tool version uses whatever is the preferred version on the 
> node's PATH. In this case, there is none. 
> > 
> > This can be useful when you don't care about the Java version used in a 
> job, and have the executing node use its default installation without 
> having to configure the path for every node, or an auto-installer. 
> > 
> > On 18.10.2013, at 10:56, ka...@quipsy.de wrote: 
> > 
> > > I have installed Jenkins 1.514 and told it to automatically provide 
> solely ANT 1.9.2 from Apache. So there is only ANT 1.9.2 on Master and no 
> other ANT installation. 
> > > Then I created a project with the "Run Ant" build task and explicitly 
> specified to use "ANT 1.9.2" in the "ANT version" configuration line. 
> > > The project builds very well. 
> > > 
> > > Then I removed "ANT 1.9.2" and replaced it by "Standard". 
> > > The project does not build now. It says I have to configure the ANT 
> version in the job config. 
> > > 
> > > This is weird. What is "Standard" good for, if it neither 
> automatically chooses the sole ANT installation found on Master, nor allows 
> me to configure "ANT 1.9.2" to be "Standard"? 
> > > 
> > > Thanks! 
> > > -Markus 
> > > 
> > > 
> > > -- 
> > > 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-use...@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-use...@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: Compiler warnings script in global configuration

[Maneesh M P]

Yeah, I found that now.. Thank you!! But I am not able to figure out a a 
regular expression for below pattern

19:35:11 err: Could not parse for environment production: Syntax error at 
'{'; expected '}' at 
/home/build/jenkins/workspace/puppet-parser-try/modules/profile/manifests/shard/master.pp:5
19:35:11 err: Try 'puppet help parser validate' for usage

Whatever I write, I get this error "The regular expression does not match 
the example text."

Thanks,
M

On Tuesday, October 22, 2013 10:31:49 PM UTC-7, Ullrich Hafner wrote:
>
> Isn't there an example in the help of the script and regular 
> expression text fields?
>
> Ulli
>
> Am Mittwoch, 23. Oktober 2013 schrieb Maneesh M P :
>
>> I would like to add a "error" finding script for our project. I know I 
>> can add a groovy script under compiler warning global configuration.
>> Can anyone give me complete example of the global configuration and a 
>> groovy script ?
>>
>> Thanks,
>> M
>>
>> -- 
>> 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.
>>
>

-- 
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: Compiler warnings script in global configuration

[Ullrich Hafner]

Isn't there an example in the help of the script and regular
expression text fields?

Ulli

Am Mittwoch, 23. Oktober 2013 schrieb Maneesh M P :

> I would like to add a "error" finding script for our project. I know I can
> add a groovy script under compiler warning global configuration.
> Can anyone give me complete example of the global configuration and a
> groovy script ?
>
> Thanks,
> M
>
> --
> 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  'cvml', 'jenkinsci-users%2bunsubscr...@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.

Compiler warnings script in global configuration

[Maneesh M P]

I would like to add a "error" finding script for our project. I know I can 
add a groovy script under compiler warning global configuration.
Can anyone give me complete example of the global configuration and a 
groovy script ?

Thanks,
M

-- 
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 pass CLASSPATH variable to Jenkins.

[puyo puy]

Thanks guys, I found the solution by calling the bat file directly from
Jenkins.  In this way, CLASSPATH is available.






On Fri, Oct 18, 2013 at 5:04 PM, Dirk Heinrichs  wrote:

> Am 18.10.2013 07:43, schrieb puyo puy:
>
> > I have an ant script running successfully using bat file. But when I
> > run that script on Jenkins it failed with error
> > "build_preprocess.xml:166: java.lang.NullPointerException".  After
> > many hours of research, I believe that is related to the CLASSPATH
> > environment variable did not pass to Jenkins.  Just wonder is there a
> > way I can pass CLASSPATH to Jenkins?
>
> Put the classpath where it belongs: into the bat file. That script is
> (hopefully) under version control together with anything else, so that
> changes to the classpath don't require a change of the Jenkins job
> configuration.
>
> HTH...
>
> Dirk
> --
>
> *Dirk Heinrichs*, Senior Systems Engineer, Infrastructure
> *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
> *Tel*: +49 2226 159 1149
> *Email*: d...@recommind.com 
> *Skype*: dirk.heinrichs.recommind
> www.recommind.com 
>
>
> http://www.recommind.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/EKSlqHglcsI/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: Different behavior while executing puppet lint through jenkins

[Daniel Beck]

So it's probably something in your /etc/profile or .bash_profile.

You can use a shebang line in 'Execute Shell' build steps to change how the 
shell is invoked (default is -xe), `#!/bin/bash -l` might work there as well.

On 23.10.2013, at 00:56, Maneesh M P  wrote:

> I solved this issue by launching the slave manually using the command ssh 
> bu...@3.ab.xy.com 'bash -l -c "java -jar /home/build/jenkins/slave.jar"'
> 
> 
> On Tuesday, October 22, 2013 11:17:10 AM UTC-7, Maneesh M P wrote:
> If i execute using ssh also I get the same error like jenkins
> 
>  ssh -l build 300.ab..xy.com "find . -iname *.pp -exec puppet-lint 
> --log-format "%{path}:%{linenumber}:%{check}:%{KIND}:%{message}" {} \;"
> 
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError)
> from 
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
>  `to_spec'
> from 
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
>  `gem'
> from /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in 
> `'
> from 
> /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in `eval'
> from 
> /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `'
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError)
> from 
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
>  `to_spec'
> from 
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
>  `gem'
> from /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in 
> `'
> from 
> /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in `eval'
> from 
> /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `'
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError)
> from 
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
>  `to_spec'
> from 
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
>  `gem'
> from /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in 
> `'
> from 
> /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in `eval'
> from 
> /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `'
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError)
> 
> 
> Not getting any clue to fix this issue, any help please?
> 
> 
> On Tuesday, October 22, 2013 11:00:44 AM UTC-7, Maneesh M P wrote:
> I did that, I tried providing all path through slave properties as well. But 
> still no luck.
> Is there a way I can make jenkins use same shell environment? 
> 
> Thanks,
> M
> 
> On Tuesday, October 22, 2013 9:30:48 AM UTC-7, Daniel Beck wrote:
> You don't have your usual shell environment when running a command from 
> Jenkins. Compare the output of the 'env' command. 
> 
> From the installation instructions at https://rvm.io/rvm/install, it looks 
> like you just need to add the command 
> 
> source $HOME/.rvm/scripts/rvm 
> 
> before your find command. 
> 
> On 22.10.2013, at 17:15, Maneesh M P  wrote: 
> 
> > Puppet-lint just works fine while executing the command from build server 
> > console using the below command 
> > 
> > find . -iname *.pp -exec puppet-lint --log-format 
> > "%{path}:%{linenumber}:%{check}:%{KIND}:%{message}" {} \; 
> > 
> > But gives all sorts of error while executing same command through jenkins 
> > "execute shell" option 
> > 
> > 
> > + find . -iname '*.pp' -exec puppet-lint --log-format 
> > '%{path}:%{linenumber}:%{check}:%{KIND}:%{message}' '{}' ';' 
> > /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
> >  

Re: Upgraded plugins, now my install is "bricked."

[Slide]

Do you have publish-over-ssh or publish-over-ftp installed? I believe there
was some issue with one or both of those.


On Tue, Oct 22, 2013 at 4:13 PM, Joshua J. Kugler wrote:

> I have Jenkins 1.509.4 installed on RHEL6.  I just went and upgraded all my
> plugins, and when Jenkins restarted, I get the attached spit out in the
> browser. Nothing in /var/log/jenkins/jenkins.log, just spit to the browser.
>
> I can't even get to my manage screen to try disabling plugins to see what
> might be causing it.
>
> Help?  Pointers to documentation?
>
> Thanks in advance for any help given!
>
> j
>
> --
> Joshua J. Kugler - Fairbanks, Alaska
> Azariah Enterprises - Programming and Website Design
> jos...@azariah.com - Jabber: pedah...@gmail.com
> PGP Key: http://pgp.mit.edu/  ID 0x73B13B6A
>
> --
> 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.
>



-- 
Website: http://earl-of-code.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.

Upgraded plugins, now my install is "bricked."

[Joshua J. Kugler]

I have Jenkins 1.509.4 installed on RHEL6.  I just went and upgraded all my 
plugins, and when Jenkins restarted, I get the attached spit out in the 
browser. Nothing in /var/log/jenkins/jenkins.log, just spit to the browser.

I can't even get to my manage screen to try disabling plugins to see what 
might be causing it.

Help?  Pointers to documentation?

Thanks in advance for any help given!

j

-- 
Joshua J. Kugler - Fairbanks, Alaska
Azariah Enterprises - Programming and Website Design
jos...@azariah.com - Jabber: pedah...@gmail.com
PGP Key: http://pgp.mit.edu/  ID 0x73B13B6A

-- 
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.
org.jvnet.hudson.reactor.ReactorException: java.lang.NoClassDefFoundError: 
com/cloudbees/plugins/credentials/common/StandardCredentials
at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246)
at jenkins.InitReactorRunner.run(InitReactorRunner.java:43)
at jenkins.model.Jenkins.executeReactor(Jenkins.java:904)
at jenkins.model.Jenkins.(Jenkins.java:802)
at hudson.model.Hudson.(Hudson.java:81)
at hudson.model.Hudson.(Hudson.java:77)
at hudson.WebAppMain$3.run(WebAppMain.java:221)
Caused by: java.lang.NoClassDefFoundError: 
com/cloudbees/plugins/credentials/common/StandardCredentials
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2444)
at java.lang.Class.getDeclaredMethods(Class.java:1808)
at org.jvnet.hudson.annotation_indexer.Index$2$1.fetch(Index.java:101)
at org.jvnet.hudson.annotation_indexer.Index$2$1.hasNext(Index.java:71)
at 
org.jvnet.hudson.annotation_indexer.FilterIterator.fetch(FilterIterator.java:23)
at 
org.jvnet.hudson.annotation_indexer.FilterIterator.hasNext(FilterIterator.java:42)
at 
hudson.init.InitializerFinder.discoverTasks(InitializerFinder.java:70)
at hudson.PluginManager$2$1$3.run(PluginManager.java:388)
at 
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:893)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.ClassNotFoundException: 
com.cloudbees.plugins.credentials.common.StandardCredentials
at 
org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1365)
at 
org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315)
at 
org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1068)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
... 17 more

Re: Different behavior while executing puppet lint through jenkins

[Maneesh M P]

I solved this issue by launching the slave manually using the command ssh 
bu...@3.ab.xy.com 'bash -l -c "java -jar /home/build/jenkins/slave.jar"'


On Tuesday, October 22, 2013 11:17:10 AM UTC-7, Maneesh M P wrote:
>
> If i execute using ssh also I get the same error like jenkins
>
>  ssh -l build 300.ab..xy.com "find . -iname *.pp -exec puppet-lint 
> --log-format "%{path}:%{linenumber}:%{check}:%{KIND}:%{message}" {} \;"
>
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  
> `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError)
> from 
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
>  
> `to_spec'
> from 
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
>  
> `gem'
> from /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in 
> `'
> from 
> /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `eval'
> from 
> /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `'
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  
> `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError)
> from 
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
>  
> `to_spec'
> from 
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
>  
> `gem'
> from /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in 
> `'
> from 
> /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `eval'
> from 
> /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `'
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  
> `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError)
> from 
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
>  
> `to_spec'
> from 
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
>  
> `gem'
> from /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in 
> `'
> from 
> /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `eval'
> from 
> /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `'
> /home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  
> `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError)
>
>
> Not getting any clue to fix this issue, any help please?
>
>
> On Tuesday, October 22, 2013 11:00:44 AM UTC-7, Maneesh M P wrote:
>>
>> I did that, I tried providing all path through slave properties as well. 
>> But still no luck.
>> Is there a way I can make jenkins use same shell environment? 
>>
>> Thanks,
>> M
>>
>> On Tuesday, October 22, 2013 9:30:48 AM UTC-7, Daniel Beck wrote:
>>>
>>> You don't have your usual shell environment when running a command from 
>>> Jenkins. Compare the output of the 'env' command. 
>>>
>>> From the installation instructions at https://rvm.io/rvm/install, it 
>>> looks like you just need to add the command 
>>>
>>> source $HOME/.rvm/scripts/rvm 
>>>
>>> before your find command. 
>>>
>>> On 22.10.2013, at 17:15, Maneesh M P  wrote: 
>>>
>>> > Puppet-lint just works fine while executing the command from build 
>>> server console using the below command 
>>> > 
>>> > find . -iname *.pp -exec puppet-lint --log-format 
>>> "%{path}:%{linenumber}:%{check}:%{KIND}:%{message}" {} \; 
>>> > 
>>> > But gives all sorts of error while executing same command through 
>>> jenkins "execute shell" option 
>>> > 
>>> > 
>>> > + find . -iname '*.pp' -exec puppet-lint --log-format 
>>> '%{path}:%{linenumber}:%{check}:%{KIND}:%{message}' '{}' ';' 
>>> > 
>>> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>>>  
>>> `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
>>> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
>>> rake-10.1.0, rubygems-bundler-1.4.

Test results aggregation

[Maureen Barger]

With multiple environments running their own sets of tests, what is
the best way to aggregate their results? So far, solutions I have
googled are not working. 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Problems in login using LDAP server

[Mauricio]

On Oct 22, 2013 6:49 PM, "Daniel Beck"  wrote:
>
> On 22.10.2013, at 23:21, Mauricio  wrote:
>
> > Are you refering to the *nix command or is that a Jenkins plugin?
>
> That's a URL path to a Jenkins page with some diagnostic information
about your user account. Open http://jenkinshost/whoAmI or
http://jenkinshost/jenkins/whoAmI (depending on your configuration) in your
browser after logging in.

It says that I'm log as anonymous
>
> --
> 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/aP-2C5vuS3A/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.

help with Collabnet Plugin authenticating to team forge via certificates

[DrewS]

I have installed jenkins on RHEL 6.4 via RPM.   I have installed the 
CollabNet Plugin to enable uploads of files/etc... to our project after a 
build.  The SCM repository is svn, and is functioning fine after 
modification of the .subversion/servers file:
>
> ssl-client-cert-file = /var/lib/jenkins/.subversion/MyCert.p12
>
> ssl-client-cert-password = Mypass
>
>
>>

I have also added the following to the /etc/sysconfig/jenkins file:  

> JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true 
>>> -Djavax.net.ssl.keyStore=/var/lib/jenkins/MyPass.p12
>>
>>   -Djavax.net.ssl.keyStoreType=pkcs12 
>>> -Djavax.net.ssl.keyStorePassword=MyPass"
>>
>>
Everything checks out fine/builds fine, so my certificates are good.

However, the Collabnet plugin fails to authenticate.  We are only able to 
use certificates, no user name and password.  Apparently, the plugin worked 
around version 1.5 with version 1.4 of jenkins, but both of those are quite 
old, and I'd rather not go 3 years back in time.  If I understand 
correctly,  the plugin is now using Apache's HTTP client for the connection 
code, but the Apache HTTP client does not automatically pick up the 
keystore from the system properties.The old plugin does not work with 
the latest versions of Jenkins, either.

Any ideas on how to get around this problem?  Either modifying the plugin's 
source, or some other mechanism?

Thanks,
and here are the error logs:


CollabNet FileRelease: Critical Error: login to https://project.forge.mil 
failed.  Setting build status to UNSTABLE (or worse).
> ERROR: Publisher hudson.plugins.collabnet.filerelease.CNFileRelease aborted 
> due to exceptionjava.lang.NullPointerException 
> 
>  at 
> hudson.plugins.collabnet.filerelease.CNFileRelease.createAction(CNFileRelease.java:195)
>  
> 
>   at 
> hudson.plugins.collabnet.filerelease.CNFileRelease.perform(CNFileRelease.java:169)
>  
> 
>   at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781)
>  
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:753)
>  
> 
>   at hudson.model.Build$BuildExecution.post2(Build.java:183) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)
>  
> 
>   at hudson.model.Run.execute(Run.java:1690) 
> 
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 
> 
>   at hudson.model.ResourceController.execute(ResourceController.java:88) 
> 
>   at hudson.model.Executor.run(Executor.java:246) 
> 
> Finished: FAILURE
>
>
 and a little more detail from /var/log/jenkins/jenkins.log:

ct 22, 2013 5:50:54 PM hudson.model.Run execute
> INFO: test2 #13 main build action completed: SUCCESS
> Oct 22, 2013 5:50:55 PM hudson.plugins.collabnet.util.CommonUtil logRE
> INFO: getCollabNetApp failed due to org.apache.axis.AxisFault: Error 
> logging in.  Please verify the username and password.
> Oct 22, 2013 5:50:55 PM hudson.plugins.collabnet.util.CNHudsonUtil 
> getCollabNetApp
> SEVERE: getCollabNetApp failed
> AxisFault
>  faultCode: {http://schema.open.collab.net/sfee50/soap50/type}LoginFault
>  faultSubcode:
>  faultString: Error logging in.  Please verify the username and password.
>  faultActor:
>  faultNode:
>  faultDetail:
> 
> {http://xml.apache.org/axis/}exceptionName:com.collabnet.ce.soap50.fault.LoginFault
> {http://xml.apache.org/axis/}hostname:ugunhp3v
> Error logging in.  Please verify the username and password.
> at 
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
> at 
> org.apache.axis.message.SOAPFa

Re: Problems in login using LDAP server

[Daniel Beck]

On 22.10.2013, at 23:21, Mauricio  wrote:

> Are you refering to the *nix command or is that a Jenkins plugin?

That's a URL path to a Jenkins page with some diagnostic information about your 
user account. Open http://jenkinshost/whoAmI or 
http://jenkinshost/jenkins/whoAmI (depending on your configuration) in your 
browser after logging in.

-- 
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: Problems in login using LDAP server

[Mauricio]

+56985101709
On Oct 22, 2013 6:08 PM, "Daniel Beck"  wrote:
>
> What's shown on /whoAmI ?

Are you refering to the *nix command or is that a Jenkins plugin?

>
> On 22.10.2013, at 23:01, Mauricio Fuentes Montero <
fuentes.mont...@gmail.com> wrote:
>
> > Hi everyone,
> >
> > I'm trying to configure security for a new instance of jenkins using
LDAP. Our LDAP server allows anonymous queries and I've set up all the
needed information on jenkins. When I try to login, I enter the username
and password and press the "log in", I understand that if the login went ok
I should see my username on the top-right corner of the next screen, but
nothing happened. I enabled the login for hudson.security.* and I saw the
following log, among others:
> > ...
> >
> > 21-Oct-2013 19:38:50.639 FINE [http-nio-8080-exec-6]
hudson.security.AuthenticationProcessingFilter2.successfulAuthentication
Authentication success:
org.acegisecurity.providers.UsernamePasswordAuthenticationToken@b475870f:
Username: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@104c2b;
Password: [PROTECTED]; Authenticated: true; Details:
org.acegisecurity.ui.WebAuthenticationDetails@6a82: RemoteIpAddress:
127.0.0.1; SessionId: 92846AB177A1833E208B166B7EFAE16E; Granted
Authorities: arquitectura, authenticated, all, ROLE_ARQUITECTURA, ROLE_ALL
> > 21-Oct-2013 19:38:50.639 FINE [http-nio-8080-exec-6]
hudson.security.AuthenticationProcessingFilter2.successfulAuthentication
Updated SecurityContextHolder to contain the following Authentication:
'org.acegisecurity.providers.UsernamePasswordAuthenticationToken@b475870f:
Username: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@104c2b;
Password: [PROTECTED]; Authenticated: true; Details:
org.acegisecurity.ui.WebAuthenticationDetails@6a82: RemoteIpAddress:
127.0.0.1; SessionId: 92846AB177A1833E208B166B7EFAE16E; Granted
Authorities: arquitectura, authenticated, all, ROLE_ARQUITECTURA, ROLE_ALL'
> > 21-Oct-2013 19:38:50.640 FINE [http-nio-8080-exec-6]
hudson.security.AuthenticationProcessingFilter2.successfulAuthentication
Redirecting to target URL from HTTP Session (or default): /manage
> > ...
> >
> > This makes me think that everything is ok, but I'm not logged in.
> >
> > Does anybody know why this happens?
> >
> > 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.
> > For more options, visit https://groups.google.com/groups/opt_out.
>
> --
> 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/aP-2C5vuS3A/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: Problems in login using LDAP server

[Daniel Beck]

What's shown on /whoAmI ?

On 22.10.2013, at 23:01, Mauricio Fuentes Montero  
wrote:

> Hi everyone,
> 
> I'm trying to configure security for a new instance of jenkins using LDAP. 
> Our LDAP server allows anonymous queries and I've set up all the needed 
> information on jenkins. When I try to login, I enter the username and 
> password and press the "log in", I understand that if the login went ok I 
> should see my username on the top-right corner of the next screen, but 
> nothing happened. I enabled the login for hudson.security.* and I saw the 
> following log, among others:
> ...
> 
> 21-Oct-2013 19:38:50.639 FINE [http-nio-8080-exec-6] 
> hudson.security.AuthenticationProcessingFilter2.successfulAuthentication 
> Authentication success: 
> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@b475870f: 
> Username: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@104c2b; 
> Password: [PROTECTED]; Authenticated: true; Details: 
> org.acegisecurity.ui.WebAuthenticationDetails@6a82: RemoteIpAddress: 
> 127.0.0.1; SessionId: 92846AB177A1833E208B166B7EFAE16E; Granted Authorities: 
> arquitectura, authenticated, all, ROLE_ARQUITECTURA, ROLE_ALL
> 21-Oct-2013 19:38:50.639 FINE [http-nio-8080-exec-6] 
> hudson.security.AuthenticationProcessingFilter2.successfulAuthentication 
> Updated SecurityContextHolder to contain the following Authentication: 
> 'org.acegisecurity.providers.UsernamePasswordAuthenticationToken@b475870f: 
> Username: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@104c2b; 
> Password: [PROTECTED]; Authenticated: true; Details: 
> org.acegisecurity.ui.WebAuthenticationDetails@6a82: RemoteIpAddress: 
> 127.0.0.1; SessionId: 92846AB177A1833E208B166B7EFAE16E; Granted Authorities: 
> arquitectura, authenticated, all, ROLE_ARQUITECTURA, ROLE_ALL'
> 21-Oct-2013 19:38:50.640 FINE [http-nio-8080-exec-6] 
> hudson.security.AuthenticationProcessingFilter2.successfulAuthentication 
> Redirecting to target URL from HTTP Session (or default): /manage
> ...
> 
> This makes me think that everything is ok, but I'm not logged in.
> 
> Does anybody know why this happens?
> 
> 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.
> 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.

Problems in login using LDAP server

[Mauricio Fuentes Montero]

Hi everyone,

I'm trying to configure security for a new instance of jenkins using LDAP. 
Our LDAP server allows anonymous queries and I've set up all the needed 
information on jenkins. When I try to login, I enter the username and 
password and press the "log in", I understand that if the login went ok I 
should see my username on the top-right corner of the next screen, but 
nothing happened. I enabled the login for hudson.security.* and I saw the 
following log, among others:
...

21-Oct-2013 19:38:50.639 FINE [http-nio-8080-exec-6] 
hudson.security.AuthenticationProcessingFilter2.successfulAuthentication 
Authentication success: 
org.acegisecurity.providers.UsernamePasswordAuthenticationToken@b475870f: 
Username: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@104c2b; 
Password: [PROTECTED]; Authenticated: true; Details: 
org.acegisecurity.ui.WebAuthenticationDetails@6a82: RemoteIpAddress: 
127.0.0.1; SessionId: 92846AB177A1833E208B166B7EFAE16E; Granted 
Authorities: arquitectura, authenticated, all, ROLE_ARQUITECTURA, ROLE_ALL
21-Oct-2013 19:38:50.639 FINE [http-nio-8080-exec-6] 
hudson.security.AuthenticationProcessingFilter2.successfulAuthentication 
Updated SecurityContextHolder to contain the following Authentication: 
'org.acegisecurity.providers.UsernamePasswordAuthenticationToken@b475870f: 
Username: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@104c2b; 
Password: [PROTECTED]; Authenticated: true; Details: 
org.acegisecurity.ui.WebAuthenticationDetails@6a82: RemoteIpAddress: 
127.0.0.1; SessionId: 92846AB177A1833E208B166B7EFAE16E; Granted 
Authorities: arquitectura, authenticated, all, ROLE_ARQUITECTURA, ROLE_ALL'
21-Oct-2013 19:38:50.640 FINE [http-nio-8080-exec-6] 
hudson.security.AuthenticationProcessingFilter2.successfulAuthentication 
Redirecting to target URL from HTTP Session (or default): /manage
...

This makes me think that everything is ok, but I'm not logged in.

Does anybody know why this happens?

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.
For more options, visit https://groups.google.com/groups/opt_out.

EC2 instances terminate after building job

[Vinod Doshi]

I used latest stable 1.509.4 to setup a jenkins master. I installed the EC2 
plugin and setup a job to launch on demand instances from an ami. The 
instance is launched fine and the build succeeds. However about a min after 
the build succeeds the slave on ec2 is disconnected with an unexpected 
error (although termination time is set to 30 min idle). I setup another 
jenkins master instance with latest build 1.536. Everything works fine on 
this version and slave does does not lose connection. Is this a bug with 
the 1.509.4?

Thanks,
Vinod

-- 
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.

Cannot save changes to job configuration after upgrading to 1.536

[Vinod Doshi]

I upgraded jenkins to 1.536 today. After the upgrade, I cannot save any job 
configuration changes. There is a exception thrown by github plugin. I 
uninstalled github,github-api plugin and then everything started working 
fine. I was able to save job configuration changes. Are hte github and 
github-api plugins breaking in this build?

Thanks,
Vinod
** 

-- 
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: Different behavior while executing puppet lint through jenkins

[Maneesh M P]

If i execute using ssh also I get the same error like jenkins

 ssh -l build 300.ab..xy.com "find . -iname *.pp -exec puppet-lint 
--log-format "%{path}:%{linenumber}:%{check}:%{KIND}:%{message}" {} \;"

/home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
 
`to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
(Gem::LoadError)
from 
/home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
 
`to_spec'
from 
/home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
 
`gem'
from /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in 
`'
from 
/home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
`eval'
from 
/home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
`'
/home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
 
`to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
(Gem::LoadError)
from 
/home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
 
`to_spec'
from 
/home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
 
`gem'
from /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in 
`'
from 
/home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
`eval'
from 
/home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
`'
/home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
 
`to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
(Gem::LoadError)
from 
/home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
 
`to_spec'
from 
/home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
 
`gem'
from /home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in 
`'
from 
/home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
`eval'
from 
/home/cdadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
`'
/home/cdadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
 
`to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
(Gem::LoadError)


Not getting any clue to fix this issue, any help please?


On Tuesday, October 22, 2013 11:00:44 AM UTC-7, Maneesh M P wrote:
>
> I did that, I tried providing all path through slave properties as well. 
> But still no luck.
> Is there a way I can make jenkins use same shell environment? 
>
> Thanks,
> M
>
> On Tuesday, October 22, 2013 9:30:48 AM UTC-7, Daniel Beck wrote:
>>
>> You don't have your usual shell environment when running a command from 
>> Jenkins. Compare the output of the 'env' command. 
>>
>> From the installation instructions at https://rvm.io/rvm/install, it 
>> looks like you just need to add the command 
>>
>> source $HOME/.rvm/scripts/rvm 
>>
>> before your find command. 
>>
>> On 22.10.2013, at 17:15, Maneesh M P  wrote: 
>>
>> > Puppet-lint just works fine while executing the command from build 
>> server console using the below command 
>> > 
>> > find . -iname *.pp -exec puppet-lint --log-format 
>> "%{path}:%{linenumber}:%{check}:%{KIND}:%{message}" {} \; 
>> > 
>> > But gives all sorts of error while executing same command through 
>> jenkins "execute shell" option 
>> > 
>> > 
>> > + find . -iname '*.pp' -exec puppet-lint --log-format 
>> '%{path}:%{linenumber}:%{check}:%{KIND}:%{message}' '{}' ';' 
>> > 
>> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>>  
>> `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
>> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
>> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
>> (Gem::LoadError) 
>> > from 
>> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
>>  
>> `to_spec' 
>> > from 
>> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
>>  
>> `gem' 
>> > from 
>> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:1

Re: Different behavior while executing puppet lint through jenkins

[Maneesh M P]

I did that, I tried providing all path through slave properties as well. 
But still no luck.
Is there a way I can make jenkins use same shell environment? 

Thanks,
M

On Tuesday, October 22, 2013 9:30:48 AM UTC-7, Daniel Beck wrote:
>
> You don't have your usual shell environment when running a command from 
> Jenkins. Compare the output of the 'env' command. 
>
> From the installation instructions at https://rvm.io/rvm/install, it 
> looks like you just need to add the command 
>
> source $HOME/.rvm/scripts/rvm 
>
> before your find command. 
>
> On 22.10.2013, at 17:15, Maneesh M P > 
> wrote: 
>
> > Puppet-lint just works fine while executing the command from build 
> server console using the below command 
> > 
> > find . -iname *.pp -exec puppet-lint --log-format 
> "%{path}:%{linenumber}:%{check}:%{KIND}:%{message}" {} \; 
> > 
> > But gives all sorts of error while executing same command through 
> jenkins "execute shell" option 
> > 
> > 
> > + find . -iname '*.pp' -exec puppet-lint --log-format 
> '%{path}:%{linenumber}:%{check}:%{KIND}:%{message}' '{}' ';' 
> > 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  
> `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError) 
> > from 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
>  
> `to_spec' 
> > from 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
>  
> `gem' 
> > from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in `' 
> > from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `eval' 
> > from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `' 
> > 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  
> `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError) 
> > from 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
>  
> `to_spec' 
> > from 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
>  
> `gem' 
> > from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in `' 
> > from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `eval' 
> > from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `' 
> > 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  
> `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError) 
> > from 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
>  
> `to_spec' 
> > from 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
>  
> `gem' 
> > from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in `' 
> > from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `eval' 
> > from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `' 
> > 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  
> `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, 
> > 
> > 
> > Why is the two different behavior? what is happening while executing 
> through jenkins? can anyone help? 
> > 
> > Thanks, 
> > M 
> > 
> > -- 
> > 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-use...@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.

S3 links from several jobs

[Curtis Kline]

I have a Build Flow job that orchestrates running three Jenkins projects
with various parameters, so there are a total of 12 (Maven) jobs that run.
After these jobs are complete, a wrap-up job is run that just emails out a
list of S3 links to the artifacts that were produced in each of the 12 jobs.

I was able to extract the build number from each of the 12 jobs using
b1.build.number (for example) and passed that to the email job to include
in the S3 links. However the filenames also include the Git branch, and I
haven't been able to pass that to the email job from within the Build Flow.

It seems that there are probably several other ways I could approach this.
One would probably be to grab the artifact filenames from the REST API
(since I already know the build numbers) and prepend my root S3 URL. I am
new to Jenkins and not too clear on the easiest way to do that, though.

Any other suggestions?

Thanks.
Curtis

-- 
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: post-step top-level maven target doesn't find class

[Ramin Rad]

Just as a follow-up, it turns out I do have a maven home,
/usr/share/maven2, but setting my M2_HOME env variable didn't help. A
colleague suggested that this might be an issue with plugin dependency.

Also, I failed to mention in my original post that maven works in all the
build steps except the post step which is a top level maven target.

Thanks for your attention,
-ramin



On Tue, Oct 22, 2013 at 10:41 AM, Ramin Rad  wrote:

> I am having a class not found exception in Jenkins when I run a “Post
> Step” top-level maven target. A google search leads me to not having set
> M2_HOME or M3_HOME env variable. But on my Ubuntu, I don’t have a maven
> home because I used apt-get to install maven and didn’t build it from
> scratch!
>
>
>
> Do you know where maven stores the jar files it needs?
>
>
> Snippet of the build logs are below.
>
>
> Thanks,
>
> -ramin
>
>
>
>
> [workspace] $ mvn -f pom.xml mytarget
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/codehaus/classworlds/Launcher
>
> Caused by: java.lang.ClassNotFoundException:
> org.codehaus.classworlds.Launcher
>
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>
> at java.security.AccessController.doPrivileged(Native Method)
>
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>
> Could not find the main class: org.codehaus.classworlds.Launcher.  Program
> will exit.
>
> Build step 'Invoke top-level Maven targets' marked build as 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: email-ext plugin error

[Slide]

Yes, already fixed via pull request. A new version will be released shortly.


On Tue, Oct 22, 2013 at 9:48 AM, agentbilly  wrote:

> After updating Jenkins to 1.536 today, the email extension plugin version 
> (2.35.1) started throwing this exception.
>
>
> ERROR: Processing failed due to a bug in the code. Please report this to 
> jenkinsci-us...@googlegroups.comjava.lang.NullPointerException 
> 
> at 
> hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:243)
>  
> 
>   at 
> hudson.plugins.emailext.ExtendedEmailPublisher.prebuild(ExtendedEmailPublisher.java:222)
>  
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:815)
>  
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:810)
>  
> 
>   at 
> hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:647)
>  
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) 
> 
>   at hudson.model.Run.execute(Run.java:1665) 
> 
>   at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) 
> 
>   at hudson.model.ResourceController.execute(ResourceController.java:88) 
> 
>   at hudson.model.Executor.run(Executor.java:230) 
> 
>
> [redacted name of company project]
>
>  FATAL: nulljava.lang.NullPointerException 
> 
>  at 
> hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:243)
>  
> 
>   at 
> hudson.plugins.emailext.ExtendedEmailPublisher.prebuild(ExtendedEmailPublisher.java:222)
>  
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:815)
>  
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:810)
>  
> 
>   at 
> hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:647)
>  
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) 
> 
>   at hudson.model.Run.execute(Run.java:1665) 
> 
>   at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) 
> 
>   at hudson.model.ResourceController.execute(ResourceController.java:88) 
> 
>   at hudson.model.Executor.run(Executor.java:230) 
> 
>
>  --
> 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

email-ext plugin error

[agentbilly]

After updating Jenkins to 1.536 today, the email extension plugin version 
(2.35.1) started throwing this exception.


ERROR: Processing failed due to a bug in the code. Please report this to 
jenkinsci-us...@googlegroups.comjava.lang.NullPointerException 
  
at 
hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:243)
 

at 
hudson.plugins.emailext.ExtendedEmailPublisher.prebuild(ExtendedEmailPublisher.java:222)
 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:815)
 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:810)
 

at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:647)
 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) 

at hudson.model.Run.execute(Run.java:1665) 

at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) 

at hudson.model.ResourceController.execute(ResourceController.java:88) 

at hudson.model.Executor.run(Executor.java:230) 


[redacted name of company project]

 FATAL: nulljava.lang.NullPointerException 
  
 at 
hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:243)
 

at 
hudson.plugins.emailext.ExtendedEmailPublisher.prebuild(ExtendedEmailPublisher.java:222)
 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:815)
 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:810)
 

at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:647)
 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) 

at hudson.model.Run.execute(Run.java:1665) 

at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) 

at hudson.model.ResourceController.execute(ResourceController.java:88) 

at hudson.model.Executor.run(Executor.java:230) 


-- 
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: Different behavior while executing puppet lint through jenkins

[Daniel Beck]

You don't have your usual shell environment when running a command from 
Jenkins. Compare the output of the 'env' command.

>From the installation instructions at https://rvm.io/rvm/install, it looks 
>like you just need to add the command

source $HOME/.rvm/scripts/rvm

before your find command.

On 22.10.2013, at 17:15, Maneesh M P  wrote:

> Puppet-lint just works fine while executing the command from build server 
> console using the below command
> 
> find . -iname *.pp -exec puppet-lint --log-format 
> "%{path}:%{linenumber}:%{check}:%{KIND}:%{message}" {} \;
> 
> But gives all sorts of error while executing same command through jenkins 
> "execute shell" option
> 
> 
> + find . -iname '*.pp' -exec puppet-lint --log-format 
> '%{path}:%{linenumber}:%{check}:%{KIND}:%{message}' '{}' ';'
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError)
>   from 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
>  `to_spec'
>   from 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
>  `gem'
>   from /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in 
> `'
>   from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `eval'
>   from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `'
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError)
>   from 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
>  `to_spec'
>   from 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
>  `gem'
>   from /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in 
> `'
>   from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `eval'
>   from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `'
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
> rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
> (Gem::LoadError)
>   from 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
>  `to_spec'
>   from 
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
>  `gem'
>   from /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in 
> `'
>   from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `eval'
>   from 
> /home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
> `'
> /home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
>  `to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
> bundler-unload-1.0.2, executable-hooks-1.2.6, 
> 
> 
> Why is the two different behavior? what is happening while executing through 
> jenkins? can anyone help?
> 
> Thanks,
> M
> 
> -- 
> 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.

-- 
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.

Different behavior while executing puppet lint through jenkins

[Maneesh M P]

Puppet-lint just works fine while executing the command from build server 
console using the below command

find . -iname *.pp -exec puppet-lint --log-format 
"%{path}:%{linenumber}:%{check}:%{KIND}:%{message}" {} \;

But gives all sorts of error while executing same command through jenkins 
"execute shell" option 

+ find . -iname '*.pp' -exec puppet-lint --log-format 
'%{path}:%{linenumber}:%{check}:%{KIND}:%{message}' '{}' ';' 
/home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
 
`to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
(Gem::LoadError) from 
/home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
 
`to_spec' from 
/home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
 
`gem' from 
/home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in `' 
from 
/home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
`eval' from 
/home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
`' 
/home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
 
`to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
(Gem::LoadError) from 
/home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
 
`to_spec' from 
/home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
 
`gem' from 
/home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in `' 
from 
/home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
`eval' from 
/home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
`' 
/home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
 
`to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
bundler-unload-1.0.2, executable-hooks-1.2.6, executable-hooks-1.2.5, 
rake-10.1.0, rubygems-bundler-1.4.0, rubygems-bundler-1.3.4, rvm-1.11.3.8] 
(Gem::LoadError) from 
/home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in
 
`to_spec' from 
/home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in
 
`gem' from 
/home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/puppet-lint:18:in `' 
from 
/home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
`eval' from 
/home/jenkinsadmin/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in 
`' 
/home/jenkinsadmin/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in
 
`to_specs': Could not find puppet-lint (>= 0) amongst [bundler-1.3.5, 
bundler-unload-1.0.2, executable-hooks-1.2.6, 

Why is the two different behavior? what is happening while executing 
through jenkins? can anyone help?

Thanks,
M

-- 
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 can I parameterize a value across all of my jobs

[Robert CHAVANNE]

Eric Wood  rocketmail.com> writes:

> 
> 
> 
> I have a bunch of jobs that are connecting to a TFS server and I have to
put the server path in all of my jobs.  I'm migrating to a new server and
would like to be able to parameterize the value for this server across all
my jobs so I do not have to go through them all and change in the future.
 Can somebody tell me the best means of accomplishing this task?
> 
> Thanks, Eric
> 
> 
> 


Hi Eric,
I think that you should be able to do this by using Configuration Slicing
Plugin. It allows you to define the value of a common parameter on
"http://JenkinsServer:8080/slicing/parameters/"; page. 

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.

How can I parameterize a value across all of my jobs

[Eric Wood]

I have a bunch of jobs that are connecting to a TFS server and I have to put 
the server path in all of my jobs.  I'm migrating to a new server and would 
like to be able to parameterize the value for this server across all my jobs so 
I do not have to go through them all and change in the future.  Can somebody 
tell me the best means of accomplishing this task?

Thanks, Eric

-- 
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.

post-step top-level maven target doesn't find class

[Ramin Rad]

I am having a class not found exception in Jenkins when I run a “Post Step”
top-level maven target. A google search leads me to not having set M2_HOME
or M3_HOME env variable. But on my Ubuntu, I don’t have a maven home
because I used apt-get to install maven and didn’t build it from scratch!



Do you know where maven stores the jar files it needs?


Snippet of the build logs are below.


Thanks,

-ramin




[workspace] $ mvn -f pom.xml mytarget

Exception in thread "main" java.lang.NoClassDefFoundError:
org/codehaus/classworlds/Launcher

Caused by: java.lang.ClassNotFoundException:
org.codehaus.classworlds.Launcher

at java.net.URLClassLoader$1.run(URLClassLoader.java:202)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:190)

at java.lang.ClassLoader.loadClass(ClassLoader.java:306)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)

at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

Could not find the main class: org.codehaus.classworlds.Launcher.  Program
will exit.

Build step 'Invoke top-level Maven targets' marked build as 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: Null pointer exception in ExtendedEmailPublisher after updated jenkins it's plugin and build script- Jenkins ver. 1.536 - Email Extension Plugin ver. 2.35.1

[Slide]

Seems like something from the form is not making it through to the post
with the values for the DataBoundConstructor of the triggers.

"project_triggers":[{"stapler-class":"","kind":""},{"stapler-class":"
","kind":""},{"stapler-class":"","kind":""},{"stapler-class"
:"","kind":""},{"stapler-class":"","kind":""}]

I'm not familiar enough with stapler to know why that could happen.


On Tue, Oct 22, 2013 at 5:59 AM, mubbashir  wrote:

> Hi guys,
>
> Today I had updated jenkins and it's plugin, after the update I am
> getting some weird exception as soon as jenkins is done with scm This will
> only happen if the build script of a job is updated.
>
> After updating the build script I wasn't able to save the job (see below
> the exception 1 )
> - I open the advance option of the editable email and there were couple of
> empty values in the triggers advance option
> - I deleted all the triggers, added new triggers
> - I was able to save the the job
> - On  executing the build I got null pointer exception  (see below the
> exception 2 , couldn't find the complete stack trace)
>
> I removed the editable email notifications from post build actions run the
> build it worked fine.
>
> I got the same null pointer exception on adding the editable email
> notification again.
>
> Any thoughts?
>
> _
>
>
> *Exception 1* (unable to save the job):
>
> Oops!
>
> A problem occurred while processing the request. Please check our bug
> tracker to see if a similar problem has already been reported. If it is
> already reported, please vote and put a comment on it to let us gauge the
> impact of the problem. If you think this is a new issue, please file a new
> issue. When you file an issue, make sure to add the entire stack trace,
> along with the version of Jenkins and relevant plugins. The users list
> might be also useful in understanding what has happened.
>
> Stack trace
>
> javax.servlet.ServletException: java.lang.RuntimeException: Failed to
> instantiate class hudson.plugins.emailext.ExtendedEmailPublisher from
> {"project_recipient_list":"$DEFAULT_RECIPIENTS","project_replyto":"$DEFAULT_RECIPIENTS","project_content_type":"default","project_default_subject":"$DEFAULT_SUBJECT","project_default_content":"$DEFAULT_CONTENT","project_attachments":"","project_attach_buildlog":"0","project_presend_script":"","project_save_output":false,"project_triggers":[{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""}],"stapler-class":"hudson.plugins.emailext.ExtendedEmailPublisher","kind":"hudson.plugins.emailext.ExtendedEmailPublisher"}
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:777)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841)
> at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
> at
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:727)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:630)
> at org.kohsuke.stapler.Stapler.service(Stapler.java:224)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
> at
> hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
> at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
> at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 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
> jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
> 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.sec

Re: Null pointer exception in ExtendedEmailPublisher after updated jenkins it's plugin and build script- Jenkins ver. 1.536 - Email Extension Plugin ver. 2.35.1

[mubbashir]

I tried the same after posting to the mailing list, didn't help :( 

It actually went back to the same thing where I wasn't able to save the job 
:(

On Tuesday, 22 October 2013 18:09:51 UTC+4, Daniel Beck wrote:
>
> I think we had this just yesterday, try removing and adding the email-ext 
> publisher, then make sure to add a trigger (e.g. 'Success'). 
>
> On 22.10.2013, at 14:59, mubbashir > 
> wrote: 
>
> > Hi guys, 
> > 
> > Today I had updated jenkins and it's plugin, after the update I am 
> getting some weird exception as soon as jenkins is done with scm This will 
> only happen if the build script of a job is updated. 
> > 
> > After updating the build script I wasn't able to save the job (see below 
> the exception 1 ) 
> > - I open the advance option of the editable email and there were couple 
> of empty values in the triggers advance option 
> > - I deleted all the triggers, added new triggers 
> > - I was able to save the the job 
> > - On  executing the build I got null pointer exception  (see below the 
> exception 2 , couldn't find the complete stack trace) 
> > 
> > I removed the editable email notifications from post build actions run 
> the build it worked fine. 
> > 
> > I got the same null pointer exception on adding the editable email 
> notification again. 
> > 
> > Any thoughts? 
> > 
> > _ 
> > 
> > 
> > Exception 1 (unable to save the job): 
> > 
> > Oops! 
> > 
> > A problem occurred while processing the request. Please check our bug 
> tracker to see if a similar problem has already been reported. If it is 
> already reported, please vote and put a comment on it to let us gauge the 
> impact of the problem. If you think this is a new issue, please file a new 
> issue. When you file an issue, make sure to add the entire stack trace, 
> along with the version of Jenkins and relevant plugins. The users list 
> might be also useful in understanding what has happened. 
> > 
> > Stack trace 
> > 
> > javax.servlet.ServletException: java.lang.RuntimeException: Failed to 
> instantiate class hudson.plugins.emailext.ExtendedEmailPublisher from 
> {"project_recipient_list":"$DEFAULT_RECIPIENTS","project_replyto":"$DEFAULT_RECIPIENTS","project_content_type":"default","project_default_subject":"$DEFAULT_SUBJECT","project_default_content":"$DEFAULT_CONTENT","project_attachments":"","project_attach_buildlog":"0","project_presend_script":"","project_save_output":false,"project_triggers":[{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""}],"stapler-class":"hudson.plugins.emailext.ExtendedEmailPublisher","kind":"hudson.plugins.emailext.ExtendedEmailPublisher"}
>  
>
> > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:777) 
> > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841) 
> > at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) 
> > at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) 
>
> > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:727) 
> > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841) 
> > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:630) 
> > at org.kohsuke.stapler.Stapler.service(Stapler.java:224) 
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) 
> > at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>  
>
> > at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>  
>
> > at 
> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) 
> > at 
> hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) 
> > at 
> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 
> > at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) 
> > at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>  
>
> > at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>  
>
> > at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) 
> > at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>  
>
> > at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>  
>
> > 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 
> jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
>  
>
> > at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) 
>
> > at 
> org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.ja

Re: how to display a filtered history of a parameterized build?

[Michal Maruska]

On 22 October 2013 14:40, Michal Maruska  wrote:
> Hello,
>
> I have a parameterized build.
> I would like to see the build history, but limited  to those builds with a
> fixed parameter value.

It seems a possible way is to use the Pipeline View: invoke the
parameterized build with fixed parameter value  through a
special/reserved "Build Flow" job;   then  Pipeline View for pipelines
triggered by that invoker will show that part of the build history.

-- 
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: Null pointer exception in ExtendedEmailPublisher after updated jenkins it's plugin and build script- Jenkins ver. 1.536 - Email Extension Plugin ver. 2.35.1

[Ahmed Mubbashir Khan]

I tried the same after posting to the mailing list, didn't help :(

Regards,
--
Ahmed Mubbashir Khan
"I don't make Software, I make it better"
http://about.me/mubbashir


On Tue, Oct 22, 2013 at 6:09 PM, Daniel Beck  wrote:

> I think we had this just yesterday, try removing and adding the email-ext
> publisher, then make sure to add a trigger (e.g. 'Success').
>
> On 22.10.2013, at 14:59, mubbashir  wrote:
>
> > Hi guys,
> >
> > Today I had updated jenkins and it's plugin, after the update I am
> getting some weird exception as soon as jenkins is done with scm This will
> only happen if the build script of a job is updated.
> >
> > After updating the build script I wasn't able to save the job (see below
> the exception 1 )
> > - I open the advance option of the editable email and there were couple
> of empty values in the triggers advance option
> > - I deleted all the triggers, added new triggers
> > - I was able to save the the job
> > - On  executing the build I got null pointer exception  (see below the
> exception 2 , couldn't find the complete stack trace)
> >
> > I removed the editable email notifications from post build actions run
> the build it worked fine.
> >
> > I got the same null pointer exception on adding the editable email
> notification again.
> >
> > Any thoughts?
> >
> > _
> >
> >
> > Exception 1 (unable to save the job):
> >
> > Oops!
> >
> > A problem occurred while processing the request. Please check our bug
> tracker to see if a similar problem has already been reported. If it is
> already reported, please vote and put a comment on it to let us gauge the
> impact of the problem. If you think this is a new issue, please file a new
> issue. When you file an issue, make sure to add the entire stack trace,
> along with the version of Jenkins and relevant plugins. The users list
> might be also useful in understanding what has happened.
> >
> > Stack trace
> >
> > javax.servlet.ServletException: java.lang.RuntimeException: Failed to
> instantiate class hudson.plugins.emailext.ExtendedEmailPublisher from
> {"project_recipient_list":"$DEFAULT_RECIPIENTS","project_replyto":"$DEFAULT_RECIPIENTS","project_content_type":"default","project_default_subject":"$DEFAULT_SUBJECT","project_default_content":"$DEFAULT_CONTENT","project_attachments":"","project_attach_buildlog":"0","project_presend_script":"","project_save_output":false,"project_triggers":[{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""}],"stapler-class":"hudson.plugins.emailext.ExtendedEmailPublisher","kind":"hudson.plugins.emailext.ExtendedEmailPublisher"}
> > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:777)
> > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841)
> > at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
> > at
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
> > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:727)
> > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841)
> > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:630)
> > at org.kohsuke.stapler.Stapler.service(Stapler.java:224)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> > at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> > at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > at
> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
> > at
> hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
> > at
> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
> > at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
> > at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
> > at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > 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
> jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
> > 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
>

Re: Null pointer exception in ExtendedEmailPublisher after updated jenkins it's plugin and build script- Jenkins ver. 1.536 - Email Extension Plugin ver. 2.35.1

[Daniel Beck]

I think we had this just yesterday, try removing and adding the email-ext 
publisher, then make sure to add a trigger (e.g. 'Success').

On 22.10.2013, at 14:59, mubbashir  wrote:

> Hi guys, 
> 
> Today I had updated jenkins and it's plugin, after the update I am getting 
> some weird exception as soon as jenkins is done with scm This will only 
> happen if the build script of a job is updated.
> 
> After updating the build script I wasn't able to save the job (see below the 
> exception 1 )
> - I open the advance option of the editable email and there were couple of 
> empty values in the triggers advance option
> - I deleted all the triggers, added new triggers
> - I was able to save the the job
> - On  executing the build I got null pointer exception  (see below the 
> exception 2 , couldn't find the complete stack trace)
> 
> I removed the editable email notifications from post build actions run the 
> build it worked fine. 
> 
> I got the same null pointer exception on adding the editable email 
> notification again. 
> 
> Any thoughts?
> 
> _
> 
> 
> Exception 1 (unable to save the job):
> 
> Oops!
> 
> A problem occurred while processing the request. Please check our bug tracker 
> to see if a similar problem has already been reported. If it is already 
> reported, please vote and put a comment on it to let us gauge the impact of 
> the problem. If you think this is a new issue, please file a new issue. When 
> you file an issue, make sure to add the entire stack trace, along with the 
> version of Jenkins and relevant plugins. The users list might be also useful 
> in understanding what has happened.
> 
> Stack trace
> 
> javax.servlet.ServletException: java.lang.RuntimeException: Failed to 
> instantiate class hudson.plugins.emailext.ExtendedEmailPublisher from 
> {"project_recipient_list":"$DEFAULT_RECIPIENTS","project_replyto":"$DEFAULT_RECIPIENTS","project_content_type":"default","project_default_subject":"$DEFAULT_SUBJECT","project_default_content":"$DEFAULT_CONTENT","project_attachments":"","project_attach_buildlog":"0","project_presend_script":"","project_save_output":false,"project_triggers":[{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""}],"stapler-class":"hudson.plugins.emailext.ExtendedEmailPublisher","kind":"hudson.plugins.emailext.ExtendedEmailPublisher"}
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:777)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841)
> at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
> at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:727)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:630)
> at org.kohsuke.stapler.Stapler.service(Stapler.java:224)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
> at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
> at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
> at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 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 
> jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
> 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.

Re: Jenkins 1.514 successfully uses explicitly told ANT version to build, but fails to find ANT when asking to use "Standard".

[Daniel Beck]

I used the tool whose version is least significant in most of my jobs as 
example, but as you're facing the exact same situation with Ant, it applies as 
well.

That's basically the use case: You install Ant system-wide (e.g. from your 
Linux distro's repository), it's put into your PATH (possibly automatically), 
and that'll get used by Jenkins as the default version. No matter what node you 
build on, it uses the system-wide default Ant installation.

If you still want Jenkins to install it, but still don't care about the 
version, just define an installation, call it 'Any Ant', and select _any_ of 
the auto-installer choices, configure your jobs to use it, and be done with it. 
Or redefine PATH (or even just ANT_HOME?) on the node level.

On 22.10.2013, at 12:24, k...@quipsy.de wrote:

> Are you sure you are talking about ANT? It sounds like you talk about JDK.
> 
> Am Freitag, 18. Oktober 2013 18:55:22 UTC+2 schrieb Daniel Beck:
> The 'default' tool version uses whatever is the preferred version on the 
> node's PATH. In this case, there is none. 
> 
> This can be useful when you don't care about the Java version used in a job, 
> and have the executing node use its default installation without having to 
> configure the path for every node, or an auto-installer. 
> 
> On 18.10.2013, at 10:56, ka...@quipsy.de wrote: 
> 
> > I have installed Jenkins 1.514 and told it to automatically provide solely 
> > ANT 1.9.2 from Apache. So there is only ANT 1.9.2 on Master and no other 
> > ANT installation. 
> > Then I created a project with the "Run Ant" build task and explicitly 
> > specified to use "ANT 1.9.2" in the "ANT version" configuration line. 
> > The project builds very well. 
> > 
> > Then I removed "ANT 1.9.2" and replaced it by "Standard". 
> > The project does not build now. It says I have to configure the ANT version 
> > in the job config. 
> > 
> > This is weird. What is "Standard" good for, if it neither automatically 
> > chooses the sole ANT installation found on Master, nor allows me to 
> > configure "ANT 1.9.2" to be "Standard"? 
> > 
> > Thanks! 
> > -Markus 
> > 
> > 
> > -- 
> > 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-use...@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.

-- 
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 1.514 successfully uses explicitly told ANT version to build, but fails to find ANT when asking to use "Standard".

[karg]

No, it is not. I want Jenkins to install ANT and then use that one, which 
works fine if I specify an explicit ANT version in the job. But I don't 
care that the exact version, as the job in fact would run with really any 
version of ANT.

Am Dienstag, 22. Oktober 2013 14:53:12 UTC+2 schrieb LesMikesell:
>
> On Tue, Oct 22, 2013 at 5:26 AM,  > wrote: 
> > In my particular case, the ANT script to run is so ridiculously simple 
> that 
> > it won't fail ever. It consists only of a single . So I'd be happy 
> if 
> > I could just tell Jenkins that it shall just pick any ANT to do the job. 
> > 
>
> Is there an ant located in the PATH on the machine? 
>
> -- 
>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.

Null pointer exception in ExtendedEmailPublisher after updated jenkins it's plugin and build script- Jenkins ver. 1.536 - Email Extension Plugin ver. 2.35.1

[mubbashir]

Hi guys, 

Today I had updated jenkins and it's plugin, after the update I am getting 
some weird exception as soon as jenkins is done with scm This will only 
happen if the build script of a job is updated.

After updating the build script I wasn't able to save the job (see below 
the exception 1 )
- I open the advance option of the editable email and there were couple of 
empty values in the triggers advance option
- I deleted all the triggers, added new triggers
- I was able to save the the job
- On  executing the build I got null pointer exception  (see below the 
exception 2 , couldn't find the complete stack trace)

I removed the editable email notifications from post build actions run the 
build it worked fine. 

I got the same null pointer exception on adding the editable email 
notification again. 

Any thoughts?

_


*Exception 1* (unable to save the job):

Oops!

A problem occurred while processing the request. Please check our bug 
tracker to see if a similar problem has already been reported. If it is 
already reported, please vote and put a comment on it to let us gauge the 
impact of the problem. If you think this is a new issue, please file a new 
issue. When you file an issue, make sure to add the entire stack trace, 
along with the version of Jenkins and relevant plugins. The users list 
might be also useful in understanding what has happened.

Stack trace

javax.servlet.ServletException: java.lang.RuntimeException: Failed to 
instantiate class hudson.plugins.emailext.ExtendedEmailPublisher from 
{"project_recipient_list":"$DEFAULT_RECIPIENTS","project_replyto":"$DEFAULT_RECIPIENTS","project_content_type":"default","project_default_subject":"$DEFAULT_SUBJECT","project_default_content":"$DEFAULT_CONTENT","project_attachments":"","project_attach_buildlog":"0","project_presend_script":"","project_save_output":false,"project_triggers":[{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""},{"stapler-class":"","kind":""}],"stapler-class":"hudson.plugins.emailext.ExtendedEmailPublisher","kind":"hudson.plugins.emailext.ExtendedEmailPublisher"}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:777)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:727)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:630)
at org.kohsuke.stapler.Stapler.service(Stapler.java:224)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at 
hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
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 
jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
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:174)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.ja

Re: Jenkins 1.514 successfully uses explicitly told ANT version to build, but fails to find ANT when asking to use "Standard".

[Les Mikesell]

On Tue, Oct 22, 2013 at 5:26 AM,   wrote:
> In my particular case, the ANT script to run is so ridiculously simple that
> it won't fail ever. It consists only of a single . So I'd be happy if
> I could just tell Jenkins that it shall just pick any ANT to do the job.
>

Is there an ant located in the PATH on the machine?

-- 
   Les Mikesell
 lesmikes...@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.

how to display a filtered history of a parameterized build?

[Michal Maruska]

Hello,

I have a parameterized build.
I would like to see the build history, but limited  to those builds with a 
fixed parameter value.

It seems customizable "views" do not list the history, so I'm lost.

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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Violations plugin uses wrong path to find pep8 report

[Ulli Hafner]

Seems that something is broken there. Please create a bug report in our issue 
tracker.

Can you please check if the pep8 parser in the warnings plug-in works for your 
file? If the same exceptions appears there too then maybe your input file is 
somehow corrupt?

Ulli
   

Am 22.10.2013 um 12:37 schrieb Dmitry S :

> reports\pep8.log
> 
> вторник, 22 октября 2013 г., 14:23:05 UTC+4 пользователь Ullrich Hafner 
> написал:
> What did you specify as file pattern?
> 
> Ulli
> 
> Am 22.10.2013 um 12:07 schrieb Dmitry S :
> 
>> I'm using pytest to run pep8 check:
>> 
>> py.test --pep8 --junitxml=reports\pep8.log
>> 
>> I setup a job to look for pep8.log file in reports\pep8.log
>> 
>> But when i run the job I see that the path where violations plugin looks for 
>> reports makes no sense:
>> 
>> generated xml file: 
>> C:\Jenkins\jobs\python-template-2\workspace\reports\pep8.log 
>> === 89 failed, 33 skipped, 1 error in 1.48 seconds 
>> 
>> 
>> C:\Jenkins\jobs\python-template-2\workspace>exit 1 
>> Build step 'Выполнить команду Windows' marked build as failure
>> ERROR: Publisher hudson.plugins.violations.ViolationsPublisher aborted due 
>> to exception
>> java.io.FileNotFoundException: 
>> C:\Jenkins\jobs\python-template-2\builds\2013-10-22_13-30-44\violations\file\<\failure><\testcase>>  classname="" name="contests.migrations.0003_auto__add_votinghistory" 
>> time="0.016324249">C:\Jenkins\jobs\python-template-2\workspace\contests\migrations\0003_auto__add_votinghistory.py.xml
>>  (Синтаксическая ошибка в имени файла, имени папки или метке тома)
>>  at java.io.FileOutputStream.open(Native Method)
>>  at java.io.FileOutputStream.(Unknown Source)
>>  at java.io.FileOutputStream.(Unknown Source)
>>  at hudson.FilePath.write(FilePath.java:1642)
>>  at 
>> hudson.plugins.violations.generate.ExecuteFilePath.execute(ExecuteFilePath.java:40)
>>  at 
>> hudson.plugins.violations.generate.GenerateXML.execute(GenerateXML.java:47)
>>  at 
>> hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:122)
>>  at 
>> hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:25)
>>  at hudson.FilePath.act(FilePath.java:912)
>>  at hudson.FilePath.act(FilePath.java:885)
>>  at 
>> hudson.plugins.violations.ViolationsPublisher.perform(ViolationsPublisher.java:74)
>>  at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781)
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:753)
>>  at hudson.model.Build$BuildExecution.post2(Build.java:183)
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)
>>  at hudson.model.Run.execute(Run.java:1690)
>>  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
>>  at hudson.model.ResourceController.execute(ResourceController.java:88)
>>  at hudson.model.Executor.run(Executor.java:230)
>> Finished: FAILURE
>> 
>> Addittionally, I tried to launch pep8 check without using pytest, instead I 
>> used this command for windows to find and check all .py files:
>> 
>> FOR /R %i IN (*.py) DO pep8 %i  1>>reports\pep8.log 
>> 
>> In this case, I get the following:
>> 
>> C:\Jenkins\jobs\python-template-2\workspace>exit 1 
>> Build step 'Выполнить команду Windows' marked build as failure
>> ERROR: Publisher hudson.plugins.violations.ViolationsPublisher aborted due 
>> to exception
>> java.io.FileNotFoundException: 
>> C:\Jenkins\jobs\python-template-2\builds\2013-10-15_13-31-37\violations\file\C:\Jenkins\jobs\python-template-2\workspace\notifications\email.py.xml
>>  (Syntax error in filename)
>>  at java.io.FileOutputStream.open(Native Method)
>>  at java.io.FileOutputStream.(Unknown Source)
>>  at java.io.FileOutputStream.(Unknown Source)
>>  at hudson.FilePath.write(FilePath.java:1666)
>>  at 
>> hudson.plugins.violations.generate.ExecuteFilePath.execute(ExecuteFilePath.java:40)
>>  at 
>> hudson.plugins.violations.generate.GenerateXML.execute(GenerateXML.java:47)
>>  at 
>> hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:122)
>>  at 
>> hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:25)
>>  at hudson.FilePath.act(FilePath.java:916)
>>  at hudson.FilePath.act(FilePath.java:889)
>>  at 
>> hudson.plugins.violations.ViolationsPublisher.perform(ViolationsPublisher.java:74)
>>  at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:786)
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:758)
>>  at hudson.model.Build$BuildExecution.post2(Build.java:183)
>>  at 
>> hudson.model.AbstractBuild$Abs

Re: Violations plugin uses wrong path to find pep8 report

[Dmitry S]

reports\pep8.log

вторник, 22 октября 2013 г., 14:23:05 UTC+4 пользователь Ullrich Hafner 
написал:
>
> What did you specify as file pattern?
>
> Ulli
>
> Am 22.10.2013 um 12:07 schrieb Dmitry S 
> >:
>
> I'm using pytest to run pep8 check:
>
> py.test --pep8 --junitxml=reports\pep8.log
>
> I setup a job to look for pep8.log file in reports\pep8.log
>
> But when i run the job I see that the path where violations plugin looks 
> for reports makes no sense:
>
> generated xml file: 
> C:\Jenkins\jobs\python-template-2\workspace\reports\pep8.log 
> === 89 failed, 33 skipped, 1 error in 1.48 seconds 
> 
>
> C:\Jenkins\jobs\python-template-2\workspace>exit 1 
> Build step 'Выполнить команду Windows' marked build as failure
> ERROR: Publisher hudson.plugins.violations.ViolationsPublisher aborted due to 
> exception*java.io.FileNotFoundException 
> :
>  
> C:\Jenkins\jobs\python-template-2\builds\2013-10-22_13-30-44\violations\file\<\failure><\testcase>  classname="" name="contests.migrations.0003_auto__add_votinghistory" 
> time="0.016324249">C:\Jenkins\jobs\python-template-2\workspace\contests\migrations\0003_auto__add_votinghistory.py.xml*
>  (Синтаксическая ошибка в имени файла, имени папки или метке тома)
>   at java.io.FileOutputStream.open(Native Method)
>   at java.io.FileOutputStream.(Unknown Source)
>   at java.io.FileOutputStream.(Unknown Source)
>   at hudson.FilePath.write(FilePath.java:1642)
>   at 
> hudson.plugins.violations.generate.ExecuteFilePath.execute(ExecuteFilePath.java:40)
>   at 
> hudson.plugins.violations.generate.GenerateXML.execute(GenerateXML.java:47)
>   at 
> hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:122)
>   at 
> hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:25)
>   at hudson.FilePath.act(FilePath.java:912)
>   at hudson.FilePath.act(FilePath.java:885)
>   at 
> hudson.plugins.violations.ViolationsPublisher.perform(ViolationsPublisher.java:74)
>   at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:753)
>   at hudson.model.Build$BuildExecution.post2(Build.java:183)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)
>   at hudson.model.Run.execute(Run.java:1690)
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
>   at hudson.model.ResourceController.execute(ResourceController.java:88)
>   at hudson.model.Executor.run(Executor.java:230)
> Finished: FAILURE
>
>
> Addittionally, I tried to launch pep8 check without using pytest, instead I 
> used this command for windows to find and check all .py files:
>
> FOR /R %i IN (*.py) DO pep8 %i  1>>reports\pep8.log 
>
>
> In this case, I get the following:
>
>
> C:\Jenkins\jobs\python-template-2\workspace>exit 1 
> Build step 'Выполнить команду Windows' marked build as failure
> ERROR: Publisher hudson.plugins.violations.ViolationsPublisher aborted due to 
> exception*java.io.FileNotFoundException 
> :
>  
> C:\Jenkins\jobs\python-template-2\builds\2013-10-15_13-31-37\violations\file\C:\Jenkins\jobs\python-template-2\workspace\notifications\email.py.xml
>  (Syntax error in filename)*
>   at java.io.FileOutputStream.open(Native Method)
>   at java.io.FileOutputStream.(Unknown Source)
>   at java.io.FileOutputStream.(Unknown Source)
>   at hudson.FilePath.write(FilePath.java:1666)
>   at 
> hudson.plugins.violations.generate.ExecuteFilePath.execute(ExecuteFilePath.java:40)
>   at 
> hudson.plugins.violations.generate.GenerateXML.execute(GenerateXML.java:47)
>   at 
> hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:122)
>   at 
> hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:25)
>   at hudson.FilePath.act(FilePath.java:916)
>   at hudson.FilePath.act(FilePath.java:889)
>   at 
> hudson.plugins.violations.ViolationsPublisher.perform(ViolationsPublisher.java:74)
>   at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:786)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:758)
>   at hudson.model.Build$BuildExecution.post2(Build.java:183)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:711)
>   at hudson.model.Run.execute(Run.java:1690)
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
>   at hudson.model.ResourceController.execu

Re: Jenkins 1.514 successfully uses explicitly told ANT version to build, but fails to find ANT when asking to use "Standard".

[karg]

In my particular case, the ANT script to run is so ridiculously simple that 
it won't fail ever. It consists only of a single . So I'd be happy if 
I could just tell Jenkins that it shall just pick any ANT to do the job.

Am Montag, 21. Oktober 2013 11:39:52 UTC+2 schrieb Andreas Schilling:
>
> Hi Markus, 
>
> while I understand your point of view (thought the same some time ago) I 
> nowadays highly recommend to use explicit tool versions for everything. My 
> experience is that it is alot easier to track down build problems if 
> explicit versions are used everywhere. It may be a hassle to manage alot of 
> jobs if you e.g. want to switch to a later version of tool X, however 
> groovy scripts are your friend here... 
>
> Mit freundlichen Grüßen / kind regards 
> i.A. Andreas Schilling 
> Enterprise Processes & Software 
> --- 
> Dipl. Inf. Andreas Schilling 
> Senior Software Architect 
>
> TWT GmbH 
> Science & Innovation 
> Ernsthaldenstraße 17 
> D-70565 Stuttgart 
>   
> Tel: +49.7 11.21 57 77.6 73 
> Mobil: +49.1 72.6 22 88 70 
> E-Mail: andreas@twt-gmbh.de  
>  
> www.twt-gmbh.de 
>  
> Geschäftsführung: Dr. Dimitrios Vartziotis, Joachim Laicher (Stv.), Frank 
> Beutenmüller (Stv.) 
> Registergericht: Amtsgericht Stuttgart, HRB Nr. 212778 
> Umsatzsteuer: ID-Nr.: DE147841145 
>  
>
>
>
> Von:ka...@quipsy.de  
> An:jenkins...@googlegroups.com  
> Datum:18.10.2013 10:56 
> Betreff:Jenkins 1.514 successfully uses explicitly told ANT 
> version to build, but fails to find ANT when asking to use "Standard". 
> Gesendet von:jenkins...@googlegroups.com  
> --
>
>
>
> I have installed Jenkins 1.514 and told it to automatically provide solely 
> ANT 1.9.2 from Apache. So there is only ANT 1.9.2 on Master and no other 
> ANT installation. 
> Then I created a project with the "Run Ant" build task and explicitly 
> specified to use "ANT 1.9.2" in the "ANT version" configuration line. 
> The project builds very well. 
>
> Then I removed "ANT 1.9.2" and replaced it by "Standard". 
> The project does not build now. It says I have to configure the ANT 
> version in the job config. 
>
> This is weird. What is "Standard" good for, if it neither automatically 
> chooses the sole ANT installation found on Master, nor allows me to 
> configure "ANT 1.9.2" to be "Standard"? 
>
> Thanks! 
> -Markus 
>
> -- 
> 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-use...@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: Jenkins 1.514 successfully uses explicitly told ANT version to build, but fails to find ANT when asking to use "Standard".

[karg]

Are you sure you are talking about ANT? It sounds like you talk about JDK.

Am Freitag, 18. Oktober 2013 18:55:22 UTC+2 schrieb Daniel Beck:
>
> The 'default' tool version uses whatever is the preferred version on the 
> node's PATH. In this case, there is none. 
>
> This can be useful when you don't care about the Java version used in a 
> job, and have the executing node use its default installation without 
> having to configure the path for every node, or an auto-installer. 
>
> On 18.10.2013, at 10:56, ka...@quipsy.de  wrote: 
>
> > I have installed Jenkins 1.514 and told it to automatically provide 
> solely ANT 1.9.2 from Apache. So there is only ANT 1.9.2 on Master and no 
> other ANT installation. 
> > Then I created a project with the "Run Ant" build task and explicitly 
> specified to use "ANT 1.9.2" in the "ANT version" configuration line. 
> > The project builds very well. 
> > 
> > Then I removed "ANT 1.9.2" and replaced it by "Standard". 
> > The project does not build now. It says I have to configure the ANT 
> version in the job config. 
> > 
> > This is weird. What is "Standard" good for, if it neither automatically 
> chooses the sole ANT installation found on Master, nor allows me to 
> configure "ANT 1.9.2" to be "Standard"? 
> > 
> > Thanks! 
> > -Markus 
> > 
> > 
> > -- 
> > 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-use...@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: Violations plugin uses wrong path to find pep8 report

[Ulli Hafner]

What did you specify as file pattern?

Ulli

Am 22.10.2013 um 12:07 schrieb Dmitry S :

> I'm using pytest to run pep8 check:
> 
> py.test --pep8 --junitxml=reports\pep8.log
> 
> I setup a job to look for pep8.log file in reports\pep8.log
> 
> But when i run the job I see that the path where violations plugin looks for 
> reports makes no sense:
> 
> generated xml file: 
> C:\Jenkins\jobs\python-template-2\workspace\reports\pep8.log 
> === 89 failed, 33 skipped, 1 error in 1.48 seconds 
> 
> 
> C:\Jenkins\jobs\python-template-2\workspace>exit 1 
> Build step 'Выполнить команду Windows' marked build as failure
> ERROR: Publisher hudson.plugins.violations.ViolationsPublisher aborted due to 
> exception
> java.io.FileNotFoundException: 
> C:\Jenkins\jobs\python-template-2\builds\2013-10-22_13-30-44\violations\file\<\failure><\testcase>  classname="" name="contests.migrations.0003_auto__add_votinghistory" 
> time="0.016324249">C:\Jenkins\jobs\python-template-2\workspace\contests\migrations\0003_auto__add_votinghistory.py.xml
>  (Синтаксическая ошибка в имени файла, имени папки или метке тома)
>   at java.io.FileOutputStream.open(Native Method)
>   at java.io.FileOutputStream.(Unknown Source)
>   at java.io.FileOutputStream.(Unknown Source)
>   at hudson.FilePath.write(FilePath.java:1642)
>   at 
> hudson.plugins.violations.generate.ExecuteFilePath.execute(ExecuteFilePath.java:40)
>   at 
> hudson.plugins.violations.generate.GenerateXML.execute(GenerateXML.java:47)
>   at 
> hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:122)
>   at 
> hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:25)
>   at hudson.FilePath.act(FilePath.java:912)
>   at hudson.FilePath.act(FilePath.java:885)
>   at 
> hudson.plugins.violations.ViolationsPublisher.perform(ViolationsPublisher.java:74)
>   at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:753)
>   at hudson.model.Build$BuildExecution.post2(Build.java:183)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)
>   at hudson.model.Run.execute(Run.java:1690)
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
>   at hudson.model.ResourceController.execute(ResourceController.java:88)
>   at hudson.model.Executor.run(Executor.java:230)
> Finished: FAILURE
> 
> Addittionally, I tried to launch pep8 check without using pytest, instead I 
> used this command for windows to find and check all .py files:
> 
> FOR /R %i IN (*.py) DO pep8 %i  1>>reports\pep8.log 
> 
> In this case, I get the following:
> 
> C:\Jenkins\jobs\python-template-2\workspace>exit 1 
> Build step 'Выполнить команду Windows' marked build as failure
> ERROR: Publisher hudson.plugins.violations.ViolationsPublisher aborted due to 
> exception
> java.io.FileNotFoundException: 
> C:\Jenkins\jobs\python-template-2\builds\2013-10-15_13-31-37\violations\file\C:\Jenkins\jobs\python-template-2\workspace\notifications\email.py.xml
>  (Syntax error in filename)
>   at java.io.FileOutputStream.open(Native Method)
>   at java.io.FileOutputStream.(Unknown Source)
>   at java.io.FileOutputStream.(Unknown Source)
>   at hudson.FilePath.write(FilePath.java:1666)
>   at 
> hudson.plugins.violations.generate.ExecuteFilePath.execute(ExecuteFilePath.java:40)
>   at 
> hudson.plugins.violations.generate.GenerateXML.execute(GenerateXML.java:47)
>   at 
> hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:122)
>   at 
> hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:25)
>   at hudson.FilePath.act(FilePath.java:916)
>   at hudson.FilePath.act(FilePath.java:889)
>   at 
> hudson.plugins.violations.ViolationsPublisher.perform(ViolationsPublisher.java:74)
>   at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:786)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:758)
>   at hudson.model.Build$BuildExecution.post2(Build.java:183)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:711)
>   at hudson.model.Run.execute(Run.java:1690)
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
>   at hudson.model.ResourceController.execute(ResourceController.java:88)
>   at hudson.model.Executor.run(Executor.java:246)
> 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 f

Violations plugin uses wrong path to find pep8 report

[Dmitry S]

I'm using pytest to run pep8 check:

py.test --pep8 --junitxml=reports\pep8.log

I setup a job to look for pep8.log file in reports\pep8.log

But when i run the job I see that the path where violations plugin looks 
for reports makes no sense:

generated xml file: 
C:\Jenkins\jobs\python-template-2\workspace\reports\pep8.log 
=== 89 failed, 33 skipped, 1 error in 1.48 seconds 

C:\Jenkins\jobs\python-template-2\workspace>exit 1 
Build step 'Выполнить команду Windows' marked build as failure
ERROR: Publisher hudson.plugins.violations.ViolationsPublisher aborted due to 
exception*java.io.FileNotFoundException 
: 
C:\Jenkins\jobs\python-template-2\builds\2013-10-22_13-30-44\violations\file\<\failure><\testcase>C:\Jenkins\jobs\python-template-2\workspace\contests\migrations\0003_auto__add_votinghistory.py.xml*
 (Синтаксическая ошибка в имени файла, имени папки или метке тома)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(Unknown Source)
at java.io.FileOutputStream.(Unknown Source)
at hudson.FilePath.write(FilePath.java:1642)
at 
hudson.plugins.violations.generate.ExecuteFilePath.execute(ExecuteFilePath.java:40)
at 
hudson.plugins.violations.generate.GenerateXML.execute(GenerateXML.java:47)
at 
hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:122)
at 
hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:25)
at hudson.FilePath.act(FilePath.java:912)
at hudson.FilePath.act(FilePath.java:885)
at 
hudson.plugins.violations.ViolationsPublisher.perform(ViolationsPublisher.java:74)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:753)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)
at hudson.model.Run.execute(Run.java:1690)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:230)
Finished: FAILURE


Addittionally, I tried to launch pep8 check without using pytest, instead I 
used this command for windows to find and check all .py files:

FOR /R %i IN (*.py) DO pep8 %i  1>>reports\pep8.log 


In this case, I get the following:


C:\Jenkins\jobs\python-template-2\workspace>exit 1 
Build step 'Выполнить команду Windows' marked build as failure
ERROR: Publisher hudson.plugins.violations.ViolationsPublisher aborted due to 
exception*java.io.FileNotFoundException 
: 
C:\Jenkins\jobs\python-template-2\builds\2013-10-15_13-31-37\violations\file\C:\Jenkins\jobs\python-template-2\workspace\notifications\email.py.xml
 (Syntax error in filename)*
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(Unknown Source)
at java.io.FileOutputStream.(Unknown Source)
at hudson.FilePath.write(FilePath.java:1666)
at 
hudson.plugins.violations.generate.ExecuteFilePath.execute(ExecuteFilePath.java:40)
at 
hudson.plugins.violations.generate.GenerateXML.execute(GenerateXML.java:47)
at 
hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:122)
at 
hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:25)
at hudson.FilePath.act(FilePath.java:916)
at hudson.FilePath.act(FilePath.java:889)
at 
hudson.plugins.violations.ViolationsPublisher.perform(ViolationsPublisher.java:74)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:786)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:758)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:711)
at hudson.model.Run.execute(Run.java:1690)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)
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: Jenkins : Add passphrase key to jenkins user for Git pull from jenkins job

[Stephen Connolly]

have you tried using the ssh-agent plugin?


On 22 October 2013 00:49, JonathanRRogers  wrote:

>
>
> On Monday, October 21, 2013 8:47:20 AM UTC-4, Mitul Parmar wrote:
>>
>> Hi,
>>
>> I am new to jenkins. I have created a job which tries to pull changes
>> from git repositories using ssh. I have created SSH key for the jenkins
>> user and I am able to do "ls-remote -h ssh://git@myhost/repo.git" 
>> successfully.
>> I have set all the required parameter for Git plugin. However I am confused
>> regarding how to pass the "PASSPHRASE KEY" for pulling the changes from my
>> Git Repositories. (There is only one protocol supported in my Git
>> Repository i.e. SSH with authentication). Has anybody passed a PASSPHRASE
>> KEY for pulling the changes from Git Repositories using Jenkins job ?
>>
>> Any help will be appriciated. Thanks in advance.
>>
>>  If you must configure public key SSH authentication to work unattended,
> it's a lot easier to simply store the private key unencrypted than to store
> the passphrase. If you store the passphrase, there's little point to
> encrypting the private key any way. This HOWTO will help you change the
> passphrase. If you don't provide a passphrase, the private key will simply
> be stored unencrypted.
>
>  https://wiki.archlinux.org/index.php/SSH_Keys#Changing_the_private_key.27s_passphrase_without_changing_the_key
> >
>
> --
> 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.
>

-- 
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.

Jenkins reports a different ruby version than what is installed on build server

[Maneesh M P]

If I check the version of ruby by logging into build server, I get the 
version as 1.9.3

ruby --version
ruby 1.9.3p448 (2013-06-27 revision 41675) [x86_64-linux]

But if I execute ruby --version through "execute shell" option in jenkins, 
I get a different ruby version.

[xyz-abc] $ /bin/bash -xe /tmp/hudson2192021507907867383.sh
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]


I even tried exporting the ruby path which I have in build server, but still 
jenkins reports a different version.

Can anyone help? :(


Thanks,

M


-- 
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.