Yes, for security reasons we will only send the env variables that will
start with some prefix like Sumo_, others will be discarded.
Also, even if a stage has lot of env variables it will not matter to us, as
we would like to send all env variables prefixed with Sumo_ in that
particular stage.
On Wed, Dec 16, 2020 at 5:11 PM 'Björn Pedersen' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
> This seems flawed in 2 ways:
> 1) As a stage may contain many steps the env vars at the end of the stage
> may not be what the main workload saw
>
>
> stage ('xxx') {
> withEnv(XXX=1) {
> do work
> }
> withEnv(XXX=2) {}
> } <== XXX has a non-interesting value
>
> 2) Security: The collection mechanism needs to carefully filter all
> 'sensitive' variables (akin to
> https://www.jenkins.io/security/advisory/2018-02-26/#SECURITY-248,
> see also
> https://www.jenkins.io/doc/book/pipeline/jenkinsfile/#interpolation-of-sensitive-environment-variables
> )
>
>
> sou...@sumologic.com schrieb am Mittwoch, 16. Dezember 2020 um 06:31:37
> UTC+1:
>
>> Hi Jesse,
>>
>> The problem we have is to send some data(all environment variables,
>> global or local) after each stage is completed in a jenkins Pipeline.
>>
>> So, we are using GraphListener to listen to every stage end and then send
>> env variables to a HTTP url.
>>
>> But we are not getting all environment variables as explained previously.
>>
>> I hope the above helps.
>>
>> On Wed, Dec 16, 2020 at 1:59 AM Jesse Glick <jgl...@cloudbees.com> wrote:
>>
>>> On Tue, Dec 15, 2020 at 1:01 PM Sourabh Jain <sou...@sumologic.com>
>>> wrote:
>>> > do the flownode object in graph listener have the step context?
>>>
>>> No. There is a `StepListener` that does, but this smells like the
>>> wrong approach to whatever problem it is you are trying to solve,
>>> which you have never explained.
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/jenkinsci-dev/CDKvVuClyJk/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> jenkinsci-de...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0CXWP8h2Ldc70WaBo6w7O4P9doz3ocssZkTy295SJCjw%40mail.gmail.com
>>> .
>>>
>>
>>
>> --
>> Best Regards,
>> *Sourabh Jain*
>> *8408019626*
>> Integration Engineer, APP DEV team,
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/CDKvVuClyJk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/e16c9622-afd2-4111-9d3c-b8fdc88c1b59n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/e16c9622-afd2-4111-9d3c-b8fdc88c1b59n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
Best Regards,
*Sourabh Jain*
*8408019626*
Integration Engineer, APP DEV team,
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CACHaJQR3VFibM-WHgxEnYTLLw-v7TcWH%2BcFN7nWHV2XXceHOEQ%40mail.gmail.com.
