Well, Its not available to assign as a param ... it's something generated only when the build runs
On Mon, Jul 24, 2017 at 4:17 PM J0991 <[email protected]> wrote: > One possibility may be assigning the task name as an environment variable > during the initial job. > You could then access this environment variable from any subsequent jobs. > > More information on Jenkins environment variables can be found here > <https://jenkins.io/doc/pipeline/tour/environment/> . > > > > -- > View this message in context: > http://jenkins-ci.361315.n4.nabble.com/parse-out-text-from-the-console-log-to-be-used-in-the-letter-stage-of-the-build-tp4900671p4900782.html > Sent from the Jenkins users mailing list archive at Nabble.com. > > -- > 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/1500929850006-4900782.post%40n4.nabble.com > . > For more options, visit https://groups.google.com/d/optout. > -- Sent from mobile device, excuse typos if any. -- 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/CAPzcO4hXo1aAO%3D9a31G165mv5eKQ__L_810OJPHDcjPC6UF6vg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
