If you are using same job for your QA, Stage and Prod environment [Though I don't recommend it], and from the build page, you want to show this information by replacing build number to your environment  and By giving a description under your new build name, then you can easily do it by just putting these 2 information's in your Jenkin file:

currentBuild.displayName = "${params.Tags}";

currentBuild.description = "${params.Environment}";

In my case, I am reading this information from the params, but if you want, you can hard code it also.

Once set, and when you will ran your job, the build information will appear like this in your Jenkin build page:

When I did the groovy set up on a windows machine, I never thought I would like an article about the same [How to configure groovy in Mac intelij] when I will do it in mac. The reason is obvious: It's not straightforward in mac. So let me share the steps which I followed to install groovy in mac:

1. You can make sure you have  brew (Homebrew) installed in your mac. To check this, You can run thsi command in the terminal:

2. If the above command says, the brew is not found/recognized, it means you have to install it.

You can open this site:

https://brew.sh/

And inside that, you will see, Install homebrew.

Copy the command and paste it to the terminal and run it.

It will take some time, but it will install brew in your mac.

3. Once homebrew is in your machine, you can install groovy with this command in terminal:

brew install groovy

9. After figuring out groovy in your mac, you need to find out the lib folder. Because in IntelliJ, the lib folder needs to be added. This can be found inside the groovy folder.

10.  Now add it in IntelliJ.

It will add now.

Note: To run groovy, you must have java also configured.

Recently I came across to a problem where I have to run the same Jenkins File which I was running in Linux (Mac) machine to the other Windows machine as well. The first thing which came in my mind (I believe will come to everyone's mind too) is to identify the machine OS and run the script accordingly.

While googling it's solution, reading stack overflow answers, Jenkins documentations, I came across to a solution, which helped me to put a condition in my Jenkins file based on the OS.

Jenkin provides a method isUnix() to check the os Type. So if your code is running in Unix/Linux or mac machine, you can put a condition like this:

 if(isUnix()) {

sh "mvn clean test" // Linux related stuff

} else {

bat "mvn clean test" // Windows related stuff

}

With this way, you can put the windows and Linux configurations separately in your Jenkins file.

 Recently, When I was trying to run my Automation Job in Windows environment, I stuck with one issue, Where in Jenkin console, It started throwing error:

 No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?

I first navigated to that directory where Jenkin took the clone and later ran my maven command there. It worked fine and didn't give any error. It helped me to narrowed down to find the soltution.

In local, where my pom.xml file was present, I tried to run the same command , and here also it worked.

I started googling about this failure.  I found few answer in stackoverflow, but the which which worked in my case was:

to add 

<fork>true</fork>

inside my pom.xml file.

Now My pom file started looking like this:

<plugins>

    <plugin>

        <artifactId>maven-compiler-plugin</artifactId>

        <version>3.1</version>

        <configuration>

            <fork>true</fork>

        </configuration>

    </plugin>

</plugins>

This worked fine and didn't impacted the other jobs also which I was running.

Link: StackOverFlowLink

 Recently I was trying to run the JMeter project with Jenkin and I found some interesting information about it. Let me share what steps I followed. 

1. First I create a java maven project in my local machine.

2. Then create a jmeter directory inside your src/test path.

3. Inside this, put your jmx file.

4. Now go to your pom.xml file. And put the following plugin and dependencies.

<dependencies>
    <dependency>
        <groupId>junit</groupId>
        <artifactId>junit</artifactId>
        <version>3.8.1</version>
        <scope>test</scope>
    </dependency>
</dependencies>
<build>
    <plugins>
        <plugin>
            <groupId>com.lazerycode.jmeter</groupId>
            <artifactId>jmeter-maven-plugin</artifactId>
            <version>2.1.0</version>
            <executions>
                <execution>
                    <id>jmeter-tests</id>
                    <goals>
                        <goal>jmeter</goal>
                    </goals>
                </execution>
            </executions>
        </plugin>


        <plugin>
            <groupId>de.codecentric</groupId>
            <artifactId>jmeter-graph-maven-plugin</artifactId>
            <version>0.1.0</version>
            <configuration>
                <inputFile>${project.build.directory}/jmeter/results/20170319-BlazeDemo Home Page.jtl</inputFile>
                <graphs>
                    <graph>
                        <pluginType>ResponseTimesOverTime</pluginType>
                        <width>800</width>
                        <height>600</height>
                        <outputFile>${project.build.directory}/jmeter/results/BlazeDemo Request.png</outputFile>
                    </graph>
                </graphs>
            </configuration>
        </plugin>


    </plugins>

jmeter.save.saveservice.output_format=xml

7. Once this local setup will be ready, you can create maven job in jenkin.

8. Inside that JSON, add this command in pre-built steps.

9. In the post-build section, add this path for the report to come in the Performance report plugin:

**\target\jmeter\results\*.jtl

10. Now save the job and click on the build.

 So If you have set up your API Automation project with the Karate framework, and now you are planning to run your automated test cases with the help of Jenkin, you can do it by creating jobs in your Jenkin.

You can create a Jenkin job as a freestyle project or you can create with the help of a pipeline.

Here in this article, we will try to create a freestyle job in Jenkin for API Automated test cases. We can follow below steps:

Steps 1: Click on New Item, give a name for your API Automation

Step 2: Select Maven  project

Step 3: Click on Ok. It will load the configuration page. Select or make sure JDK is selected.

Step 13: Clicking on the cucumber report will show you the summary of all the test cases.