Email publisher in Multi-configuration job

15 views
Skip to first unread message

Pulkit Lall

unread,
Aug 22, 2016, 6:03:09 AM8/22/16
to Jenkins Developers
Hi,
I have a Jenkins Multi-configuration job which build 1X3 jobs.

I have 2 questions regarding this:
1. Once the build is complete, an email is sent with details like link to job, artifacts, build console, etc. but the problem is for artifacts and build console, I am not able to send email in tabular format instead it just passes the parent job link and then I have to click on the single job and download artifacts or view build console. Am I missing something?
2. In above case, there might be chance that I trigger only one job then how can I prepare email just like above.

Example:

My job:

 

Linux Flavor 1

Linux Flavor 2

Linux Flavor 3

Test

 

 

 


There might be case that some fail while some pass.

What I am expecting:

Body of email:

STATUS

The Build System finished building the job_name

Status: Failure
BuildNumber: 3
Originator: Started by user user-name
Changes: No changes 

Download URL:

Linux Flavor 1

Build Artifacts

Build Console

Linux Flavor 2

Build Artifacts

Build Console

Linux Flavor 3

Build Artifacts

Build Console

Test

${Artifact1}

Build Console

${Artifact2}

${Artifact3}

${Artifact4}


If one flavor is not run then it should put blank

TIA

Slide

unread,
Aug 22, 2016, 8:47:07 AM8/22/16
to Jenkins Developers

Please don't double post. This question is definitely for the user list, not the developer list. Double posting doesn't get your question answered faster.


--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6d3b7f95-bcdf-4543-8335-db9a7565f279%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pulkit Lall

unread,
Aug 23, 2016, 1:51:54 AM8/23/16
to Jenkins Developers
Sorry, did not knew in which to post .
Reply all
Reply to author
Forward
0 new messages