Jenkins properties file

Question

How to change values in .properties file and run a build using the values in jenkins?

Answer 1

You can try to use the EnvInject Plugin for Jenkins which allows to inject environment variables into build process, and modify your .bat file to use them instead of reading values from the properties file.

Here are some of the plugin's usecases/features:

To remove inherited environment variables (PATH, ANT_HOME, ...) at node level (master/slave), available by default for a job run.
To inject variables in the first step of the job (before the SCM checkout)
To inject variables based on user parameter values
To execute an initialization script before a SCM checkout.
To execute an initialization script after a SCM checkout
To inject variables as a build step obtained from a file filled in by a previous build step
To know environment variables used for a build
To inject build cause as environment variable for a build
To inject environment variables from the evaluation of a Groovy script (powered by Script Security Plugin)
To export environment variables as a metadata in your binary repository

Comments

@Dragonlord, what is the difference between .bat file and a .properties file?

Answer 2

Follow these steps:

1. Install ‘EnvInject’ plug-in in the Jenkins CI tool.

2. After installing ‘EnvInject’ plug-in, you will see ‘Inject environment variables’ option under ‘Add Build Step’.

3. Configure the plug-in with Jenkins job by clicking on ‘Inject environment variables’ option.

4. You will see two fields: ‘Properties File Path’ and ‘Properties Content’ field after adding ‘Inject environment variables’.

5. In ‘Properties File Path’ field, provide the path of the properties file, i.e. where it exists in the Automation project and in ‘Properties Content’ field, provide all the information that you want to change in the run time

6. Now, run the Jenkins’s job to set all the ‘Properties Content’ field data into environment variable of target Virtual machine temporarily.

7. Get the properties data from the System environment variables and update the properties file.  This can be done by configuring the build.xml file

Comments

If build.xml file is already exist, where can i find it? if i want to create newly please let me know how to create.

Answer 3

To change the property values, open the output stream and store properties after you have closed the input stream.

FileInputStream in = new FileInputStream("First.properties");
Properties props = new Properties();
props.load(in);
in.close();

FileOutputStream out = new FileOutputStream("First.properties");
props.setProperty("country", "america");
props.store(out, null);
out.close();

Answer 4

You can use the EnvInject plugin. This plugin makes it possible to have an isolated environment for your jobs.

Answer 5

Use cases of the EnvInject plug-in:

• To remove inherited environment variables (PATH, ANT_HOME, ...) at node level (master/slave), available by default for a job run.
• To inject variables in the first step of the job (before the SCM checkout)
• To inject variables based on user parameter values
• To execute an initialization script before a SCM checkout.
• To execute an initialization script after a SCM checkout
• To inject variables as a build step obtained from a file filled in by a previous build step
• To know environment variables used for a build
• To inject build cause as environment variable for a build
• To inject environment variables from the evaluation of a Groovy script 
• To export environment variables as a metadata in your binary repository