perftest | Automate performance tests on Amazon EC2 | AWS library

#1 - its possible via CLI commands (appcmd & netsh) or scripting (PowerShell) and programming (c#) but not with the IIS Manager GUI afaik.

#2 - (see #1). IIS Manager is stupid and will overwrite existing bindings with the last certificate selected. You end up with bindings attached to the wrong certificate if you click Yes. This is a limitation of IIS Manager GUI not IIS.

#3 - You want SNI turned on. It means you can have multiple certificates associated with the same IP address. Without SNI you would need 1 IP address per certificate

These 2 links will give you an idea how to use appcmd and netsh - this is the quickest/easiest way to create your desired configuration.

1. Adding a HTTPS binding to a site
2. Binding a certificate with netsh

If you know PowerShell("POSH") you can use the IISAdministration PowerShell cmdlet New-IISSiteBinding to create bindings and associate with a certificates thumbprint (though netsh is still useful for debugging and fixing issues).

Either approach your really configuring 2 things - IIS' bindings and Windows/SChannel/HTTPS.sys (the operating system component actually responsible for the 'S' in 'HTTPS'). Sometimes they get out of sync and the easiest fix is to delete and re-create the bindings (after clicking yes to "At least one other site is using the same HTTPS binding..." for example).

Few tips:

• Once you start using this configuration IIS Manager or Windows Update/software installs will probably break your bindings at some point. Write a script that can remove and re-create all your bindings for port 443(only!) so you can easily fix future issues.
• If you use netsh - its very fussy about the syntax. Order and spacing of parameters are important when using command netsh http add sslcert.
• While your testing netsh http show sslcert and netsh http delete sslcert are very useful to try different configurations (this wont delete the cert, just the binding)
• Cert needs to be in the Machine certificate store and make a note of the path. When using POSH or netsh always specify both certificate thumbprint and the store\path where the cert was installed.
• If you need a default HTTPS binding on the IIS Site (eg load balancer healthchecks etc) add it before any named HTTPS bindings.

Final aside - if your domains are all 1 level under abc.com getting a wildcard certificate would save you a lot of bother. a single *.abc.com certificate would cover all your domains and you can avoid this limitation entirely.

Good luck!

I had a similar problem, not exactly the same, and to solve it I just had to click that Hide Preview Features button.

apparently Google released some new features that are all broken in the new Front-end, but not in the old

Your YAML is very nice but it doesn't tell anything about how do you launch JMeter or what these shell scripts you invoke are doing.

If you just kick off 2 separate JMeter instances by means of k8s - JMeter will look at the number of active threads from the .jtl file and given the Sampler/Transaction names are the same JMeter "thinks" that the tests were executed on one engine.

The workaround is to add i.e. machineName() or __machineIP() function to sampler/transaction labels, this way JMeter will distinguish the results coming from different instances and you will see real number of active threads.

The solution would be running your JMeter test in Distributed Mode so master will run in one pod, slaves in their own pods and the master will be responsible for transferring .jmx script to the slaves and collecting results from them

It looks you ran your pipeline on self-hosted agent. Or you configured the maven to retrieve the dependencies from the local repository(in mvnsettings.xml, or .m2/settings.xml ). If you ran your pipeline on self-hosted agent. You can check if the local repo /testartifacts/m2repository exists.

If you run your pipeline on cloud agents, you need to find which setting files configured the the local repo, And remove the localRepository.

Then you might need to use Maven Authenticate task to provides credentials for Azure Artifacts feeds and external Maven repositories.

Add Maven Authenticate task at the top of your pipeline. And select your azure maven feed from the Feeds dropdown list

This task will store the credentials on a temp settings.xml file(with feed name as the server id, see below) on the agent, which will be used to authenticate the maven repository in the following maven task.

Noted: The repository id you specified in your pom.xml file(ie. see below highlighted) should be the same with the name of your azure artifacts maven feed. Or it will still fail to authenticate the feed in the follow maven task. for the server id in the temp settings.xml file created above is the feed name.

This is what you are looking for, these docs explain how to use parameters when extending from templates.

In short it means you define all steps in the template yaml file and pass parameter values from the extending yaml file. Keep in mind you can also pass buildsteps as parameter, see here for an example.

See below for a few snippets based on your case.

pipeline-template.yml in repository named TemplateRepo