Branch: refs/heads/refactoring
Home: https://github.com/jenkinsci/pipeline-github-plugin
Commit: 76ab4851f8c60c93f01ef256d9ae039ee9ea9074
https://github.com/jenkinsci/pipeline-github-plugin/commit/76ab4851f8c60c93f01ef256d9ae039ee9ea9074
Author: Deiwin Sarjas <deiwin.sar...@gmail.com>
Date: 2018-04-04 (Wed, 04 Apr 2018)
Changed paths:
M README.md
M
src/main/java/org/jenkinsci/plugins/pipeline/github/trigger/GitHubEventSubscriber.java
M
src/main/java/org/jenkinsci/plugins/pipeline/github/trigger/IssueCommentCause.java
Log Message:
-----------
Expose additional trigger information from build cause
With this, it should be possible to use multiple different triggers and to
execute different steps based on the particular trigger. It also provides a way
to notify the user who triggered the build via GitHub comments.
The full comment is exposed so that trigger commands could be parameterized.
E.g. extracting the module name from `test module-x`, which matches a generic
`test.*` trigger.
Commit: 85596448bd4203d5ae87350de87f6ab7fc213728
https://github.com/jenkinsci/pipeline-github-plugin/commit/85596448bd4203d5ae87350de87f6ab7fc213728
Author: Aaron Whiteside <aaronjwhites...@gmail.com>
Date: 2018-04-08 (Sun, 08 Apr 2018)
Changed paths:
M README.md
M
src/main/java/org/jenkinsci/plugins/pipeline/github/trigger/GitHubEventSubscriber.java
M
src/main/java/org/jenkinsci/plugins/pipeline/github/trigger/IssueCommentCause.java
Log Message:
-----------
Merge pull request #12 from salemove/comment_trigger
Expose additional trigger information from build cause
Compare:
https://github.com/jenkinsci/pipeline-github-plugin/compare/83c6070e2366...85596448bd42
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
