Daniel Beck commented on Bug JENKINS-25355

I am not "Preparing an environment".

That's just where the option is located. No need to use the rest of the 'prepare' options. I'm fairly sure they're no-op if left empty.

I'll try not take this personally, but it is written quite harsh (in my eyes)

It was not meant to insult, and I apologize if it came across that way.

My attempt to reproduce the issue (This has got weird):

Actually, the more specific you can be regarding the circumstances for an issue to occur (and the less complex the setup, e.g. plugins to be installed), the better.

Regarding the example, I'd have expected this to be as simple as:

Configure a job:

  1. Add a build parameter 'foo', set its default to 'bar'
  2. Shell build step: env
  3. Inject variables: foo=baz
  4. Shell build step: env
    and build it, leave the default parameter value.

If I understand the issue correctly, both shell build steps should be showing the same output: foo=bar (among other variables)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to