Env property during Jenkins build about zerocode

[authorjapps]

@dinesh76in , this is being developed here as a PR #24
Once this gets merged, you should be able to use the env property as below-

// if "env.name=ci", then it picks "app_config_ci.properties". 
// If "env.name" not set, then defaults to "app_config.properties" mentioned via @TargetEnv

@EnvProperty("_${env.name}") 
@TargetEnv("app_config.properties")
@RunWith(TestOnlyZeroCodeUnitRunner.class)
public class ZeroCodeEnvPropertyReaderTest {

    @Test
    @JsonTestCase("01_verification_test_cases/22_env_property_dynamic_runtime.json")
    public void testRunAgainstConfigPropertySetViaJenkins() throws Exception {        
    }
}

-or-

Configure the below mvn command when you run via Jenkins in the specific environment-

For CI :

mvn clean install -Denv.name=ci

For SIT:

mvn clean install -Denv.name=sit

and make sure:
app_config_ci.properties and app_config_sit.properties etc are available in the resources folder or class path.

[authorjapps]

This has been fixed and released now to maven central, use version 1.1.22 or higher.
Search here for latest : http://search.maven.org/#search%7Cga%7C1%7Czerocode

For help on how to use, always refer to README.

Click below for the help n usage of this particular issue-
Setting Jenkins env propperty and picking environment specific properties file