subject:"\[JIRA\] \[parameterized\-trigger\] $JENKINS\-22212$ No e\-mail sent after failed build triggered from another build"















































Alexander Obuhovich
 updated  JENKINS-22212


No e-mail sent after failed build triggered from another build
















Even though I've set to passthrough SVN related info (included revisions) to the downstream job but it didn't work.

Maybe problem is, with my setup. I have:


	upstream job that does 2 SVN checkouts and is triggered by SVN post-commit hook
	downstream job that deploys changes on staging server
	downstream job doens't have any SVN related options set up







Change By:


Alexander Obuhovich
(26/Mar/14 11:26 AM)




Attachment:


SvnRevision_Dont_GetPassedThrough.png



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build













































 
Alexander Obuhovich
 edited a comment on  JENKINS-22212


No e-mail sent after failed build triggered from another build
















Even though I've set to passthrough SVN related info (included revisions) to the downstream job but it didn't work.

Maybe problem is, with my setup. I have:


	upstream job that does 2 SVN checkouts and is triggered by SVN post-commit hook
	downstream job that deploys changes on staging server
	downstream job doesn't have any SVN related options set up



See attached "SvnRevision_Dont_GetPasse..." image.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build















































Alexander Obuhovich
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















 Fingerprint Plugin helps you!: https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint+Plugin It provides "Fingerprint files" in "Build" step.

I've tried it, but it seems that fact, that I have several upstream jobs that trigger a same downstream deployment job and that all are using same "revision.txt" makes it hard for Jenkins to manage.

Maybe I should create "projecta_revsision.txt", "projectb_revision.txt" in upstream job and pass that filename as a build parameter to downstream job. Then in fingerprint screen I won't see messages like "revision.txt" was introduced by "projecta" and last used by "projectb".



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build













































 
Alexander Obuhovich
 edited a comment on  JENKINS-22212


No e-mail sent after failed build triggered from another build
















Fingerprint Plugin helps you!: https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint+Plugin It provides "Fingerprint files" in "Build" step.

I've tried it, but it seems that fact, that I have several upstream jobs that trigger a same downstream deployment job and that all are using same "revision.txt" makes it hard for Jenkins to manage.

Maybe I should create "projecta_revsision.txt", "projectb_revision.txt" in upstream job and pass that filename as a build parameter to downstream job. Then in fingerprint screen I won't see messages like "revision.txt" was introduced by "projecta" and last used by "projectb".



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-26 Thread de...@ikedam.jp (JIRA)















































ikedam
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















I think fingerprints use not the name of files, but the content of files.
You should output SVN_URL_1 additional to SVN_REVISION_1.


I'm not sure how "Include/passthrough Upstream SVN Revisons" work.
It may requires checkout also in downstream to have variables defined.
"Predefined Parameters" always work and may be reliable.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build















































Alexander Obuhovich
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















I'm not sure how "Include/passthrough Upstream SVN Revisons" work.

Aren't the "parameterized-trigger" plugin developer?

It may requires checkout also in downstream to have variables defined.

That is my guess too.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-26 Thread de...@ikedam.jp (JIRA)















































ikedam
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















parameterized-trigger-plugin just passes information to ensure subversion-plugin checkouts the same revision as upstream.
Detailed behaviors, for example when variables are defined, are controlled by subversion-plugin.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-25 Thread de...@ikedam.jp (JIRA)















































ikedam
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















Fingerprint Plugin helps you!: https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint+Plugin
It provides "Fingerprint files" in "Build" step.

2 repositories invalidates ${SVN_REVISION}. Instead you should get revisions with ${SVN_REVISION_1} or ${SVN_REVISION_2}.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-24 Thread aik.b...@gmail.com (JIRA)















































Alexander Obuhovich
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















I've enabled upstreamCulprits and things didn't go as planned. Since "Culprits" include "Developers" that isn't populated from upstream job, then I ended up in same place I started: no e-mail were sent out.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-24 Thread de...@ikedam.jp (JIRA)

ikedam
commented on JENKINS-22212

No e-mail sent after failed build triggered from another build

Sorry, that's my mistake.
It requires using fingerprints to have Jenkins recognize "upstream" and "downstream".

This would be done in following way (but not so simple...):

In upstream project, fingerprint the revision as following:

run following script with "Execute shell":

echo ${SVN_REVISION} revision.txt

Call "Record fingerprints of files to track usage" for "revision.txt"
Pass SVN_REVISION to downstream project as following with "Predefined Parameters" in "Trigger parameterized build on other projects"

UPSTREAM_SVN_REVISION=${SVN_REVISION}

As you use "Include/passthrough Upstream SVN Revisons", SVN_REVISION may be passed to downstream automatically. I cannot test as I don't use subversion in my environment.

Also in downstream project, fingerprint the revision as following:

run following script with "Execute shell":

echo ${UPSTREAM_SVN_REVISION} revision.txt

Call "Record fingerprints of files to track usage" for "revision.txt"

This should be called before calling Email-ext.

You can see fingerprints work correct in "See Fingerprints" of the build page.
And you can also test in Manage Jenkins Script Console:

hudson.model.AbstractBuild.upstreamCulprits

Returns true if hudson.upstreamCulprits is successfully configured.

Jenkins.instance.getItemByFullName("downstreamProjectName").lastBuild.getDependencyChanges(Jenkins.instance.getItemByFullName("downstreamProjectName").lastBuild.previousBuild)

Returns upstream build if successfully tracked using fingerprints

Jenkins.instance.getItemByFullName("downstreamProjectName").lastBuild.culprits

Returns upstream developers if upstreamCulprits (and fingerprints) work successfully.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-24 Thread aik.b...@gmail.com (JIRA)















































Alexander Obuhovich
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















echo ${SVN_REVISION} revision.txt

I don't get it. I dump the SVN revision to "revision.txt" in both upstream and downstream projects, but why? Maybe a mistake?

Call "Record fingerprints of files to track usage" for "revision.txt"

I don't have such build step in build step dropdown.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-24 Thread de...@ikedam.jp (JIRA)















































ikedam
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















Do you have multiple svn repositories to checkout?
In that case, revisions are passed as SVN_REVISION_1, SVN_REVISION_2, ... 
Please dump all environment variables by running "export" in "Execute shell".

"Record fingerprints of files to track usage" is available in Post-build Actions.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-24 Thread aik.b...@gmail.com (JIRA)















































Alexander Obuhovich
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















Do you have multiple svn repositories to checkout?

I have 2 repositories to be checked out, but I do have $SVN_REVISION environment variable never the less pointing out to SVN commit that caused build to start.

"Record fingerprints of files to track usage" is available in Post-build Actions.

That doesn't help in my case, because upstream job is triggering downstream job in parallel (non-blocking) so the downstream job starts before upstream job finishes.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build















































Alexander Obuhovich
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















To use hudson.upstreamCulprits

I think I'll start with that.

To write a groovy script to extract upstream developers. It is available at JENKINS-17742

I'm new at Groovy scripts. Where should I put it, maybe as "Run Groovy Script" postbuild action? What happens, when I run this downstream job on it's own, then this Groovy script won't mess all up?

To request a new feature to email-ext.

The same problem would happen with native Jenkins e-mailing post build action I guess. How "Email-Ext" can solve it?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-18 Thread de...@ikedam.jp (JIRA)















































ikedam
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















This page would be better to understand how to extract upstream developers with a groovy script:
http://stackoverflow.com/questions/14541617/how-can-jenkins-downstream-job-send-email-notification-to-upstream-git-committer


The same problem would happen with native Jenkins e-mailing post build action I guess. How "Email-Ext" can solve it?
As I mentioned, it's not a bug but a designated behavior of Jenkins.
Parameterized trigger does nothing for that.
If you want both built-in mailer and email-ext extract upstream developers, you can post requests of new features to both of them.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build















































Alexander Obuhovich
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















I've added -Dhudson.upstreamCulprits=true. Let's see how it will go.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build













































 
Alexander Obuhovich
 edited a comment on  JENKINS-22212


No e-mail sent after failed build triggered from another build
















I've added -Dhudson.upstreamCulprits=true. Let's see how it will go.

Thanks for your help.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
















































Alexander Obuhovich
 resolved  JENKINS-22212 as Not A Defect


No e-mail sent after failed build triggered from another build
















Change By:


Alexander Obuhovich
(18/Mar/14 2:20 PM)




Status:


Open
Resolved





Resolution:


NotADefect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build

2014-03-17 Thread de...@ikedam.jp (JIRA)















































ikedam
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















"Developers" extracts users to send a mail from changelog.
Please look at change logs of downstream (deployment) build. Does it properly report changes as upstream build?
If no change logs are recorded in the downstream build, "Developers" does not work correct.

"Culprits" provides extraction from upstream builds by setting system property hudson.upstreamCulprits to true.
It can be set by launching your Jenkins as

java -Dhudson.upstreamCulprits=true jenkins.jar
Please see https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties for more details.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build















































Alexander Obuhovich
 commented on  JENKINS-22212


No e-mail sent after failed build triggered from another build















"Developers" extracts users to send a mail from changelog.
Please look at change logs of downstream (deployment) build. Does it properly report changes as upstream build?

Nope it doesn't. The downstream job has "No Changes" in the "Changes" tab on the each build page.

If a downstream job has no SCM integration, then I wonder how the upstream job, that has it can pass that info to downstream job.

Setting up a SCM integration for downstream job isn't a good idea, since I use a single downstream job to deploy probjects from different other jobs, where each has own SVN project path.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build













































 
Alexander Obuhovich
 edited a comment on  JENKINS-22212


No e-mail sent after failed build triggered from another build
















"Developers" extracts users to send a mail from changelog.
Please look at change logs of downstream (deployment) build. Does it properly report changes as upstream build?

Nope it doesn't. The downstream job has "No Changes" in the "Changes" tab on the each build page.

If a downstream job has no SCM integration, then I wonder how the upstream job, that has it can pass that info to downstream job.

Setting up a SCM integration for downstream job isn't a good idea, since I use a single downstream job to deploy probjects from different other jobs, where each has own SVN project path.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build













































 
Alexander Obuhovich
 edited a comment on  JENKINS-22212


No e-mail sent after failed build triggered from another build
















"Developers" extracts users to send a mail from changelog. Please look at change logs of downstream (deployment) build. Does it properly report changes as upstream build?

Nope it doesn't. The downstream job has "No Changes" in the "Changes" tab on the each build page.

If a downstream job has no SCM integration, then I wonder how the upstream job, that has it can pass that info to downstream job.

Setting up a SCM integration for downstream job isn't a good idea, since I use a single downstream job to deploy probjects from different other jobs, where each has own SVN project path.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build