You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2017/04/19 00:44:42 UTC

[jira] [Updated] (SUREFIRE-1365) Allow environment variables to be read from a file, instead of set as a Map

     [ https://issues.apache.org/jira/browse/SUREFIRE-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tibor Digana updated SUREFIRE-1365:
-----------------------------------
    Fix Version/s: 3.0-RC1
                   3.0

> Allow environment variables to be read from a file, instead of set as a Map
> ---------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1365
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1365
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin
>            Reporter: Darius Cooper
>            Assignee: Tibor Digana
>            Priority: Minor
>             Fix For: 3.0, 3.0-RC1
>
>
> With 12-factors apps and deployment on platforms like OpenShift, there a new push on using Environment Variables for configuration. When running Integration tests with Failsafe, it would be nice to set the same variables as will be set to the target environment. 
> Often, there's a file that contains the variables in a key-value pair format, just like a properties file. It would be nice to be able to read that same file in while setting environment variables for Failsafe and also when deploying.
> (There may be some type of simple file-formatting differences, but that's typically easy to handle in an automated way.)
> failsafe:integration-test supports an "environmentVariables" parameter. It would nice if it could support an "environmentVariablesFile" parameter that allowed a simple properties-style file to be read in an set as environment variables.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)