[Jmeter] Update new jar dependencies

[OUFDOU Anas <ao...@sqli.com>]

Hello,

I see there are many dependencies not uptodate on Jmeter, maybe adding the
gradle plugin like  to build (
https://github.com/ben-manes/gradle-versions-plugin) will help to have a
report on updatable dependencies.
Another question regarding CI, I see tarvis, github action and Jenkins are
used in Jmeter. What is the main CI ?

In attachment the report  for Jmeter

Re: [Jmeter] Update new jar dependencies

[OUFDOU Anas <ou...@gmail.com>]

Thanks for your quick response ,

If I understand you response
For CI:

   1. Jenkins is used for critical/securised action like publishing ...
   2. Travis is the main CI, and the main reason for still using it is
   testing with s390x hardware?
   3. Github is the new CI and may replace definitively Travis CI in the
   future.

For Check update : we have at least 4 choices:

   1. https://github.com/renovatebot/renovate : +6k stars
   2. https://github.com/ben-manes/gradle-versions-plugin: +3k stars
   3. https://github.com/jmfayard/refreshVersions : +1k stars
   4. https://github.com/palantir/gradle-consistent-versions : +70 stars


Best regards



:

On Mon, Dec 13, 2021 at 7:21 AM Vladimir Sitnikov <
sitnikov.vladimir@gmail.com> wrote:

> >Another question regarding CI, I see tarvis, github action and Jenkins are
> used in Jmeter. What is the main CI ?
>
> It is complicated. All of them add value.
> I would inline to GitHub Actions, however, we can't drop all Travis and all
> Jenkins jobs.
>
> There's https://github.com/renovatebot/renovate bot that can be integrated
> with Gradle, however, I have not explored that option.
>
> >gradle plugin like  to build (
> https://github.com/ben-manes/gradle-versions-plugin)
>
> There's https://github.com/jmfayard/refreshVersions which is good.
> The only sad thing is that it does not support composite builds (see
> https://github.com/jmfayard/refreshVersions/issues/205).
> "composite build" is the idiomatic Gradle way of structuring the build
> logic (see
>
> https://docs.gradle.org/current/userguide/structuring_software_products.html
> )
>
> https://github.com/palantir/gradle-consistent-versions is good as well
>
> Travis used to be the primary CI, however, it becomes limited nowadays.
>
> The key Travis features for now are:
> * testing with s390x hardware
> * collecting code coverage information <-- this can (should) be moved to
> GitHub, however, it has not been done yet
>
> ASF Jenkins:
> * It allows publishing Maven snapshots to the ASF Nexus repository
> https://repository.apache.org/ without sharing credentials with non-ASF
> systems.
> * It makes it easier to publish HTML reports as a part of the build
>
> Unfortunately, we can't easily enable PR builds for ASF Jenkins as we can't
> run arbitrary (untrusted) code in the ASF environments.
>
> GitHub:
> * It allows PR builds even for untrusted code
>
> Buildbot:
> * We use it to publish nightly builds, however, I have no idea how it is
> configured.
>
> Vladimir
>


-- 
Cordialement,
-------------
Anas OUFDOU

Re: [Jmeter] Update new jar dependencies

[Vladimir Sitnikov <si...@gmail.com>]

>Another question regarding CI, I see tarvis, github action and Jenkins are
used in Jmeter. What is the main CI ?

It is complicated. All of them add value.
I would inline to GitHub Actions, however, we can't drop all Travis and all
Jenkins jobs.

There's https://github.com/renovatebot/renovate bot that can be integrated
with Gradle, however, I have not explored that option.

>gradle plugin like  to build (
https://github.com/ben-manes/gradle-versions-plugin)

There's https://github.com/jmfayard/refreshVersions which is good.
The only sad thing is that it does not support composite builds (see
https://github.com/jmfayard/refreshVersions/issues/205).
"composite build" is the idiomatic Gradle way of structuring the build
logic (see
https://docs.gradle.org/current/userguide/structuring_software_products.html
)

https://github.com/palantir/gradle-consistent-versions is good as well

Travis used to be the primary CI, however, it becomes limited nowadays.

The key Travis features for now are:
* testing with s390x hardware
* collecting code coverage information <-- this can (should) be moved to
GitHub, however, it has not been done yet

ASF Jenkins:
* It allows publishing Maven snapshots to the ASF Nexus repository
https://repository.apache.org/ without sharing credentials with non-ASF
systems.
* It makes it easier to publish HTML reports as a part of the build

Unfortunately, we can't easily enable PR builds for ASF Jenkins as we can't
run arbitrary (untrusted) code in the ASF environments.

GitHub:
* It allows PR builds even for untrusted code

Buildbot:
* We use it to publish nightly builds, however, I have no idea how it is
configured.

Vladimir