On Wed, May 2, 2018 at 10:50 AM, <[email protected]> wrote: > The goal I am trying to achieve is a deep insight into the CI/build/etc > pipeline. > So if for example a user of the platform complains about slow builds, we can > see exactly where time is spent. > Waiting for executors, running a certain shell script, a single maven step > and > so on. > And all of this would be stored in a uniform way for queries and analysis.
All of that metadata is already available via `workflow-api` metadata calls. It is unclear to me why it would need to be made available to steps inside the build itself as environment variables, as opposed to via REST endpoints on the build URL or something (akin to what Blue Ocean uses). > As everything goes through a shell fair enough. > I somehow thought `sh` would be like plain `execve` There is JENKINS-44231, though the most straightforward implementation would not handle prohibited environment variables. -- 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/CANfRfr3cXMneEToQn1zrfe7XzyooDgVGkZzhYJ2LofQWPxC2KA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
