Re: Jenkins : Add passphrase key to jenkins user for Git pull from jenkins job

[JonathanRRogers]

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.

Re: Using perforce Workspace name in the perforce plugin

[D Soa]

I have a followup question.  I read the help text, but am still confused at 
what the settings mean.

I have multiple jobs that need to work off the same client view spec and I 
want Jenkins to create/manage a separate workspace for each job.  But I 
want the "view spec" to be based off an existing Perforce workspace so I 
don't have to maintain the view spec settings in multiple jobs.

What are the proper settings to accomplish this?

Thanks.



-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

System Groovy script HELP

[Jeff]

I have a groovy script that reads the MAVEN_VERSION in a "Pre Step" from
the job/project and sets an environment variable.

>From the job description of "execute system Groovy script" it states:

Executes a system groovy script similarly to *hudson_url*/script. The
script is *always* executed on master.


I take that to mean that if a job is run on a slave, the script would still
run on the master, however if it does get run on the master it really
doesn't help because the environment of the slave never gets the value
output from the system script.

Is there a way I can get the maven version of a project set in the job
environment without limiting where it can run?

-- 
Jeff Vincent
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent

-- 
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-build action (editable email notification)

[Ramin Rad]

Awesome! In the Editable Email Notification box, I clicked on Advanced
Settings and added a trigger for SUCCESS. It worked as you suggested.

Thanks,
-ramin



On Mon, Oct 21, 2013 at 1:06 PM, Slide  wrote:

> Someone already issued a pull request to fix this issue and I merged it. I
> have not done a release yet. Please try configuring triggers, that should
> workaround the issue.
>
>
> On Mon, Oct 21, 2013 at 9:28 AM, Ramin Rad  wrote:
>
>> Greetings,
>>
>> I am adding a Post-Build action (Editable Email Notification) and I am
>> attaching a log file to this attachment but I get the following exception.
>> Per error log below, I am reporting this as a defect.
>>
>> The build succeeds without the post-build action.
>>
>> Version of Jenkins: Jenkins ver. 1.535
>>
>>
>> Thanks,
>>
>> -ramin
>>
>>
>> Started by user anonymous
>>
>> Building in workspace 
>>
>> Checkout:workspace /  -
>> hudson.remoting.LocalChannel@7bdf6ed6
>>
>> Using strategy: Default
>>
>> Last Built Revision: Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8
>> (origin/HEAD, origin/master)
>>
>> Fetching changes from 1 remote Git repository
>>
>> Fetching upstream changes from origin
>>
>> Seen branch in repository origin/HEAD
>>
>> Seen branch in repository origin/master
>>
>> Seen 2 remote branches
>>
>> Commencing build of Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8
>> (origin/HEAD, origin/master)
>>
>> Checking out Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8
>> (origin/HEAD, origin/master)
>>
>> Warning : There are multiple branch changesets here
>>
>> ERROR: Processing failed due to a bug in the code. Please report this to
>> jenkinsci-users@googlegroups.com
>>
>> java.lang.NullPointerException
>>
>> at
>> hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:242)
>>
>> 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:246)
>>
>> project=hudson.maven.MavenModuleSet@69f070e8[TommyWeb]
>>
>> project.getModules()=[hudson.maven.MavenModule@6db17b38
>> [TommyWeb/TommyWeb:TommyWeb][TommyWeb/TommyWeb:TommyWeb][relativePath:TommyWeb]]
>>
>> project.getRootModule()=hudson.maven.MavenModule@6db17b38
>> [TommyWeb/TommyWeb:TommyWeb][TommyWeb/TommyWeb:TommyWeb][relativePath:TommyWeb]
>>
>> FATAL: null
>>
>> java.lang.NullPointerException
>>
>> at
>> hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:242)
>>
>> 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:246)
>>
>> --
>> 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 a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/R9IsR2RwLDM/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 th

Re: post-build action (editable email notification)

[Slide]

Someone already issued a pull request to fix this issue and I merged it. I
have not done a release yet. Please try configuring triggers, that should
workaround the issue.


On Mon, Oct 21, 2013 at 9:28 AM, Ramin Rad  wrote:

> Greetings,
>
> I am adding a Post-Build action (Editable Email Notification) and I am
> attaching a log file to this attachment but I get the following exception.
> Per error log below, I am reporting this as a defect.
>
> The build succeeds without the post-build action.
>
> Version of Jenkins: Jenkins ver. 1.535
>
>
> Thanks,
>
> -ramin
>
>
> Started by user anonymous
>
> Building in workspace 
>
> Checkout:workspace /  -
> hudson.remoting.LocalChannel@7bdf6ed6
>
> Using strategy: Default
>
> Last Built Revision: Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8
> (origin/HEAD, origin/master)
>
> Fetching changes from 1 remote Git repository
>
> Fetching upstream changes from origin
>
> Seen branch in repository origin/HEAD
>
> Seen branch in repository origin/master
>
> Seen 2 remote branches
>
> Commencing build of Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8
> (origin/HEAD, origin/master)
>
> Checking out Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8
> (origin/HEAD, origin/master)
>
> Warning : There are multiple branch changesets here
>
> ERROR: Processing failed due to a bug in the code. Please report this to
> jenkinsci-users@googlegroups.com
>
> java.lang.NullPointerException
>
> at
> hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:242)
>
> 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:246)
>
> project=hudson.maven.MavenModuleSet@69f070e8[TommyWeb]
>
> project.getModules()=[hudson.maven.MavenModule@6db17b38
> [TommyWeb/TommyWeb:TommyWeb][TommyWeb/TommyWeb:TommyWeb][relativePath:TommyWeb]]
>
> project.getRootModule()=hudson.maven.MavenModule@6db17b38
> [TommyWeb/TommyWeb:TommyWeb][TommyWeb/TommyWeb:TommyWeb][relativePath:TommyWeb]
>
> FATAL: null
>
> java.lang.NullPointerException
>
> at
> hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:242)
>
> 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:246)
>
> --
> 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.

Re: Warnings Plugin MSBuild Parser detection of Visual Studio Code Analysis Warnings

[Mike Hambidge]

Thanks for the response Ulli. I've created 
JENKINS-20154to track this.

- Mike

On Sunday, October 20, 2013 10:03:40 AM UTC-5, Ullrich Hafner wrote:
>
> Yes, it should work on Visual Studio messages, too. Please file a new bug 
> report, it should be quite easy to fix.
>
> Ulli 
>
> Am Samstag, 19. Oktober 2013 schrieb Mike Hambidge :
>
>> Does anyone know if the MSBuild parser for the Warnings Plugin is 
>> supposed to detection Visual Studio Code Analysis warnings? The reason I 
>> ask is that I've encountered a problem where the console output for code 
>> analysis warnings contains an extra space character that causes the regex 
>> used within the MSBuild parser to not match.
>>
>> Typically, the various warnings from MSBuild (actual msbuild warnings, 
>> StyleCop warnings, etc) include text in the format:
>>
>> ... warning: : Message
>>
>> Where ID is something like "SA1234" for a StyleCop warnings. But the 
>> Visual Studio Code Analysis output has an extra space after the , so 
>> looks like
>>
>> ... warning: CA1234 : Message
>>
>> I suppose I may be encountering a bug, but before creating a bug report I 
>> was trying to see if the MSBuild parser was even intended to catch the code 
>> analysis warnings.
>>
>> Thanks gang.
>>
>> - Mike
>>
>> -- 
>> 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: post-build action (editable email notification)

[Ramin Rad]

Jenkins Email Extension Plugin 2.35.1.



On Mon, Oct 21, 2013 at 12:30 PM, Slide  wrote:

> What version of email-ext?
>
>
> On Mon, Oct 21, 2013 at 9:28 AM, Ramin Rad  wrote:
>
>> Greetings,
>>
>> I am adding a Post-Build action (Editable Email Notification) and I am
>> attaching a log file to this attachment but I get the following exception.
>> Per error log below, I am reporting this as a defect.
>>
>> The build succeeds without the post-build action.
>>
>> Version of Jenkins: Jenkins ver. 1.535
>>
>>
>> Thanks,
>>
>> -ramin
>>
>>
>> Started by user anonymous
>>
>> Building in workspace 
>>
>> Checkout:workspace /  -
>> hudson.remoting.LocalChannel@7bdf6ed6
>>
>> Using strategy: Default
>>
>> Last Built Revision: Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8
>> (origin/HEAD, origin/master)
>>
>> Fetching changes from 1 remote Git repository
>>
>> Fetching upstream changes from origin
>>
>> Seen branch in repository origin/HEAD
>>
>> Seen branch in repository origin/master
>>
>> Seen 2 remote branches
>>
>> Commencing build of Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8
>> (origin/HEAD, origin/master)
>>
>> Checking out Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8
>> (origin/HEAD, origin/master)
>>
>> Warning : There are multiple branch changesets here
>>
>> ERROR: Processing failed due to a bug in the code. Please report this to
>> jenkinsci-users@googlegroups.com
>>
>> java.lang.NullPointerException
>>
>> at
>> hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:242)
>>
>> 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:246)
>>
>> project=hudson.maven.MavenModuleSet@69f070e8[TommyWeb]
>>
>> project.getModules()=[hudson.maven.MavenModule@6db17b38
>> [TommyWeb/TommyWeb:TommyWeb][TommyWeb/TommyWeb:TommyWeb][relativePath:TommyWeb]]
>>
>> project.getRootModule()=hudson.maven.MavenModule@6db17b38
>> [TommyWeb/TommyWeb:TommyWeb][TommyWeb/TommyWeb:TommyWeb][relativePath:TommyWeb]
>>
>> FATAL: null
>>
>> java.lang.NullPointerException
>>
>> at
>> hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:242)
>>
>> 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:246)
>>
>> --
>> 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 a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/R9IsR2RwLDM/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: Restrict where this project can be run - extra options?

[Les Mikesell]

On Fri, Oct 18, 2013 at 3:55 AM, Tânia Magalhães
 wrote:
>
> Does anyone know if it is possible to define an order of preference for the
> choice of the node that will do the build?
>
> For example: if there are the nodes A, B and C and I want a particular job
> to run in A, or B, or C in this order of preference, how can I do it?
>
> This is relevant if at certain point the best node to build the job is
> offline and I want the job to be build anyway even if the only available
> node is the worst for this task.

I don't think that is possible.  You can (and usually should) apply a
label to a set of nodes and restrict builds to nodes with that label,
but the only preference ordering within the group is that jenkins will
use the node that did the last build if it is available - otherwise, I
think it picks at random from the others with the specified label.

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

Re: post-build action (editable email notification)

[Slide]

What version of email-ext?


On Mon, Oct 21, 2013 at 9:28 AM, Ramin Rad  wrote:

> Greetings,
>
> I am adding a Post-Build action (Editable Email Notification) and I am
> attaching a log file to this attachment but I get the following exception.
> Per error log below, I am reporting this as a defect.
>
> The build succeeds without the post-build action.
>
> Version of Jenkins: Jenkins ver. 1.535
>
>
> Thanks,
>
> -ramin
>
>
> Started by user anonymous
>
> Building in workspace 
>
> Checkout:workspace /  -
> hudson.remoting.LocalChannel@7bdf6ed6
>
> Using strategy: Default
>
> Last Built Revision: Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8
> (origin/HEAD, origin/master)
>
> Fetching changes from 1 remote Git repository
>
> Fetching upstream changes from origin
>
> Seen branch in repository origin/HEAD
>
> Seen branch in repository origin/master
>
> Seen 2 remote branches
>
> Commencing build of Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8
> (origin/HEAD, origin/master)
>
> Checking out Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8
> (origin/HEAD, origin/master)
>
> Warning : There are multiple branch changesets here
>
> ERROR: Processing failed due to a bug in the code. Please report this to
> jenkinsci-users@googlegroups.com
>
> java.lang.NullPointerException
>
> at
> hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:242)
>
> 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:246)
>
> project=hudson.maven.MavenModuleSet@69f070e8[TommyWeb]
>
> project.getModules()=[hudson.maven.MavenModule@6db17b38
> [TommyWeb/TommyWeb:TommyWeb][TommyWeb/TommyWeb:TommyWeb][relativePath:TommyWeb]]
>
> project.getRootModule()=hudson.maven.MavenModule@6db17b38
> [TommyWeb/TommyWeb:TommyWeb][TommyWeb/TommyWeb:TommyWeb][relativePath:TommyWeb]
>
> FATAL: null
>
> java.lang.NullPointerException
>
> at
> hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:242)
>
> 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:246)
>
> --
> 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.

svn:external *files* not polled

[Ronny Schuetz]

Hi,

I'm running Jenkins 1.509.4 with Subversion plugin 1.53. I've some SVN 
directories defined in a project, that contain svn:externals definitions to 
directories as well as to files, all relative to the current SVN server 
(^/trunk/ ...). When the plugin polls the repository for changes, it indeed 
detects changes of the linked directories, but it doesn't detect changes of 
the linked files. Is there any workaround to fix that?

Best regards,
Ronny


-- 
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-build action (editable email notification)

[Ramin Rad]

Greetings,

I am adding a Post-Build action (Editable Email Notification) and I am 
attaching a log file to this attachment but I get the following exception. 
Per error log below, I am reporting this as a defect.

The build succeeds without the post-build action.

Version of Jenkins: Jenkins ver. 1.535


Thanks,

-ramin


Started by user anonymous

Building in workspace 

Checkout:workspace /  - 
hudson.remoting.LocalChannel@7bdf6ed6

Using strategy: Default

Last Built Revision: Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8 
(origin/HEAD, origin/master)

Fetching changes from 1 remote Git repository

Fetching upstream changes from origin

Seen branch in repository origin/HEAD

Seen branch in repository origin/master

Seen 2 remote branches

Commencing build of Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8 
(origin/HEAD, origin/master)

Checking out Revision fd448ff7ae7cccaddba9112129f13a1db85df3d8 
(origin/HEAD, origin/master)

Warning : There are multiple branch changesets here

ERROR: Processing failed due to a bug in the code. Please report this to 
jenkinsci-users@googlegroups.com

java.lang.NullPointerException

at 
hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:242)

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

project=hudson.maven.MavenModuleSet@69f070e8[TommyWeb]

project.getModules()=[hudson.maven.MavenModule@6db17b38[TommyWeb/TommyWeb:TommyWeb][TommyWeb/TommyWeb:TommyWeb][relativePath:TommyWeb]]

project.getRootModule()=hudson.maven.MavenModule@6db17b38[TommyWeb/TommyWeb:TommyWeb][TommyWeb/TommyWeb:TommyWeb][relativePath:TommyWeb]

FATAL: null

java.lang.NullPointerException

at 
hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:242)

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

-- 
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 resolve the RDC issue when GUI Testing on a windows Jenkins agent

[Kelvin Lei]

I have a jenkins agent set up on window 7 and a jenkins server on Linux. I am
running GUI testing on the windows agent. It runs fine if I have a remote
desktop connection connected to it, but fails otherwise. I found this link,
http://stackoverflow.com/questions/10177708/jenkins-on-windows-and-gui-tests-without-rdc

But the solution provided there is pretty vague.. It seems like the only
solution is to somehow make Jenkins server to have a remote desktop
connection open at all times. But I can't find such an option to do so. 
Could anyone please clearly teach me how to solve this issue? 

Much appreciated!



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/How-to-resolve-the-RDC-issue-when-GUI-Testing-on-a-windows-Jenkins-agent-tp4679065.html
Sent from the Jenkins users mailing list archive at Nabble.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to resolve the RDC issue when GUI Testing on a windows Jenkins agent

[Kelvin Lei]

It's connected via Java Web Start btw



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/How-to-resolve-the-RDC-issue-when-GUI-Testing-on-a-windows-Jenkins-agent-tp4679065p4679100.html
Sent from the Jenkins users mailing list archive at Nabble.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

RE: CLI command failing since Friday 10/18/13

[Ginga, Dick]

I think I might have found the issue. I "think" I was trying to force run a job 
that was waiting for an executor on the master. The master had 2 hung jobs.

From: Ginga, Dick
Sent: Monday, October 21, 2013 9:34 AM
To: jenkinsci-users@googlegroups.com
Subject: CLI command failing since Friday 10/18/13

I have a job that runs one jenkins cli command. It was working before 12 PM EST 
10/18/13.

@echo #
@echo # set the build display name
@echo #

java -jar \Jenkins\jenkins-cli.jar -s http://dilithium.perkinelmer.net:8082/ 
set-build-display-name %JOB_TO_LABEL% %BUILD_TO_LABEL% %DISPLAY_NAME%

Now each invocation produces this:

Description: Unable to locate the server named "wiki.jenkins-ci.org" --- the 
server does not have a DNS entry. Perhaps there is a misspelling in the server 
name, or the server no longer exists. Double-check the name and try again.

I can ping the wiki server from the master where this job runs and I can browse 
to it. It appears that after attempting to run, it gets re-queued

Dick Ginga, Informatics R&D
PerkinElmer Inc. | For the Better
HUMAN HEALTH | ENVIRONMENTAL HEALTH
940 Winter Street, Waltham MA 02451

dick.gi...@perkinelmer.com
Mobile - 508-847-1434
Office - 781-663-6947

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

CLI command failing since Friday 10/18/13

[Ginga, Dick]

I have a job that runs one jenkins cli command. It was working before 12 PM EST 
10/18/13.

@echo #
@echo # set the build display name
@echo #

java -jar \Jenkins\jenkins-cli.jar -s http://dilithium.perkinelmer.net:8082/ 
set-build-display-name %JOB_TO_LABEL% %BUILD_TO_LABEL% %DISPLAY_NAME%

Now each invocation produces this:

Description: Unable to locate the server named "wiki.jenkins-ci.org" --- the 
server does not have a DNS entry. Perhaps there is a misspelling in the server 
name, or the server no longer exists. Double-check the name and try again.

I can ping the wiki server from the master where this job runs and I can browse 
to it. It appears that after attempting to run, it gets re-queued

Dick Ginga, Informatics R&D
PerkinElmer Inc. | For the Better
HUMAN HEALTH | ENVIRONMENTAL HEALTH
940 Winter Street, Waltham MA 02451

dick.gi...@perkinelmer.com
Mobile - 508-847-1434
Office - 781-663-6947


-- 
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 : Add passphrase key to jenkins user for Git pull from jenkins job

[Mitul Parmar]

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.

-- 
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: Double-builds, if any SCM change while first build ist still running

[Michael Clarke]

JENKINS-19314 describes your issue. I have a change sitting on my machine
which should fix your issue, but I still need to push it to Git.

I aim to release a new version of the CVS plugin later this week which will
therefore fix your issue.

Thanks
Michael

On 21 Oct 2013, at 12:54, Horst Krause  wrote:

Hi.

After we added many more integration tests to our project the build now
runs about 20 minutes instead of 10 before. This causes jenkins to always
run 2 builds for 1 SCM change, because the build is still running when SCM
poll next time in his interval.

In Detail:

Scenario: SCM polling interval is smaller than build duration. e.g. polling
intervall 15min, build duration about 20 min

My observations are:
Build #1

Started on 14.10.2013 18:30:50
Using locally configured password for connection to :pserver:jenkins@...
cvs rlog -S -d14 Oct 2013 18:06:57 +0200<14 Oct 2013 18:30:50 +0200 my_project
Done. Took 1,6 Sekunden
Changes found


This is ok, there are changes which are also shown in the changeset, build
is started and will go until

[INFO] Total time: 20 minutes 25 seconds
[INFO] Finished at: Mon Oct 14 18:51:50 CEST 2013
[INFO] Final Memory: 90M/220M


Now what about the next build?

Build #2

Started on 14.10.2013 18:45:50
Using locally configured password for connection to :pserver:jenkins@...
cvs rlog -S -d14 Oct 2013 18:06:57 +0200<14 Oct 2013 18:45:50 +0200 my_project
Done. Took 1,5 Sekunden
Changes found


As you can see, the CVS poll is done exactly in the configured polling
intervall, 15min later. So far ok.

But the cvs command uses the timestamp "Oct 2013 18:06:57" which is the
same as for build#1. I think this causes the second poll to find the same
changes as the first poll.

The real build then starts later, one second after the first build is
finished:

Build wurde durch eine SCM-Änderung ausgelöst.
Baue auf Slave prod01 in workspace /var/jenkins/workspace/my_project
Using locally configured password for connection to :pserver:jenkins@...
cvs checkout -P -D 14 Oct 2013 18:51:53 +0200 -d MZV-Online
Sportdatenbank my_project
Using locally configured password for connection to :pserver:jenkins@...
cvs rlog -S -d14 Oct 2013 18:30:52 +0200<14 Oct 2013 18:51:51 +0200 my_project


At the start of the build, SCM is polled again, but not with the newer
timestamp "Oct 2013 18:30:52" to get only changes after the scm poll of the
first build. The result is, that for the second build it says
a) Build was triggered by scm changes
and
b) no changes

So in the end, we always get two builds for each SCM change.
I think this could be fixed, if the initial SCM poll of the second build
uses the timestamp "Oct 2013 18:30:52" and not "Oct 2013 18:06:57"

But I don't know how to change this behaviour. Would be nice to get any
help.

Bye,
 Horst

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

Double-builds, if any SCM change while first build ist still running

[Horst Krause]

Hi.

After we added many more integration tests to our project the build now 
runs about 20 minutes instead of 10 before. This causes jenkins to always 
run 2 builds for 1 SCM change, because the build is still running when SCM 
poll next time in his interval.

In Detail:

Scenario: SCM polling interval is smaller than build duration. e.g. polling 
intervall 15min, build duration about 20 min 

My observations are: 
Build #1 

Started on 14.10.2013 18:30:50
Using locally configured password for connection to :pserver:jenkins@...
cvs rlog -S -d14 Oct 2013 18:06:57 +0200<14 Oct 2013 18:30:50 +0200 my_project
Done. Took 1,6 Sekunden
Changes found


This is ok, there are changes which are also shown in the changeset, build 
is started and will go until 

[INFO] Total time: 20 minutes 25 seconds
[INFO] Finished at: Mon Oct 14 18:51:50 CEST 2013
[INFO] Final Memory: 90M/220M


Now what about the next build? 

Build #2 

Started on 14.10.2013 18:45:50
Using locally configured password for connection to :pserver:jenkins@...
cvs rlog -S -d14 Oct 2013 18:06:57 +0200<14 Oct 2013 18:45:50 +0200 my_project
Done. Took 1,5 Sekunden
Changes found


As you can see, the CVS poll is done exactly in the configured polling 
intervall, 15min later. So far ok. 

But the cvs command uses the timestamp "Oct 2013 18:06:57" which is the 
same as for build#1. I think this causes the second poll to find the same 
changes as the first poll. 

The real build then starts later, one second after the first build is 
finished: 

Build wurde durch eine SCM-Änderung ausgelöst.
Baue auf Slave prod01 in workspace /var/jenkins/workspace/my_project
Using locally configured password for connection to :pserver:jenkins@...
cvs checkout -P -D 14 Oct 2013 18:51:53 +0200 -d MZV-Online Sportdatenbank 
my_project
Using locally configured password for connection to :pserver:jenkins@...
cvs rlog -S -d14 Oct 2013 18:30:52 +0200<14 Oct 2013 18:51:51 +0200 my_project


At the start of the build, SCM is polled again, but not with the newer 
timestamp "Oct 2013 18:30:52" to get only changes after the scm poll of the 
first build. The result is, that for the second build it says 
a) Build was triggered by scm changes 
and 
b) no changes 

So in the end, we always get two builds for each SCM change. 
I think this could be fixed, if the initial SCM poll of the second build 
uses the timestamp "Oct 2013 18:30:52" and not "Oct 2013 18:06:57"

But I don't know how to change this behaviour. Would be nice to get any 
help.

Bye,
 Horst

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

Disable maven automatic archving for Maven jobs

[Aswini Rajasekaran]

Hi,

I am using some maven jobs for doing certain builds. The pom and war files 
got automatically archived at the end of the builds, I disabled it by 
checking the box Disable automatic maven archiving.
Though it disables the archiving/copy part, I get messages as 

[JENKINS] Archiving disabled 
which consumes lot of time. Is there any way in blocking these messages and let 
Maven know that it doesn't have to check for archiving at all?

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.

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

[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.schill...@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:k...@quipsy.de
An: jenkinsci-users@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:   jenkinsci-users@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-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.