jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: svn commit: r36676 - in /release/jmeter: binaries/ source/
Date Sat, 09 Nov 2019 12:31:11 GMT
On Sat, 9 Nov 2019 at 11:15, Vladimir Sitnikov
<sitnikov.vladimir@gmail.com> wrote:
>
> I've added removeStaleArtifacts which is automatically run after publishing
> the release to /release/jmeter/...

That is too soon.
Should wait until mirrors have had a chance to catch up and the
release is announced before removing old versions.

As per https://cwiki.apache.org/confluence/display/JMETER/ReleaseCreation

Which now needs updating.

> The task can be called manually:
> $ gw removeStaleArtifacts -PasfDryRun -Pjmeter.version=5.2 # keep 5.2
> artifacts, and print the files to be removed
> $ gw removeStaleArtifacts -Pasf -Pjmeter.version=5.2 # keep 5.2 artifacts,
> and remove the other files

That looks fine, except it's not obvious why the -Pasf property is needed

> The set of files to keep is configured in /build.gradle.kts
> -> staleRemovalFilters { ... }
>
> The missing bit is to drop stale Nexus staging repositories.

I don't remember doing that, and it's not in the wiki page cited above.

AFAIK Nexus tidies itself up eventually.

I suppose it would do no harm, and might make it a bit easier to navigate.
But I don't think it's necessary.
Before spending any time on it, I suggest checking whether it's
necessary or not.

> It could be implemented as
> https://github.com/gradle-nexus/publish-plugin effort
> stabilizes.
>
> Vladimir

Mime
View raw message