blazemeter/blazemeter-jenkins-plugin

Run a BlazeMeter test as part of your Jenkins continuous integration process.

blazemeter-jenkins-plugin's Issues

Search field in Tests dropdown is broken when you add the second BlazeMeter build step

[for Blazemeter/taurus] Build tries to write into /usr/local instead of the stage dir.

Sorry, but Blazemeter/taurus doesn't have the 'Issues' page.

Build fails:

Installing bzt script to /usr/ports/devel/py-taurus/work/stage/usr/local/bin
Installing jmx2yaml script to /usr/ports/devel/py-taurus/work/stage/usr/local/bin
Installing soapui2yaml script to /usr/ports/devel/py-taurus/work/stage/usr/local/bin
writing list of installed files to '/usr/ports/devel/py-taurus/work/.PLIST.pymodtmp'
[1.8.3] Creating /usr/local/etc/bzt.d
error: [Errno 13] Permission denied: '/usr/local/etc/bzt.d'
*** Error code 1

It attempts to install into the read-only directory while it is supposed to install into the stage directory. setup.py should install only into the provided stage directory.

setup.py is passed these arguments that it should use to determine the installation directory: --record /usr/ports/devel/py-ptrace/work/.PLIST.pymodtmp -c -O1 --prefix=/usr/local --single-version-externally-managed --root=/usr/ports/devel/py-ptrace/work/stage

Found this while trying to create a FreeBSD port.

Blazemeter Plugin version 4.9 introduces permission issues

After upgrading the plugin to 4.9, users with credentials create/update permissions at the folder level, lost ability to add or update credentials of any type.
We had to role back the plugin to version 4.7 to resolve the issue . This issue has been acknowledged by CloudBees as well - we are on CloudBees Jenkins Enterprise 2.289.2.3.

Move version.properties file to resource dir

Release 4.19 doesn't have valid pom.xml file

Hello,

Release 4.19 doesn't have a valid pom.xml file, as shown here: https://repo.jenkins-ci.org/releases/com/blazemeter/plugins/BlazeMeterJenkinsPlugin/4.19/

Without it, copies of the jenkins plugin mirror fail with the following:

2023-08-02 00:26:16.475+0000 [id=1]	WARNING	i.j.update_center.GitHubSource#init: Failed to obtain data from GitHub
java.net.ProtocolException: Too many follow-up requests: 21
Exception in thread "main" com.alibaba.fastjson.JSONException: Failed to retrieve content of https://repo.jenkins-ci.org/releases/com/blazemeter/plugins/BlazeMeterJenkinsPlugin/4.19/BlazeMeterJenkinsPlugin-4.19.pom (cached)
Caused by: java.io.IOException: Failed to retrieve content of https://repo.jenkins-ci.org/releases/com/blazemeter/plugins/BlazeMeterJenkinsPlugin/4.19/BlazeMeterJenkinsPlugin-4.19.pom (cached)

Request timed out behind corporate proxy

Hi, I'm using the plugin behind a corporate proxy.

I have env vars HTTPS_PROXY HTTP_PROXY http_proxy and https_proxy set in all the jenkins environments. In addition to that I have the Proxy set in the Manage Jenkins> Manage Plugins > Advanced. -- I can actually test the url here, and it passes.
In addition I'm actually starting the master with following JAVA_OPTS

        "-Dhttp.proxyPort=8080" "-Dhttps.proxyHost=foo"
        "-Dhttps.proxyPort=8080" "-Dhttp.nonProxyHosts=foo"

If I try to test the credentials in the global credential store I get request timed out. If I try to preview the pipeline syntax in the dsl generator I get Check Proxy settings. If I try to POST or get to /descriptorByName/hudson.plugins.blazemeter.BlazemeterCredentialsBAImpl/validate I get timed out there too.

Is this plugin /really/ using the proxy settings I've set in the Jenkins environment?

Blazemeter plugin generate empty junit report

I am running blazemeter from jenkins using the plugin and i have set properties to generate junit report. it comes back empty with no test results even though test was executed. also time stamp seems bad

generated file:

<?xml version="1.0" encoding="UTF-8"?>
<testsuites>
   <testsuite name="JUnitXmlReporter" errors="0" tests="0" failures="0" time="0" timestamp="2013-05-24T10:23:58" />
   <testsuite name="JUnitXmlReporter.constructor" errors="0" skipped="0" tests="0" failures="0" time="0.006" timestamp="2013-05-24T10:23:58">
      <properties>
         <property name="java.vendor" value="BlazeMeter Ltd." />
         <property name="compiler.debug" value="on" />
         <property name="project.jdk.classpath" value="jdk.classpath.1.6" />
      </properties>

   </testsuite>
</testsuites>