On Wed, Oct 19, 2016 at 3:45 AM, <[email protected]> wrote: > in > recorders, I do think that we should be able to look upon the steps so far > so we can record their results more easily by getting the correct paths and > data
If the paths were passed as configuration to the “builder”, then you just pass the same argument to the “recorder”. (Pipeline makes no distinction between types of build steps: you run what you want, when you want.) If the path is somehow autogenerated, the builder could return a value to be passed later to the recorder. Of course if there is no particular reason for the two functions to be separated in time then they can simply be packed into a single step. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/CANfRfr3aLiA7Bh16J5zA6oWySf20k_FM8DqvfVy4Dfeho_cYgQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
