Thank you for the video. One thing I noticed when I had the pipeline set up as you described in previous video (with Install Jmeter tool in the task) is subsequences redeploy of the pipeline has much lower time in the "install Jmeter tool" steps. It doesn't even seems like it re-installing the jmeter each time. I agreed, the first time running the pipeline with the install Jmeter tool took a "long" time. With this method of including the Jmeter in the repo (artifact), are we just shifting the time from the task to artifact (Artifact is now bigger than what it should be as it's now included JMeter)? btw this is a good alternative/option to the previous video. I am planning on exploring another option: Have the Jmeter installed (on) agent (local) machine, create a system environment variable (Jmeter). In THEORY, when the command line "Jmeter -n ...." task kick in, it should use the local copy of the Jmeter to run the task and thus save from having to install Jmeter in the task or in the repo (artifact)
@@littleslawyoutubechannel I will try that at work next week. At my work, there's other issues as well as we have different domain for testing. Basically, the Azure server is on prod domain and the machines with Jmeter to test is on Test domain. So there's the cross domain issue when trying to install an agent. We are trying to explore alternative way of trying to get around that by having the pipeline initiate the command line for master in the "Prod" domain machine to start the jmeter server. That machine will then trigger the slaves on the test domain to run the test. Not sure if that work but it's something we may have to explore. But your videos been a great helps in the initial set up
Thank you very much for the effort and time to share your expertise. I performed the test in my work test environment, it ran successfully but there was an "Error: Unknown option -e" showed in the command line script. The was results.jtl, and reports created. The Jmeter script generated and tested locally, passed. The script was generated using the url of the application that was being deployed. Kindly give me your input on this. Thanks again.
If we want to change the concurrent user,ramp up, duration. How to do that . Could you please make 1 video using YML file without jmeter installation. It will give more insights. Thanks in advance.
@@littleslawyoutubechannel I am using command in task Jmeter -n -t script.jmx -l results.jtl -e -o reports Jtl file is fine.. but index.html is coming blank
நன்றி , உங்களது விளக்கவுரை மிகவும் நன்றாக உள்ளது
🎉 Thanks bro
Thank you for the video. One thing I noticed when I had the pipeline set up as you described in previous video (with Install Jmeter tool in the task) is subsequences redeploy of the pipeline has much lower time in the "install Jmeter tool" steps. It doesn't even seems like it re-installing the jmeter each time. I agreed, the first time running the pipeline with the install Jmeter tool took a "long" time.
With this method of including the Jmeter in the repo (artifact), are we just shifting the time from the task to artifact (Artifact is now bigger than what it should be as it's now included JMeter)? btw this is a good alternative/option to the previous video.
I am planning on exploring another option: Have the Jmeter installed (on) agent (local) machine, create a system environment variable (Jmeter). In THEORY, when the command line "Jmeter -n ...." task kick in, it should use the local copy of the Jmeter to run the task and thus save from having to install Jmeter in the task or in the repo (artifact)
Thanks, I tried it too.. but it needs some more trial and error. Please let me know once you did that. Thanks again
@@littleslawyoutubechannel I will try that at work next week. At my work, there's other issues as well as we have different domain for testing. Basically, the Azure server is on prod domain and the machines with Jmeter to test is on Test domain. So there's the cross domain issue when trying to install an agent. We are trying to explore alternative way of trying to get around that by having the pipeline initiate the command line for master in the "Prod" domain machine to start the jmeter server. That machine will then trigger the slaves on the test domain to run the test. Not sure if that work but it's something we may have to explore. But your videos been a great helps in the initial set up
Yep sure, I can understand how difficult it is. Please let me know if you need any help, we will discuss
Thank you very much for the effort and time to share your expertise.
I performed the test in my work test environment, it ran successfully but there was an "Error: Unknown option -e" showed in the command line script. The was results.jtl, and reports created.
The Jmeter script generated and tested locally, passed. The script was generated using the url of the application that was being deployed. Kindly give me your input on this. Thanks again.
Can you please share me the complete error and it will be helpful for me to fix the issue
Thanks
@@littleslawyoutubechannel Generating script.
2023-07-11T16:46:54.5466458Z Script contents:
2023-07-11T16:46:54.5471766Z sudo jmeter -n -t HTTPRequest.jmx -l results.jtl -e -o reports
2023-07-11T16:46:54.5472052Z ========================== Starting Command Output ===========================
2023-07-11T16:46:54.5492623Z [command]/usr/bin/bash --noprofile --norc /agent/_work/_temp/1b371089-c12f-4b17-a306-e21a2f0.sh
2023-07-11T16:46:54.7784151Z Error: Unknown option -e
2023-07-11T16:46:54.7785245Z Try 'jmeter --help' for more information.
2023-07-11T16:46:54.7924760Z ##[section]Finishing: Command Line Script.
If we want to change the concurrent user,ramp up, duration. How to do that . Could you please make 1 video using YML file without jmeter installation. It will give more insights. Thanks in advance.
Let me check and get back to you bro. Thanks for asking
Let say, Sometimes we need run with 20, 50,70 user so there should be some YML file where we can change the number directly. Thanks
@vishalkumar-gv3lo sure will get back to you at the earliest
Hi, Any update on this JMeter release pipeline using YML file where we can change user duration and all
@vishalkumar-gv3lo I am working on it bro, please expect c something next week
Pipeline is passing but index.html is generating blank, please let me know how to resolve
Did the jmeter runs fine in local ??
@@littleslawyoutubechannel local means from my laptop it's working as usual
Okay so what is the your expected result , did you unzip the extracted folder to view the index file ?
@@littleslawyoutubechannel I am using command in task
Jmeter -n -t script.jmx -l results.jtl -e -o reports
Jtl file is fine.. but index.html is coming blank
Okay, let me check and get back to you .. thanks
I have below a comment which you asked me to present, I did not have a comment from you. Can you please review. Thank you
Let me check and get back to you at the earliest. Apologies for the delays
@@littleslawyoutubechannel can I get to you privately
Yes please mail me @vasanthtce@gmail.com
@@littleslawyoutubechannel I did but no reply, I did not use @ at the starting due to error.
What is your email id please