Re: Error from Gradle Plug-in retrieving gradle executable

[Kuldeep singh]

Hi Matt,
I am facing same problem, did you find out some solution for it?

Kuldeep

On Tuesday, April 16, 2013 5:36:56 AM UTC+5:30, Matt Zimmer wrote:
>
> Hello all,
>
> A gradle build of mine started failing mid-day today after succeeding 
> earlier in the day (and for the past few months).
>
> There were no changes to the build.gradle or the Jenkins job today.
>
> The error message reads:
>
> *00:03:20* Cleaning workspace*00:03:20* Resetting working tree*00:03:20* 
> [Gradle] - Launching build.*00:03:20* Unpacking 
> http://archive.apache.org/dist/ant/binaries/jakarta-ant-1.3-bin.zip to 
> /var/lib/jenkins_ci/tools/hudson.plugins.gradle.GradleInstallation/Gradle_1.3 
> on MrSlave*00:03:22* [Gradle] - [ERROR] Can't retrieve the Gradle 
> executable.*00:03:22* Build step 'Invoke Gradle script' marked build as 
> failure*00:03:22* [htmlpublisher] Archiving HTML reports...
>
>
> Is the Ant log message expected?
>
> When I look on the node where this job builds, there are only Ant related 
> files in 'hudson.plugins.gradle.GradleInstallation/Gradle_1.3' and no 
> gradle scripts or jars.
>
> Versions:
> Jenkins: 1.510
> Gradle Plugin: 1.22 (also happens with 1.21)
>
> Any insight will be appreciated.
>
> Thanks,
> Matt
>
>
>

-- 
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/d/optout.

Re: Frustration with build-step/post-build-action access...

[Jeff]

Thanks...that's what I am trying to do.  I have successfully copied the
artifacts.  Now I need to SCP them to the server BEFORE I run a remote SSH
script to install them.

Using the SCP plugin would help me not have to manually manage credentials
in the job or risk exposing them in the logs (am going to investigate other
ways per Daniel's comment) but the SCP plugin step is currently only
available in a post-build action so I am unable to use it to copy the files
before attempting to install them.

I could (and may still) write a local SSH script that simply calls SCP but
I'm unsure how to manage credentials securely and still use them in scripts
(again, still investigating).



On Wed, Jul 9, 2014 at 10:50 PM, Baskar Veeramani (baveeram) <
bavee...@cisco.com> wrote:

>  Jeff, we are managing similar requirement by configuring the post build
> steps as an separate downstream job which triggers automatically when the
> actual build completes. Copy artifact plugin (Copy artifacts from another
> project) is used to copy the artifact from build job to downstream job.
>
>
>
> Regards,
>
> Baskar.V
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Jeff
> *Sent:* Thursday, July 10, 2014 10:09 AM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: Frustration with build-step/post-build-action access...
>
>
>
> I wouldn't call it "misusing".  I'm simply working with what is there
> (that I knew about).  Since I can't do SSH in post-build I am limited to
> what I can do, hence my frustration.  With the emergence of Continuous
> Delivery/Deployment, I wish a job could be defined more broadly and tasks
> or steps within a job more fluidly to include any step in any order without
> having to resort to writing/installing all sorts of plugins or having to
> fence an operation to an explicit "type" of job or build phase.
>
>
>
> As for the current job definition I've been working with, I would likely
> do more things in a post-build action if I were allowed to, thus the point
> of my frustration.  I missed the "Any Build Step Plugin" but I will
> definitely give it a try.
>
>
>
> As for using environment variables to handle user/passwords, does that
> allow restricted access, including obfuscation in build logs?  I'm unaware
> of the mechanism for managing/obfuscating users/passwords in a secure way
> outside of using the plugins.  I'll look into that as well.
>
>
>
> Thanks for the feedback and I'm looking forward to trying the Workflow
> plugin.  Is there any information or designs I can look at?
>
>
>
>
>
> On Wed, Jul 9, 2014 at 5:21 PM, Daniel Beck  wrote:
>
> Your problem is that you're misusing the 'software build' concept and job
> type for something that isn't strictly a software build, and its
> limitations become obvious.
>
> Post-build steps usually fall into one of the categories 'recorder' (e.g.
> archive artifacts) and 'notifier' (email notifications), things that
> usually don't make sense before the actual work is done. I expect that very
> few actual build scripts need to SCP right in the middle, at least compared
> to those that upload things somewhere when they're finished. So that's what
> the plugin author decided should be the supported use case, and the reason
> you have difficulty achieving what you want.
>
> When I try do something like this, I usually try to get all the basic
> functionality going from a shell/batch script so it's usable outside
> Jenkins if there's a need to, reducing Jenkins to a fancy scheduler, log
> archiver and notifier. Passwords are provided by Jenkins as environment
> variables, SSH keys are stored on the slaves. Versioning of configuration
> is easier that way, and the job configurations don't become too complex.
>
> That said, have you tried Any Build Step Plugin? It might allow you to do
> what you want to achieve.
>
> The upcoming Workflow plugin probably also has the required flexibility of
> combining steps more flexibly in its job type.
>
>
> On 10.07.2014, at 00:53, Jeff  wrote:
>
> > This is a bit of a rant, but I'm unclear why it matters which steps are
> available as a build step vs. a post-build step.
> >
> > I'm trying to create a simple job to grab debian packages archived from
> various upstream "build" jobs and installing/configuring the debian
> packages on a set of test servers as part of an "install" job.
> >
> > The "Install job" sequence would be:
>
> >   * Copy artifacts from previous jobs
> >   * SCP them to the specified server(s)
> >   * Run the installers via SSH
> >   * Update configuration
>
> > However, I am unable to use the Jenkins plugins to do step 2 and 3 in
> the proper order because the "Publish artifacts to SCP Repository" plugin
> option is not available as a "build step" and "Execute shell script on
> remote host using ssh" plugin as it's not available as a "post-build
> action".  (chicken or egg paradox).
> >
> > The motivation to use these plugins is to 

RE: Frustration with build-step/post-build-action access...

[Baskar Veeramani (baveeram)]

Jeff, we are managing similar requirement by configuring the post build steps 
as an separate downstream job which triggers automatically when the actual 
build completes. Copy artifact plugin (Copy artifacts from another project) is 
used to copy the artifact from build job to downstream job.

Regards,
Baskar.V
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jeff
Sent: Thursday, July 10, 2014 10:09 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Frustration with build-step/post-build-action access...

I wouldn't call it "misusing".  I'm simply working with what is there (that I 
knew about).  Since I can't do SSH in post-build I am limited to what I can do, 
hence my frustration.  With the emergence of Continuous Delivery/Deployment, I 
wish a job could be defined more broadly and tasks or steps within a job more 
fluidly to include any step in any order without having to resort to 
writing/installing all sorts of plugins or having to fence an operation to an 
explicit "type" of job or build phase.

As for the current job definition I've been working with, I would likely do 
more things in a post-build action if I were allowed to, thus the point of my 
frustration.  I missed the "Any Build Step Plugin" but I will definitely give 
it a try.

As for using environment variables to handle user/passwords, does that allow 
restricted access, including obfuscation in build logs?  I'm unaware of the 
mechanism for managing/obfuscating users/passwords in a secure way outside of 
using the plugins.  I'll look into that as well.

Thanks for the feedback and I'm looking forward to trying the Workflow plugin.  
Is there any information or designs I can look at?


On Wed, Jul 9, 2014 at 5:21 PM, Daniel Beck 
mailto:m...@beckweb.net>> wrote:
Your problem is that you're misusing the 'software build' concept and job type 
for something that isn't strictly a software build, and its limitations become 
obvious.

Post-build steps usually fall into one of the categories 'recorder' (e.g. 
archive artifacts) and 'notifier' (email notifications), things that usually 
don't make sense before the actual work is done. I expect that very few actual 
build scripts need to SCP right in the middle, at least compared to those that 
upload things somewhere when they're finished. So that's what the plugin author 
decided should be the supported use case, and the reason you have difficulty 
achieving what you want.

When I try do something like this, I usually try to get all the basic 
functionality going from a shell/batch script so it's usable outside Jenkins if 
there's a need to, reducing Jenkins to a fancy scheduler, log archiver and 
notifier. Passwords are provided by Jenkins as environment variables, SSH keys 
are stored on the slaves. Versioning of configuration is easier that way, and 
the job configurations don't become too complex.

That said, have you tried Any Build Step Plugin? It might allow you to do what 
you want to achieve.

The upcoming Workflow plugin probably also has the required flexibility of 
combining steps more flexibly in its job type.

On 10.07.2014, at 00:53, Jeff 
mailto:predato...@gmail.com>> wrote:

> This is a bit of a rant, but I'm unclear why it matters which steps are 
> available as a build step vs. a post-build step.
>
> I'm trying to create a simple job to grab debian packages archived from 
> various upstream "build" jobs and installing/configuring the debian packages 
> on a set of test servers as part of an "install" job.
>
> The "Install job" sequence would be:
>   * Copy artifacts from previous jobs
>   * SCP them to the specified server(s)
>   * Run the installers via SSH
>   * Update configuration
> However, I am unable to use the Jenkins plugins to do step 2 and 3 in the 
> proper order because the "Publish artifacts to SCP Repository" plugin option 
> is not available as a "build step" and "Execute shell script on remote host 
> using ssh" plugin as it's not available as a "post-build action".  (chicken 
> or egg paradox).
>
> The motivation to use these plugins is to help manage the hosts/passwords 
> required to use SCP/SSH.
>
> Thus, the question is ... why does Jenkins need to differentiate between a 
> build step and a post-build action?  Why not allow a mix of any type of 
> operation/step, regardless if it's type?
>
> It seems job creation flexibility would be enhanced if all tasks could be 
> used, particularly for jobs that don't really do builds (in the traditional 
> sense) such as creating a "pipeline" of phases/steps (continuous delivery, 
> etc.) deploy-dev  --> functional test --> deploy-staging --> integration test 
> --> deliver release candidate.
>
> Has there been consideration around allowing any step to be added in any 
> order?
>
> --
> Jeff Vincent
> See my LinkedIn profile at:
> http://www.linkedin.com/in/rjeffreyvincent
>
> --
> You received this message because you are subscribed to the Google Gro

Re: Frustration with build-step/post-build-action access...

[Jeff]

I wouldn't call it "misusing".  I'm simply working with what is there (that
I knew about).  Since I can't do SSH in post-build I am limited to what I
can do, hence my frustration.  With the emergence of Continuous
Delivery/Deployment, I wish a job could be defined more broadly and tasks
or steps within a job more fluidly to include any step in any order without
having to resort to writing/installing all sorts of plugins or having to
fence an operation to an explicit "type" of job or build phase.

As for the current job definition I've been working with, I would likely do
more things in a post-build action if I were allowed to, thus the point of
my frustration.  I missed the "Any Build Step Plugin" but I will definitely
give it a try.

As for using environment variables to handle user/passwords, does that
allow restricted access, including obfuscation in build logs?  I'm unaware
of the mechanism for managing/obfuscating users/passwords in a secure way
outside of using the plugins.  I'll look into that as well.

Thanks for the feedback and I'm looking forward to trying the Workflow
plugin.  Is there any information or designs I can look at?



On Wed, Jul 9, 2014 at 5:21 PM, Daniel Beck  wrote:

> Your problem is that you're misusing the 'software build' concept and job
> type for something that isn't strictly a software build, and its
> limitations become obvious.
>
> Post-build steps usually fall into one of the categories 'recorder' (e.g.
> archive artifacts) and 'notifier' (email notifications), things that
> usually don't make sense before the actual work is done. I expect that very
> few actual build scripts need to SCP right in the middle, at least compared
> to those that upload things somewhere when they're finished. So that's what
> the plugin author decided should be the supported use case, and the reason
> you have difficulty achieving what you want.
>
> When I try do something like this, I usually try to get all the basic
> functionality going from a shell/batch script so it's usable outside
> Jenkins if there's a need to, reducing Jenkins to a fancy scheduler, log
> archiver and notifier. Passwords are provided by Jenkins as environment
> variables, SSH keys are stored on the slaves. Versioning of configuration
> is easier that way, and the job configurations don't become too complex.
>
> That said, have you tried Any Build Step Plugin? It might allow you to do
> what you want to achieve.
>
> The upcoming Workflow plugin probably also has the required flexibility of
> combining steps more flexibly in its job type.
>
> On 10.07.2014, at 00:53, Jeff  wrote:
>
> > This is a bit of a rant, but I'm unclear why it matters which steps are
> available as a build step vs. a post-build step.
> >
> > I'm trying to create a simple job to grab debian packages archived from
> various upstream "build" jobs and installing/configuring the debian
> packages on a set of test servers as part of an "install" job.
> >
> > The "Install job" sequence would be:
> >   * Copy artifacts from previous jobs
> >   * SCP them to the specified server(s)
> >   * Run the installers via SSH
> >   * Update configuration
> > However, I am unable to use the Jenkins plugins to do step 2 and 3 in
> the proper order because the "Publish artifacts to SCP Repository" plugin
> option is not available as a "build step" and "Execute shell script on
> remote host using ssh" plugin as it's not available as a "post-build
> action".  (chicken or egg paradox).
> >
> > The motivation to use these plugins is to help manage the
> hosts/passwords required to use SCP/SSH.
> >
> > Thus, the question is ... why does Jenkins need to differentiate between
> a build step and a post-build action?  Why not allow a mix of any type of
> operation/step, regardless if it's type?
> >
> > It seems job creation flexibility would be enhanced if all tasks could
> be used, particularly for jobs that don't really do builds (in the
> traditional sense) such as creating a "pipeline" of phases/steps
> (continuous delivery, etc.) deploy-dev  --> functional test -->
> deploy-staging --> integration test --> deliver release candidate.
> >
> > Has there been consideration around allowing any step to be added in any
> order?
> >
> > --
> > 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/d/optout.
>
> --
> 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/d/optout.
>



-- 
Jeff Vincent
See 

Re: Frustration with build-step/post-build-action access...

[Daniel Beck]

Your problem is that you're misusing the 'software build' concept and job type 
for something that isn't strictly a software build, and its limitations become 
obvious.

Post-build steps usually fall into one of the categories 'recorder' (e.g. 
archive artifacts) and 'notifier' (email notifications), things that usually 
don't make sense before the actual work is done. I expect that very few actual 
build scripts need to SCP right in the middle, at least compared to those that 
upload things somewhere when they're finished. So that's what the plugin author 
decided should be the supported use case, and the reason you have difficulty 
achieving what you want.

When I try do something like this, I usually try to get all the basic 
functionality going from a shell/batch script so it's usable outside Jenkins if 
there's a need to, reducing Jenkins to a fancy scheduler, log archiver and 
notifier. Passwords are provided by Jenkins as environment variables, SSH keys 
are stored on the slaves. Versioning of configuration is easier that way, and 
the job configurations don't become too complex.

That said, have you tried Any Build Step Plugin? It might allow you to do what 
you want to achieve.

The upcoming Workflow plugin probably also has the required flexibility of 
combining steps more flexibly in its job type.

On 10.07.2014, at 00:53, Jeff  wrote:

> This is a bit of a rant, but I'm unclear why it matters which steps are 
> available as a build step vs. a post-build step.
> 
> I'm trying to create a simple job to grab debian packages archived from 
> various upstream "build" jobs and installing/configuring the debian packages 
> on a set of test servers as part of an "install" job.
> 
> The "Install job" sequence would be:
>   * Copy artifacts from previous jobs
>   * SCP them to the specified server(s)
>   * Run the installers via SSH
>   * Update configuration
> However, I am unable to use the Jenkins plugins to do step 2 and 3 in the 
> proper order because the "Publish artifacts to SCP Repository" plugin option 
> is not available as a "build step" and "Execute shell script on remote host 
> using ssh" plugin as it's not available as a "post-build action".  (chicken 
> or egg paradox).
> 
> The motivation to use these plugins is to help manage the hosts/passwords 
> required to use SCP/SSH.
> 
> Thus, the question is ... why does Jenkins need to differentiate between a 
> build step and a post-build action?  Why not allow a mix of any type of 
> operation/step, regardless if it's type?
> 
> It seems job creation flexibility would be enhanced if all tasks could be 
> used, particularly for jobs that don't really do builds (in the traditional 
> sense) such as creating a "pipeline" of phases/steps (continuous delivery, 
> etc.) deploy-dev  --> functional test --> deploy-staging --> integration test 
> --> deliver release candidate.
> 
> Has there been consideration around allowing any step to be added in any 
> order?
> 
> -- 
> 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/d/optout.

-- 
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/d/optout.

Frustration with build-step/post-build-action access...

[Jeff]

This is a bit of a rant, but I'm unclear why it matters which steps are
available as a build step vs. a post-build step.

I'm trying to create a simple job to grab debian packages archived from
various upstream "build" jobs and installing/configuring the debian
packages on a set of test servers as part of an "install" job.

The "Install job" sequence would be:

   1. Copy artifacts from previous jobs
   2. SCP them to the specified server(s)
   3. Run the installers via SSH
   4. Update configuration

However, I am unable to use the Jenkins plugins to do step 2 and 3 in the
proper order because the "Publish artifacts to SCP Repository" plugin
option is not available as a "build step" and "Execute shell script on
remote host using ssh" plugin as it's not available as a "post-build
action".  (chicken or egg paradox).

The motivation to use these plugins is to help manage the hosts/passwords
required to use SCP/SSH.

Thus, the question is ... why does Jenkins need to differentiate between a
build step and a post-build action?  Why not allow a mix of any type of
operation/step, regardless if it's type?

It seems job creation flexibility would be enhanced if all tasks could be
used, particularly for jobs that don't really do builds (in the traditional
sense) such as creating a "pipeline" of phases/steps (continuous delivery,
etc.) deploy-dev  --> functional test --> deploy-staging --> integration
test --> deliver release candidate.

Has there been consideration around allowing any step to be added in any
order?

-- 
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/d/optout.

quotes in bash script on windows are being ignored

[Dan Tenenbaum]

Hi,

I have a jenkins project whose "Execute shell" command consists of this:


set -e  # Exit immediately if a simple command exits with a non-zero status
set -x verbose


export PKG="annotation"
export SUFFIX="zip"

ssh -o StrictHostKeyChecking=no -i $SSH_KEY jenk...@docbuilder.mydomain.org 
"rm -f ~/repository/$PKG/*.$SUFFIX"

If I run this script manually on the windows box, it works fine. 

That ssh command looks syntactically valid to me (SSH_KEY is defined in the 
node config) but it fails in jenkins. Since I have verbosity turned on this 
is the command I see (along with its output) in the jenkins build output:

+ ssh -o StrictHostKeyChecking=no -i c:/jenkins/docbuilder 
jenk...@docbuilder.mydomain.org rm -f ~/repository/annotation/*.zip
usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
   [-D [bind_address:]port] [-e escape_char] [-F configfile]
   [-I pkcs11] [-i identity_file]
   [-L [bind_address:]port:host:hostport]
   [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
   [-R [bind_address:]port:host:hostport] [-S ctl_path]
   [-W host:port] [-w local_tun[:remote_tun]]
   [user@]hostname [command]


So it looks like the quotes in my command were somehow stripped. I think those 
quotes are needed in order for ssh to understand its arguments (otherwise the * 
is expanded before it gets to ssh, and so on). 


How can I fix that? I tried escaping the quotes with a backslash and then the 
command (when echoed) looked like this in the jenkins output:


+ ssh -o StrictHostKeyChecking=no -i c:/jenkins/docbuilder 
jenk...@docbuilder.mydomain.org "rm -f ~/repository/annotation/*.zip"

usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
   [-D [bind_address:]port] [-e escape_char] [-F configfile]
   [-I pkcs11] [-i identity_file]
   [-L [bind_address:]port:host:hostport]
   [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
   [-R [bind_address:]port:host:hostport] [-S ctl_path]
   [-W host:port] [-w local_tun[:remote_tun]]
   [user@]hostname [command]


So the quotes are now present but there is still something wrong with the 
command as seen by ssh.

If I copy and paste that command directly into an sh window on the windows node 
(a cygwin terminal window where I have exported SSH_KEY), it works.


Another thing I should mention is that I'm logged into the windows node as 
Administrator, but the jenkins slave is running as nt authority\system, a user 
who does not have the right to log on interactively. 


Any ideas? 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/d/optout.

Re: "FATAL: No author in changeset" (using Git plugins)

[Mark Waite]

I see the problem on Windows and Linux slaves
On Jul 9, 2014 8:07 AM, "Steve K"  wrote:

> Mark,
>
> To be clear, are you saying you see it with both Windows and Linux *servers
> *(vs. slaves)?
>
> Thanks for the link to the reported issue. There is some comfort in
> knowing you're not alone and that, maybe, someone is looking into the
> problem.
>
> Regards,
>
> Steve K.
>
> --
> 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/d/optout.
>

-- 
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/d/optout.

Re: Extended email jelly script cached?

[novamine118]

Thanks, that did it :D

-- 
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/d/optout.

Re: Extended email jelly script cached?

[Slide]

There is an html.jelly built into the plugin so that is what is being used
(the built-in templates will be searched first). You would need to name it
something else if you want to change it. Try changing the file name to
myhtml.jelly and using template="myhtml" in the JELLY_SCRIPT token.

slide


On Wed, Jul 9, 2014 at 8:24 AM, novamine118  wrote:

> I'm using:
> extended email
>  version
> 2.38.1
>
> on jenkins: 1.542
>
> I added the html.jelly
> 
> script at /email-templates/html.jelly
>
> and set the email content to: ${JELLY_SCRIPT,template="html"}
>
> It worked like a charm...until I needed to change it(i removed the built
> artifacts sections) . I thought I could modify the script and restart
> tomcat, but the changes I had made were not executed.
>
> I even removed the file but it is still somehow executing the old jelly
> script. I did some template testing (jenkins_url/jobname/templateTest/) and
> the template test doesn't find the file on the system (html.jelly)... but i
> hit "Go!" and it executes the old script again.
>
> I can think of 2 reasons why:
>
>1. My original script was never executing in the first place - which
>is why changing it didn't affect it.
>2. The script is cached somewhere(somehow restarting tomcat and/or
>"reloading configuration from disk" doesn't clear this?)
>
>
> Has anyone else come across an issue like this?
>
> Thanks,
> Xavier
>
> --
> 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/d/optout.
>



-- 
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/d/optout.

Extended email jelly script cached?

[novamine118]

I'm using:
extended email 
 version 
2.38.1

on jenkins: 1.542

I added the html.jelly 

 
script at /email-templates/html.jelly

and set the email content to: ${JELLY_SCRIPT,template="html"}

It worked like a charm...until I needed to change it(i removed the built 
artifacts sections) . I thought I could modify the script and restart 
tomcat, but the changes I had made were not executed.

I even removed the file but it is still somehow executing the old jelly 
script. I did some template testing (jenkins_url/jobname/templateTest/) and 
the template test doesn't find the file on the system (html.jelly)... but i 
hit "Go!" and it executes the old script again.

I can think of 2 reasons why:

   1. My original script was never executing in the first place - which is 
   why changing it didn't affect it.
   2. The script is cached somewhere(somehow restarting tomcat and/or 
   "reloading configuration from disk" doesn't clear this?)


Has anyone else come across an issue like this?

Thanks,
Xavier

-- 
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/d/optout.

How to specify the pom.xml location in GIT-Jenkins project setup ?

[sai ram]

I am a new-bee to GIT-Jenkins project setup.

Project Setup

Root Folder
   -- Sub Folder
  --- Folder 1 where project is present (pom.xml located)  First 
Project
  --- Folder 1 where project is present (pom.xml located)  Second 
Project

I need some clarification to know, 

1. What to specify in Branches to build ?
2. What I need to specify in RefSpec to access project location?
3. Path to specify to access pom.xml.

I am not able to execute the project due to the above mentioned contraints. 

TIA

-- 
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/d/optout.

Re: "FATAL: No author in changeset" (using Git plugins)

[Steve K]

Mark,

To be clear, are you saying you see it with both Windows and Linux *servers 
*(vs. slaves)?

Thanks for the link to the reported issue. There is some comfort in knowing 
you're not alone and that, maybe, someone is looking into the problem.

Regards,

Steve K.

-- 
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/d/optout.

Re: "FATAL: No author in changeset" (using Git plugins)

[Mark Waite]

I see the problem on both Windows and Linux.

Mark Waite


On Wed, Jul 9, 2014 at 7:47 AM, Steve K 
wrote:

> Thanks Mark,
>
> Just curious. Are you on a Windows server?  We recently moved from a Linux
> to a Windows server. We never saw the problem when we were on the Linux
> server.
>
> Regards,
>
> Steve K.
>
>>   --
> 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/d/optout.
>



-- 
Thanks!
Mark Waite

-- 
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/d/optout.

Re: "FATAL: No author in changeset" (using Git plugins)

[Steve K]

Thanks Mark,

Just curious. Are you on a Windows server?  We recently moved from a Linux 
to a Windows server. We never saw the problem when we were on the Linux 
server.

Regards,

Steve K.

>  

-- 
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/d/optout.

Re: "FATAL: No author in changeset" (using Git plugins)

[Mark Waite]

I've seen the same problem, and Thomas Carsuzan has seen the same problem.

https://issues.jenkins-ci.org/browse/JENKINS-16737 is being used to track
the issue.

The usual work around is to build again, or to wipe the workspace and build
again.  It is still not clear what is causing the problem, since it is
sporadic.  I have multi-configuration jobs which run successfully almost
always, but occasionally one of the configurations will report that
message.  If I run the same job again, it succeeds.

Mark Waite


On Wed, Jul 9, 2014 at 7:30 AM, Steve K 
wrote:

> Hello,
>
> Have any other 'Git' users seen this problem?
> We are at Jenkins v1.554.3 with Git Plugin v 2.2.2, Git Parameter Plugin v
> 0.3.2, and Git Client Plugin v 1.9.1
>
> The problem occurs at the very end of the job, when it is attempting to
> send job success notices to the developers who committed code included in
> the build.
> Even though the real work of the build was error free, when Jenkins was
> unable to identify the author of a commit, it caused a general, fatal,
> error for the job.
>
> Here is a snippet of the Console Output:
>
> Archiving artifacts
> Recording NUnit tests results
> FATAL: No author in changeset c81c92cc02ab4535fada09e1dbc49d78a889fb9a
> java.lang.RuntimeException: No author in changeset 
> c81c92cc02ab4535fada09e1dbc49d78a889fb9a
>   at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:324)
>   at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:414)
>   at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:410)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:729)
>
>  We have verified that there is no problem with any of the commits in the
> Git repository.
>
> Thanks in advance for any insight or suggestions.
>
> Steve K.
>
> --
> 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/d/optout.
>



-- 
Thanks!
Mark Waite

-- 
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/d/optout.

"FATAL: No author in changeset" (using Git plugins)

[Steve K]

Hello,

Have any other 'Git' users seen this problem?
We are at Jenkins v1.554.3 with Git Plugin v 2.2.2, Git Parameter Plugin v 
0.3.2, and Git Client Plugin v 1.9.1

The problem occurs at the very end of the job, when it is attempting to 
send job success notices to the developers who committed code included in 
the build.
Even though the real work of the build was error free, when Jenkins was 
unable to identify the author of a commit, it caused a general, fatal, 
error for the job.

Here is a snippet of the Console Output:

Archiving artifacts
Recording NUnit tests results
FATAL: No author in changeset c81c92cc02ab4535fada09e1dbc49d78a889fb9a
java.lang.RuntimeException: No author in changeset 
c81c92cc02ab4535fada09e1dbc49d78a889fb9a
at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:324)
at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:414)
at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:410)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:729)

 We have verified that there is no problem with any of the commits in the 
Git repository.

Thanks in advance for any insight or suggestions.

Steve K.

-- 
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/d/optout.

Preserving last n working days builds

[varun srivastava]

Hi,

I want to preserve last 3 days build for my projects. But I do not run the 
builds on weekends, so I essentially want to preserve builds for last 3 
working days. Is there a way to achieve this in  jenkins.

Thanks
Varun

-- 
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/d/optout.

Re: Running test cases as different user in Jenkins

[varun srivastava]

Using unix groups looks like the correct approach here. I gave a try. It 
woks fine. Thanks.

Now, since I maintain a centralized jenkins instance that are used by 
different groups and want to run the test cases as application user(u2, u3, 
...) rather than jenkins runtime user (u1). Is there a way I can invoke the 
maven and ant targets as a different user (u2) than my jenkins run 
user(u1). In case of shell scripts I can do someting like sudo -u u2 
run_script.sh. But I am not able to figure out how to do this for maven and 
ant steps.

On Thursday, 3 July 2014 19:12:11 UTC+5:30, Fritz Elfert wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> On 07/03/2014 02:23 PM, varun srivastava wrote: 
>
>
> Not really a jenkins question. More like a generic Unix question: 
> "How to share certain directories or files between different users, 
> where each user shall be able to write/delete" 
>
> Solution: 
> That's what groups are intended for. 
> Create a dedicated group for this and make all participating users a 
> member of this group. Then, give directories rwx permissions for that 
> group and files at least rw permissions for that group. 
>
> CU 
>  -Fritz 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1 
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ 
>
> iEYEARECAAYFAlO1XWoACgkQboM4mAMyprAOpACfUwVSbHkYE2fpnVIHI1wuG1Ba 
> OBEAoJPZ7gUEsREYIJFaaBBgB4F9Ky7u 
> =OlDa 
> -END PGP SIGNATURE- 
>

-- 
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/d/optout.

Re: Jenkins API access to Build History

[teilo]

Best practice is to normally have each branch in a different job. 
 Otherwise trends and linear history become a bit meaningless.

 It also solves your issue as you just use lastStable/api/…

 /James

On Wednesday, 9 July 2014 08:54:31 UTC+1, sebastian.nickel wrote:
>
> Hi Darrel,
> thank you for your answer. I already feared that I have to do it this way 
> :-) This means that I need to do multiple API calls until I found all the 
> builds for my specific branch/tag. I hoped there is a method with doing 
> only one API call and then search for the desired build.
>
>
> Cheers
> Nick
>
> On Tuesday, July 8, 2014 9:26:05 PM UTC+2, DarrelVun wrote:
>>
>> Nick:
>>
>> If you're using Git and Gerrit, then you can find the branch and sha1 
>> under "actions" and "parameters" as name/value pairs, with name of 
>> "GERRIT_BRANCH" and "GERRIT_PATCHSET_REVISION".  I don't know of a way to 
>> find the specific build except to walk a project's builds until you find it.
>>
>> So, to be clear:
>> - Start at http://*jenkins_url*/job/*project_name*/api/json?pretty=true
>> - Find the array of "builds", each element of which contains a key/value 
>> pair of "url" and the URL you need to visit
>> - E.g. a build URL will look like http://*jenkins_url*/job/*project_name*
>> /*build_number*/api/json?pretty=true
>> - Look for "actions" -> "parameters" -> "name" == "GERRIT_BRANCH"
>>
>> I don't know of an easier way.  
>>
>>
>> Regards,
>> Darrel V in NC 
>>
>>
>>
>> On Tuesday, July 8, 2014 8:02:08 AM UTC-4, sebastian.nickel wrote:
>>>
>>> Heya,
>>> we are using jenkins in combination with capistrano to deploy the 
>>> artifacts build by jenkins directly to our servers. To get the URL for an 
>>> artifact we are trying to get the build number for a specific git 
>>> branch/tag we build in jenkins (doing this with json API calls). We noticed 
>>> that the API shows only one entry for a specific branch/tag (always the 
>>> last one). Sometimes it is the case that the latest build failed, so we 
>>> would like to deploy the last successful build of a specific branch/tag 
>>> from git. Currently I would like to find the build number via the build 
>>> history of jenkins, but it seems jenkins doesn't provide API access to the 
>>> build history. Does anyone have an idea how to get the last successful 
>>> build for a specific git branch/tag via the API?
>>>
>>> Cheers
>>> Nick
>>>
>>

-- 
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/d/optout.

Re: Problem with Clearcase plugin running many builds in parallel

[Sascha Herrmann]

Hi Vincent,

1.5.2 works fine. Thanks for the assistance and the fix.

Sascha

Am Montag, 7. Juli 2014 09:54:10 UTC+2 schrieb Vincent Latombe:
>
> I just released 1.5.2 with the form fix.
>
> Vincent
>
>
> 2014-07-07 9:07 GMT+02:00 Sascha Herrmann  >:
>
>> Hi!
>>
>> Thanks. It seems to be just a thing of saving the setting. When I put the 
>> "2" directly into the endViewDelay tag in the XML and then restart Jenkins, 
>> then the delay is applied fine and I see the "2" in the settings.
>>
>> Sascha
>>
>> -- 
>> 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/d/optout.
>>
>
>

-- 
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/d/optout.

Re: Jenkins API access to Build History

[sebastian.nickel]

Hi Darrel,
thank you for your answer. I already feared that I have to do it this way 
:-) This means that I need to do multiple API calls until I found all the 
builds for my specific branch/tag. I hoped there is a method with doing 
only one API call and then search for the desired build.


Cheers
Nick

On Tuesday, July 8, 2014 9:26:05 PM UTC+2, DarrelVun wrote:
>
> Nick:
>
> If you're using Git and Gerrit, then you can find the branch and sha1 
> under "actions" and "parameters" as name/value pairs, with name of 
> "GERRIT_BRANCH" and "GERRIT_PATCHSET_REVISION".  I don't know of a way to 
> find the specific build except to walk a project's builds until you find it.
>
> So, to be clear:
> - Start at http://*jenkins_url*/job/*project_name*/api/json?pretty=true
> - Find the array of "builds", each element of which contains a key/value 
> pair of "url" and the URL you need to visit
> - E.g. a build URL will look like http://*jenkins_url*/job/*project_name*/
> *build_number*/api/json?pretty=true
> - Look for "actions" -> "parameters" -> "name" == "GERRIT_BRANCH"
>
> I don't know of an easier way.  
>
>
> Regards,
> Darrel V in NC 
>
>
>
> On Tuesday, July 8, 2014 8:02:08 AM UTC-4, sebastian.nickel wrote:
>>
>> Heya,
>> we are using jenkins in combination with capistrano to deploy the 
>> artifacts build by jenkins directly to our servers. To get the URL for an 
>> artifact we are trying to get the build number for a specific git 
>> branch/tag we build in jenkins (doing this with json API calls). We noticed 
>> that the API shows only one entry for a specific branch/tag (always the 
>> last one). Sometimes it is the case that the latest build failed, so we 
>> would like to deploy the last successful build of a specific branch/tag 
>> from git. Currently I would like to find the build number via the build 
>> history of jenkins, but it seems jenkins doesn't provide API access to the 
>> build history. Does anyone have an idea how to get the last successful 
>> build for a specific git branch/tag via the API?
>>
>> Cheers
>> Nick
>>
>

-- 
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/d/optout.

what are the straight forward features of jenkins over team city

[Raja M]

HI,
 
I am big fan of Jenkins. I need to prepare a presentation with unique 
features of Jenkins which are not available in team city.  apart from being 
free, scalability with unlimited master slave concept,  what are points 
make us win over teamcity. your inputs are more valuable.
 
Thanks,
Raja 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/d/optout.