Build failed in Jenkins: JMeter-trunk #7292

See Changes: [felix.schumacher] Describe usage of gradle properties for proxy settings -- [...truncated 101.08 KB...] org.bouncycastle.util.Selector org.bouncycastle.cert.

Jenkins build is back to normal : JMeter Windows #1433

See

Re: buildbot exception in on jmeter-nightly

Am 4. August 2019 13:49:45 MESZ schrieb Vladimir Sitnikov : >>jenkins are publishing their snapshots both into the same destination. > >Jenkins is not publishing yet. >5.2.0-20190804.102941 is something I have deployed from my machine. OK, so nightly builds are not a complete waist, yet :) W

Re: buildbot exception in on jmeter-nightly

>jenkins are publishing their snapshots both into the same destination. Jenkins is not publishing yet. 5.2.0-20190804.102941 is something I have deployed from my machine. Vladimir

Re: buildbot exception in on jmeter-nightly

Am 04.08.19 um 13:40 schrieb Vladimir Sitnikov: > Felix>I can remove clean step. > > I have no strong preference there. > > PS. I wonder if all those steps can be configured via Jenkins. > It would probably easier to support one CI server instead of two (Jenkins > and Buildbot). Looking at https

Re: buildbot exception in on jmeter-nightly

Felix>I can remove clean step. I have no strong preference there. PS. I wonder if all those steps can be configured via Jenkins. It would probably easier to support one CI server instead of two (Jenkins and Buildbot). Vladimir

Re: buildbot exception in on jmeter-nightly

Am 04.08.19 um 12:46 schrieb Vladimir Sitnikov: >>https://ci.apache.org/builders/jmeter-nightly/builds/1432 > Technically speaking, "clean" could be omitted. > > In other words, if you find a case when "clean" is required for > "successful/good/whatever" build, that means there's a bug in bui

Re: [VOTE] JMeter: migration to Git+Gradle

Am 04.08.19 um 12:50 schrieb Vladimir Sitnikov: > Felix>The old dist artifacts had sha512 checksums in the same folder. I > didn't > see them in the gradle build ones. Can they be generated, too? > > Use ./gradlew :src:dist:assemble > Or you can use individual distTar distZip signDistTar signDis

buildbot success in on jmeter-nightly

The Buildbot has detected a restored build on builder jmeter-nightly while building . Full details are available at: https://ci.apache.org/builders/jmeter-nightly/builds/1436 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave7_ubuntu Build Reason: forced: by IRC user

buildbot failure in on jmeter-nightly

The Buildbot has detected a new failure on builder jmeter-nightly while building . Full details are available at: https://ci.apache.org/builders/jmeter-nightly/builds/1435 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave7_ubuntu Build Reason: forced: by IRC user on

Re: [VOTE] JMeter: migration to Git+Gradle

Felix>The old dist artifacts had sha512 checksums in the same folder. I didn't see them in the gradle build ones. Can they be generated, too? Use ./gradlew :src:dist:assemble Or you can use individual distTar distZip signDistTar signDistZip Credentials are managed by https://docs.gradle.org/curr

Re: buildbot exception in on jmeter-nightly

>https://ci.apache.org/builders/jmeter-nightly/builds/1432 Technically speaking, "clean" could be omitted. In other words, if you find a case when "clean" is required for "successful/good/whatever" build, that means there's a bug in build script. Extra "clean" would probably not hurt for a C

Re: [VOTE] JMeter: migration to Git+Gradle

Am 03.08.19 um 18:17 schrieb Felix Schumacher: > Am 03.08.19 um 14:22 schrieb Felix Schumacher: >> Am 03.08.19 um 14:15 schrieb Vladimir Sitnikov: >>> Felix>It generates artifacts >>> >>> This is handled by `distTar distTarSource distZip distZipSource` (pick the >>> ones that are required) >> I w

buildbot exception in on jmeter-nightly

The Buildbot has detected a build exception on builder jmeter-nightly while building . Full details are available at: https://ci.apache.org/builders/jmeter-nightly/builds/1432 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave7_ubuntu Build Reason: forced: by IRC user