ikedam commented on Bug JENKINS-12410

I could not reproduce the problem, too.
Jenkins 1.532.1 + Email-ext 2.37.2 + Parameterized-trigger 2.22.

What I tried:

  • Run parameterized trigger without parameters as a publisher from multi-configuration project, and always send email to requester in the downstream.
  • Run non-blocking parameterized trigger without parameters as a builder from multi-configuration project, and always send email to requester in the downstream.
  • Run blocking parameterized trigger without parameters as a builder from multi-configuration project, and always send email to requester in the downstream.

I think it is already resolved in some version:

  • There is another ticket JENKINS-12300, which seems same to this and it is reported as resolved (I'm not sure how it is resolved).
  • Current codes of email-ext seems completely different from that of Email-ext 2.28.

I'll close this ticket as Resolved if there is no new reports in one month.

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/groups/opt_out.

Reply via email to