Branch: refs/heads/master
Home: https://github.com/jenkinsci/pipeline-examples
Commit: 745f09f754f718014fab21297acf32c4c317dcbb
https://github.com/jenkinsci/pipeline-examples/commit/745f09f754f718014fab21297acf32c4c317dcbb
Author: Baptiste Mathus <bat...@batmat.net>
Date: 2016-05-26 (Thu, 26 May 2016)
Changed paths:
M pipeline-examples/trigger-job-on-all-nodes/triggerJobOnEveryNode.groovy
Log Message:
-----------
Using an explicit closure param instead of it
It's probably clearer for a newcomer, and seems like some users are
having issues it that form under some circumstances. Oh well.
https://github.com/jenkinsci/pipeline-examples/commit/efac394c44489d3c308631d8868b149294df48f5#commitcomment-17609700
Commit: efde8a5df36e2e0b213979735bda44444cdfde86
https://github.com/jenkinsci/pipeline-examples/commit/efde8a5df36e2e0b213979735bda44444cdfde86
Author: Andrew Bayer <andrew.ba...@gmail.com>
Date: 2016-05-27 (Fri, 27 May 2016)
Changed paths:
M pipeline-examples/trigger-job-on-all-nodes/triggerJobOnEveryNode.groovy
Log Message:
-----------
Merge pull request #35 from batmat/explicit-param-name
Using an explicit closure param instead of it
Compare:
https://github.com/jenkinsci/pipeline-examples/compare/2e961f328500...efde8a5df36e
--
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.
