You could use emailext to record changes in the actual build:
1. Create an email with the changes on build success, and check to store the 
email in the workspace ("Save Generated E-mail to Workspace"). Not sure whether 
you need actual recipients if you check that option.
2. Copy that with the build results to the upload job, and use the ${FILE} 
macro in the upload job's emailext.

Alternatively, you can probably use the Any Build Step plugin to add a shell 
script builder to your job as a post-build action (since you mentioned that).

On 22.07.2013, at 17:08, Maureen Barger <[email protected]> wrote:

> We have a maven build of several artifacts. These artifacts are FTP'd
> nightly at 9pm as a separate job from the build. We would like to
> include the changes since last build with our upload.
> 
> Issues:
> Since it's a maven job, I can't execute a shell command at build.
> I've installed Changes Since Last Success Plugin but I am not seeing
> it in the build menu of any new job I create, and since this is a
> maven job, I don't have the build option anyway.
> I have the mail-ext plugin installed and it does great to send out the
> email to interested parties when the FTP upload is complete. And it
> even has a changelog feature but since the build job (which would
> actually contain the changes) and the FTP job are separate, the
> changelog feature is meaningless here.
> 
> Ideally I would like to send a changelog since last upload but a
> changelog of that release, just added on to the file as we go, would
> suffice as well.
> 
> Any suggestions?
> 
> -- 
> 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 [email protected].
> 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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to