I am not sure how Travis supports git.  In Jenkins Git plugin provides env 
variables available to Jenkins for free:

Environment variables
The git plugin sets several environment variables you can use in your scripts:

  *   GIT_COMMIT - SHA of the current
  *   GIT_BRANCH - Name of the branch currently being used, e.g. "master" or 
"origin/foo"
  *   GIT_AUTHOR_EMAIL - Committer/Author Email
  *   GIT_COMMITTER_EMAIL - Committer/Author Email


However I would suggest that you script a python snippet one-line code to fetch 
the  Github information you need directly from Github REST API using “github” 
python module.
I use “PyGithub” python module.

-Indra



From: <[email protected]> on behalf of "[email protected]" 
<[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Saturday, December 10, 2016 at 10:29 AM
To: Jenkins Users <[email protected]>
Subject: Re: Getting E-Mail Notification:

Travis is requesting parameters from GitHub repository only.
I found the place where parameters are getting populated in GitHub Repository.
I want to add committer/author emaild id at the same place.
So, I was checking out how to fetch the committer/author email id in code.

On Saturday, December 10, 2016 at 10:18:19 AM UTC-8, slide wrote:

That would be done on the Travis side, so you'd have to figure that out under 
Travis.

On Sat, Dec 10, 2016, 10:47 <[email protected]<javascript:>> wrote:
Hi,

Thanks for the info.
I want to know how to fetch the parameter of GitHub Committer email id in 
GitHub Repository code. So that I can pass the committer email id parameter 
into my jenkins Job-parameterized build.

Thanks,
Ajay.

2016 at 3:42:28 PM UTC-8, slide wrote:Aj

On Thursday, December 8,
Check this page 
https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build#Launching+a+build+with+parameters

On Thu, Dec 8, 2016 at 4:28 PM <[email protected]> wrote:
Fine.
May I know, how can we pass user information from Travis to Jenkins 
automatically.
I can see the user info in Travis who caused the build.


On Thursday, December 8, 2016 at 3:09:40 PM UTC-8, slide wrote:

i and ii are out of the scope of this mailing list, but there is the Mailer 
plugin and email-ext plugin for iii as long as you can pass the user 
information to the Jenkins job from Travis

On Thu, Dec 8, 2016, 15:51 <[email protected]> wrote:
I want to know to how can a user (User1) get E-mail Notification, when he does 
the following:

i) User1 commits changes to GitHub in a Repo (Repo1)

ii) A Build in Travis CI server gets triggered whenever any changes committed 
to Repo1. This Build job in travis internally triggers jenkins job apart from 
doing other things.

iii) I want the User (User 1) gets notified from jenkins job, when jenkins job 
fail.

Can anybody help me out on this!
--
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].

To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b2dbda75-7419-43db-80a4-fb8d6d552c6d%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/b2dbda75-7419-43db-80a4-fb8d6d552c6d%40googlegroups.com?utm_medium=email&utm_source=footer>.
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9abbc38f-ab45-40ea-b693-21783593cea1%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/9abbc38f-ab45-40ea-b693-21783593cea1%40googlegroups.com?utm_medium=email&utm_source=footer>.
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 [email protected]<javascript:>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fd60a52d-681e-46a8-b1aa-64ab36786672%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/fd60a52d-681e-46a8-b1aa-64ab36786672%40googlegroups.com?utm_medium=email&utm_source=footer>.
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 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5644e954-8107-46ea-bb98-cc3593acf041%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/5644e954-8107-46ea-bb98-cc3593acf041%40googlegroups.com?utm_medium=email&utm_source=footer>.
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/06CA144E-61E8-4A36-A99C-1B98AF52BF2D%40cisco.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to