On 28/08/2018 19:58, Philippe Mouawad wrote:
Hello,
Pinging again on this.
JMeter 4.0 is now 6 month away and we have a very decent version with 39
Enhancements and 45 Bug fixes.
The pending issues already existed and are not blocking IMO. I've been
using JMeter 5.0 for load testing without issue.
1/ When can we start the release process ?
When we decide together. This week if PMCs are agree.
2/ I think it would also be a good occasion to look with a critical eye at
this release process to find ways to reduce its complexity and duration
- too manual, too much setup:
- See https://wiki.apache.org/jmeter/ReleaseCreation
- I for example would like to do this one time but I am on mac and
don't want to scratch my head just to find and install svnmucc
You can setup a linux virtual machine or a linux docker container into
your mac, and make the release distribution.
- every time there is at least a RC0 that is burnt because of some
manual step or a broken file svn:eol....
You're right. A lot of steps are manual...
- how could we improve ?:
- jenkins job ?
- docker image for release ?
- Other ideas ?
If you looks the release steps, you can see a lot of steps with the need
of an authentication : svn, maven upload, RC gpg sign. So if you want
automate these, that would be difficult (or not possible) because the
credentials must be provided.
Thus, a lot of steps are manual because the step need an human checks
(javadoc warning, archive checks, RAT report, etc)
And some steps are manual and (AFAIK) cannot be automate like the Nexus
release action
Perhaps add a Dockerfile to the project can help to have an local build
environment without the matter of OS of the developer machine. (we have
this way under the CloudStack project)
Otherwise, migrate the project to apache gitbox/github could provide a
different way to build the release and perhaps reduce some manual steps.
Milamber
Regards
On Sat, Aug 4, 2018 at 5:19 PM Philippe Mouawad <philippe.moua...@gmail.com>
wrote:
On Saturday, August 4, 2018, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:
Am 2. August 2018 19:37:27 GMT+01:00 schrieb Philippe Mouawad <
philippe.moua...@gmail.com>:
Hi Felix,
Did you have time to look at this ?
Sorry, haven't found the time, yet. But I think I had to add a listener
(probably result tree view) to get the exceptions.
I guess issue exists since many versions, should it block release ?
Regards,
Felix
Thanks
On Sat, Jul 28, 2018 at 10:00 PM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:
On Sat, Jul 28, 2018 at 6:49 PM, Felix Schumacher <felix.schumacher@
internetallee.de> wrote:
Am Samstag, den 28.07.2018, 17:29 +0200 schrieb Philippe Mouawad:
Hello,
@Felix, I reviewed the PR for the 62463, it looks good to me.
We could release with 62570 not fixed as it's an enhancement
The fix for 62463 is only a partial fix. Try to run a distributed
load
test with fixed rmi port in the GUI. You will get exceptions, as the
(remote) listeners will be instantiated more than one time and try
to
bind to the same fixed port.
I am not sure to understand exactly what the bug is .
I recently ran a NON Gui distributed test and had no issues.
Do it happens with any test plan, only in GUI mode ... ?
It is not clear to me, what we should do with those listeners.
Which ones ?
1) they seem to be intended rather globally, but are local to a
thread
group. I think this is odd, at least
2) the should probably not be instantiated (cloned?) more than once
in
a test run
What was the original intention for those listeners? Can they be
implemented as global singleton like objects? If not, how is the
other
side of the remote connection able to distinguish those objects?
For 62570 (enhancement related to validity of CA), I think I would
be a
good idea to add the hint about the property to the dialog that
appears
after the creation of a new CA. All further enhancements on this
case
can wait.
yes, ok for me.
Regards,
Felix
Once committed, can we start a release 5.0 ?
We haven't released since
On Sun, Jul 8, 2018 at 10:44 AM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:
Thanks for feedback.
Usually it’s a good thing to test integrity with sha of the file
and
compare it with the value we advertise.
Regards
On Sunday, July 8, 2018, Jmeter Tea <jmeter...@gmail.com> wrote:
I downloaded again and now it's working, maybe I had a problem
with
downloading
Thank you
On Sun, Jul 8, 2018 at 11:35 AM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:
Hello,
Which file did you download and from which link ?
Thank you
On Sunday, July 8, 2018, Jmeter Tea <jmeter...@gmail.com>
wrote:
Hi
I download latest nightly r1835292 and it failed to run
due
to missing
files in bin folder as
jmeter.properties and log4j2.xml
FYI
On Thu, Jul 5, 2018 at 11:47 PM, Philippe Mouawad <
p.moua...@ubik-ingenierie.com> wrote:
Hello,
We have currently 64 bugs/enhancements implemented in
trunk
that
would
deserve a Major new version 5.0 :
- https://bz.apache.org/bugzilla/buglist.cgi?bug_
status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&
component=HTTP&component=Main&list_id=170488&order=
Importance&product=JMeter&query_format=advanced&
resolution=FIXED&target_
milestone=JMETER_4.1
<https://bz.apache.org/bugzilla/buglist.cgi?bug_
status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&
component=HTTP&component=Main&list_id=170488&order=
Importance&product=JMeter&query_format=advanced&
resolution=FIXED&target_
milestone=JMETER_4.1>
I think last commits deserve a deep review /tests
related
to :
- Flow Control Action
- Result Status Action
- Iterating Controllers
If nobody finds a bug, the new version 5.0 should be
released.
I propose to send a mail on user mailing list with
following
content:
---------------------------------------------------------
---
------------------------------------------------
We'd like to release a new version 5.0 with following
enhancements /
bugfixes.
We'd like tests and feedback from users.
If you'd like to help testing, you can download a
nightly
build
tomorrow:
- https://ci.apache.org/projects/jmeter/nightlies/
Test particularly:
- Recording
- Flow Control Action (old Test Action)
- Result Status Action (break loop, switch to next
iteration of
current
loop)
- While Controller / Loop Controller / Foreach
Controller
We'll be waiting for 10 days.
---------------------------------------------------------
---
------------------------------------------------
--
Regards.
Philippe M.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
