What is the issue?
On Thu, Apr 5, 2012 at 5:37 PM, hsn_ wrote:
> anybody made envinject to work on jboss 7.1?
anybody made envinject to work on jboss 7.1?
On Thu, Apr 5, 2012 at 1:38 PM, shanz wrote:
> Fair enough but I think it is all very confusing particularly the
> Properties File Path and Properties Content fields.
>
No, Jenkins enables you to inject your own environment variables by
properties.
> Are these mutually exclusive?
>
Yes
> I thi
Fair enough but I think it is all very confusing particularly the
Properties File Path and Properties Content fields.
Are these mutually exclusive?
I think it is very unintuitive.
In the wiki page it says, "Variables Traceability - Each build
captures environment variables and stores them in an en
EnvInject plugin enables you to inject only variables for a build.
It is not aimed at propagating environment variables to downstream jobs.
Therefore, EnvInject plugin can read files (properties files) and it
doesn't create files.
If you want to share elements, you have to do yourself.
On Thu, Apr
Environment variables in jenkins are driving me up the wall!
I want to create a "formatted version number", called say BUILD_DATE.
Then I want to store this date in an environment variable that
subsequent jobs can retrieve.
I know I can write it into a file manually but surely the EnvInject
plugi