Jenkins build is back to normal : JMeter-trunk #6435

See

Build failed in Jenkins: JMeter-trunk #6434

See Changes: [pmouawad] Bug 61731 - Enhance Test plan Backup with option to save before run Add property to jmeter.properties Bugzilla Id: 61731 [pmouawad] Bug 61731 - Enhance Test plan Backup with option to save

buildbot success in on jmeter-trunk

The Buildbot has detected a restored build on builder jmeter-trunk while building . Full details are available at: https://ci.apache.org/builders/jmeter-trunk/builds/3152 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The AnyBranchScheduler

Build failed in Jenkins: JMeter-trunk #6433

See Changes: [pmouawad] Bug 61738 - Function Helper Dialog : Add Copy in Generate and clarify labels Bugzilla Id: 61738 [pmouawad] Extracted method and used streams to improve readability This closes #323

buildbot failure in on jmeter-trunk

The Buildbot has detected a new failure on builder jmeter-trunk while building . Full details are available at: https://ci.apache.org/builders/jmeter-trunk/builds/3147 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The AnyBranchScheduler

[GitHub] jmeter pull request #323: Extracted method and used streams to improve reada...

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/323 ---

[GitHub] jmeter pull request #322: General JavaDoc cleanup

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/322 ---

Jenkins build is back to normal : JMeter Ubuntu #254

See

Re: Workbench : Let's drop it ?

As you say, it’s oddity. A tool should be intuitive, this part is not, we cannot always say, rtfm. You know that lot of people don’t read docs. Let’s try and see if it is that complex. We shouldn’t say , we cannot touch, JMeter is not legacy, so we touch , break then fix . Regards On

Re: Workbench : Let's drop it ?

On 8 November 2017 at 16:18, Philippe Mouawad wrote: > Hello, > I’d say Test Plan. > I suggest testcompiler ignores them That would involve a lot of testing to ensure nothing broke. Are you sure it's worth it? There have been other instances where what seems to

Re: Workbench : Let's drop it ?

Hello, I’d say Test Plan. I suggest testcompiler ignores them Regards On Wednesday, November 8, 2017, Artem Fedorov wrote: > Hello, > > If we dropped WorkBench, in which element we can add Non-Test Elements > (HTTP Mirror Server, HTTP(S) Test Script Recorder,

Re: Workbench : Let's drop it ?

Hello, If we dropped WorkBench, in which element we can add Non-Test Elements (HTTP Mirror Server, HTTP(S) Test Script Recorder, Property Display)? Can we add these Non-Test Elements to Test Plan (root) or Test Fragment? Thanks

Build failed in Jenkins: JMeter Ubuntu #253

See Changes: [pmouawad] Formatting -- [...truncated 512.95 KB...] [jmeter] SLF4J: Class path contains multiple SLF4J bindings. [jmeter] SLF4J: Found binding in

Re: Workbench : Let's drop it ?

Great ! On Wed, Nov 8, 2017 at 2:38 PM, Andrey Pokhilko wrote: > FYI BlazeMeter will attempt to implement this change and contribute it. > > Andrey Pokhilko > > 04.11.2017 17:06, Andrey Pokhilko пишет: > > I'll need to think about it. > > > > Andrey Pokhilko > > > > 04.11.2017

Re: Workbench : Let's drop it ?

FYI BlazeMeter will attempt to implement this change and contribute it. Andrey Pokhilko 04.11.2017 17:06, Andrey Pokhilko пишет: > I'll need to think about it. > > Andrey Pokhilko > > 04.11.2017 17:01, Philippe Mouawad пишет: >> On Sat, Nov 4, 2017 at 2:52 PM, Andrey Pokhilko wrote:

Having Maven javadoc and source artifact deployed to maven

Hello, If there is a volunteer to implement this feature, it would be great: - https://bz.apache.org/bugzilla/show_bug.cgi?id=56368 It's about creating in Ant build.xml the zips for each bundle for javadocs and sources. It is really useful when users want to develop with JMeter. -- Regards.

[GitHub] jmeter issue #323: Extracted method and used streams to improve readability

Github user codecov-io commented on the issue: https://github.com/apache/jmeter/pull/323 # [Codecov](https://codecov.io/gh/apache/jmeter/pull/323?src=pr=h1) Report > Merging [#323](https://codecov.io/gh/apache/jmeter/pull/323?src=pr=desc) into

[GitHub] jmeter pull request #323: Extracted method and used streams to improve reada...

GitHub user ham1 opened a pull request: https://github.com/apache/jmeter/pull/323 Extracted method and used streams to improve readability You can merge this pull request into a Git repository by running: $ git pull https://github.com/ham1/jmeter save_refactor Alternatively