Simon Baslé <sbasle@vmware.com>: Author Summary

Builds triggered by Simon Baslé <sbasle@vmware.com>

Builds triggered by an author are those builds which contains changes committed by the author.
240
24 (10%)
216 (90%)

Breakages and fixes

Broken means the build has failed but the previous build was successful.
Fixed means that the build was successful but the previous build has failed.
21 (9% of all builds triggered)
17 (7% of all builds triggered)
-4
Build Completed Code commits Tests
REACTOR › REACTORBOM › #280 2 days ago
Merge #697 into Europium
GitHub Actions Release Process (#697)
This commit changes the release process to be based on GitHub Actions.

No CI is currently running for the BOM.

We define helper tasks and methods in the setup.gradle file to help
interpret the version number. The trigger is pushing a commit to an
active maintenance branch.

The new workflow uses GitHub Environments to manage access to secrets,
especially in the case of milestones and releases as it introduces
signing of artifacts in these cases. It is split into 4 jobs, 3 of
which are conditional and depend on a GitHub Environment.

Notably:
 - Add a function to qualify a BOM version as one of RELEASE,
 MILESTONE, SNAPSHOT or BAD. Recognizes `Dysprosium` as old scheme.
 - Add a GitHub Actions oriented task, `qualifyVersionGha`, which
 produces gha step output for the current project version. `versionType`
 is an application of the above function and `fullVersion` is the plain
 project's `version`
 - tag releases and milestones using `git` commands in `prepare` job, without
 a `v` prefix (this is the BOM)
 - Activate the JFrog Artifactory plugin only if a password is defined
 (including in subprojects)
 - Add the `signing` plugin, activated only if a signing key is defined,
   requiring that signing be performed if a publish task is invoked
 - Add a Maven publication repository if Sonatype OSS credentials are
   defined
 - Add a `mock` maven repository target and a `-PforceSigning` option
 for debugging purposes
 - Use the GHA RUN_NUMBER as the build id in Artifactory

See reactor/reactor#694.
See reactor/reactor-addons#254.
Testless build
REACTOR › RPOOL › #162 2 days ago
Merge #132 into 0.2.4
GitHub Actions Release Process: signing, artifactory, sonatype (#132)
This commit changes the release process to be based on GitHub Actions.

CI is already performed on GHA, but that workflow will now only run
for pull_request trigger.

We define helper tasks and methods in the setup.gradle file to help
interpret the version number. The trigger is pushing a commit to an
active maintenance branch.

The new workflow uses GitHub Environments to manage access to secrets,
especially in the case of milestones and releases as it introduces
signing of artifacts in these cases. It is split into 4 jobs, 3 of
which are conditional and depend on a GitHub Environment.

Notably:
 - Add a function to qualify a version number as one of RELEASE,
 MILESTONE, SNAPSHOT or BAD
 - Add a GitHub Actions oriented task, `qualifyVersionGha`, which
 produces gha step output for the current project version. `versionType`
 is an application of the above function and `fullVersion` is the plain
 project's `version`
 - tag releases and milestones using `git` commands in `prepare` job
 - Activate the JFrog Artifactory plugin only if a password is defined
 (including in subprojects)
 - Add the `signing` plugin, activated only if a signing key is defined,
   requiring that signing be performed if a publish task is invoked
 - Add a Maven publication repository if Sonatype OSS credentials are
   defined
 - Add a `mock` maven repository target and a `-PforceSigning` option
 for debugging purposes
 - Use the GHA RUN_NUMBER as the build id in Artifactory

See reactor/reactor#694.
See reactor/reactor-addons#254.
Fixes #116.
Testless build
REACTOR › RNEXT › #3067 3 days ago
[chores] Remove Sergei as codeowner of reactor-tools
Merge 76149a949 into 3.4.5
Testless build
REACTOR › RPOOL › #161 4 days ago
Merge #131 in 0.2.4
Merge #130 into 0.2.4
Only increment acquiredSize() once resource has been allocated (#130)
This commit ensures the acquiredSize() metric is only updated when the
resource has been allocated, and is about to be handed off to the
subscriber of acquire().

The decrement in case of allocation error is thus not needed anymore.

Fixes #126.
Make log quieter in CommonPoolTest#pendingLimitAsync (#131)
The test would log an `ErrorCallbackNotImplemented` but the error is
actually evaluated in a `doOnError`, so we can suppress this output
by subscribing with an empty error handler.

Fixes #125.
363 passed
REACTOR › RPOOL › #160 4 days ago
Merge #129 into 0.2.4
japicmp is still baselining against 0.1.x, but now the latest release:
0.1.9.RELEASE.
Implementation review, make a few small improvements... (#129)
This commit fixes a few low hanging fruits in the current pool
implementation:

 - Remove PENDING_COUNT and rely on `Queue#size()` directly instead
 - isDisposed also checks IDLE_RESOURCES is null
 - Remove WIP lazySets to prevent re-entry in terminal state
 - In drain loop, return slot if no borrower and invalidate slot
   if pool disposed. These case are protective against polling
   an unexpected null in the drain loop, although the conditional
   branches are reviewing the actual queue sizes.
 - In tests, make the switch to new RaceTestUtils methods
 - Ensure japicmp compares with the latest release as baseline

This commit also adds a few remaining TODOs.
359 passed
REACTOR › RKAFKA › #936 1 week ago
Merge #209 into 1.3.4
Remove JCenter from build (#209)
See reactor/reactor#695.
158 passed
REACTOR › RNEXT › #3066 1 week ago
Remove jcenter() from build, update jcstress plugin to 0.8.8 (#2666)
On top of being used as a repository, JCenter was also used to
retrieve the baseline jars for japicmp. This is now based on Maven
Central.

This also bumps the jcstress-gradle-plugin to 0.8.8 which allows
to unpin the version of jcstress executable.

See reactor/reactor#695.
Merge #2666 into 3.4.5
Testless build
REACTOR › KOTLIN › #91 1 week ago
Remove JCenter from build, temporarily fix plugin resolution (#23)
Somehow Gradle complains that repo.spring.io plugin repository doesn't
contain the dokka jar, even though mavenCentral() is listed first and
said jar is now on Maven Central. Thus we added a `content` block to
enforce the spring repo is only used to resolve spring gradle plugins.

See reactor/reactor#695.
Merge #23 into 1.1.2
131 passed
REACTOR › RNEXT › #3065 1 week ago
Remove Fuseable from MonoSingle[Mono|Callable] (#2668)
This commit fixes a regression where a ClassCastException would
be thrown at runtime when `single()` was used with a fused source
and a fuseable downstream.

This was due to MonoSingleMono and MonoSingleCallable implementing
the Fuseable interface without providing a QueueSubscription to
their downstream, so the fusion has been removed from these two
Publishers.

Fixes #2663.
Merge #2668 into 3.4.5
7811 passed
REACTOR › REACTORBOM › #279 1 week ago
Remove JCenter from build (#696)
See reactor/reactor#695.
Merge #696 into Europium
Testless build
Build Completed Code commits Tests
REACTOR › REACTORBOM › #280 2 days ago
Merge #697 into Europium
GitHub Actions Release Process (#697)
This commit changes the release process to be based on GitHub Actions.

No CI is currently running for the BOM.

We define helper tasks and methods in the setup.gradle file to help
interpret the version number. The trigger is pushing a commit to an
active maintenance branch.

The new workflow uses GitHub Environments to manage access to secrets,
especially in the case of milestones and releases as it introduces
signing of artifacts in these cases. It is split into 4 jobs, 3 of
which are conditional and depend on a GitHub Environment.

Notably:
 - Add a function to qualify a BOM version as one of RELEASE,
 MILESTONE, SNAPSHOT or BAD. Recognizes `Dysprosium` as old scheme.
 - Add a GitHub Actions oriented task, `qualifyVersionGha`, which
 produces gha step output for the current project version. `versionType`
 is an application of the above function and `fullVersion` is the plain
 project's `version`
 - tag releases and milestones using `git` commands in `prepare` job, without
 a `v` prefix (this is the BOM)
 - Activate the JFrog Artifactory plugin only if a password is defined
 (including in subprojects)
 - Add the `signing` plugin, activated only if a signing key is defined,
   requiring that signing be performed if a publish task is invoked
 - Add a Maven publication repository if Sonatype OSS credentials are
   defined
 - Add a `mock` maven repository target and a `-PforceSigning` option
 for debugging purposes
 - Use the GHA RUN_NUMBER as the build id in Artifactory

See reactor/reactor#694.
See reactor/reactor-addons#254.
Testless build
REACTOR › RPOOL › #162 2 days ago
Merge #132 into 0.2.4
GitHub Actions Release Process: signing, artifactory, sonatype (#132)
This commit changes the release process to be based on GitHub Actions.

CI is already performed on GHA, but that workflow will now only run
for pull_request trigger.

We define helper tasks and methods in the setup.gradle file to help
interpret the version number. The trigger is pushing a commit to an
active maintenance branch.

The new workflow uses GitHub Environments to manage access to secrets,
especially in the case of milestones and releases as it introduces
signing of artifacts in these cases. It is split into 4 jobs, 3 of
which are conditional and depend on a GitHub Environment.

Notably:
 - Add a function to qualify a version number as one of RELEASE,
 MILESTONE, SNAPSHOT or BAD
 - Add a GitHub Actions oriented task, `qualifyVersionGha`, which
 produces gha step output for the current project version. `versionType`
 is an application of the above function and `fullVersion` is the plain
 project's `version`
 - tag releases and milestones using `git` commands in `prepare` job
 - Activate the JFrog Artifactory plugin only if a password is defined
 (including in subprojects)
 - Add the `signing` plugin, activated only if a signing key is defined,
   requiring that signing be performed if a publish task is invoked
 - Add a Maven publication repository if Sonatype OSS credentials are
   defined
 - Add a `mock` maven repository target and a `-PforceSigning` option
 for debugging purposes
 - Use the GHA RUN_NUMBER as the build id in Artifactory

See reactor/reactor#694.
See reactor/reactor-addons#254.
Fixes #116.
Testless build
REACTOR › RNEXT › #3066 1 week ago
Remove jcenter() from build, update jcstress plugin to 0.8.8 (#2666)
On top of being used as a repository, JCenter was also used to
retrieve the baseline jars for japicmp. This is now based on Maven
Central.

This also bumps the jcstress-gradle-plugin to 0.8.8 which allows
to unpin the version of jcstress executable.

See reactor/reactor#695.
Merge #2666 into 3.4.5
Testless build
REACTOR › KOTLIN › #86 3 weeks ago
Prepare release 1.1.3
 - core is bumped to 3.4.4
 - addons is brought back to 3.4.2
131 passed
REACTOR › NETTYWIN › #1382 3 weeks ago
Remove all occurrences of jcenter() in build
Merge 8d1de345 into 1.0.5
Also switched from jcenter to mavenCentral in sub-modules for japicmp.
Testless build
REACTOR › RNETTY › #2456 3 weeks ago
Remove all occurrences of jcenter() in build
Merge 8d1de345 into 1.0.5
Also switched from jcenter to mavenCentral in sub-modules for japicmp.
Testless build
REACTOR › REACTORRMQ › #465 3 weeks ago
Prepare release 1.5.2
1 of 105 failed
REACTOR › RPOOL › #153 3 weeks ago
Prepare release 0.2.3
Testless build
REACTOR › RNEXT › #3025 1 month ago
Merge #2567 into 3.4.3
1 of 7410 failed
REACTOR › RNEXT › #3010 2 months ago
Merge #2574 into 3.4.3
[build] Enforce NoHTTP with plugin and relevant exclusions (#2574)
Testless build
Build Completed Code commits Tests
REACTOR › NETTYWIN › #1383 3 weeks ago
Prepare release 1.0.5
900 passed
REACTOR › REACTORRMQ › #467 3 weeks ago
Fix Prepare release: remove jcenter() from build
105 passed
REACTOR › RPOOL › #154 3 weeks ago
Fix Prepare release 0.2.3 - remove jcenter()
359 passed
REACTOR › RNEXT › #3047 3 weeks ago
Merge-ignore release 3.3.15.RELEASE into master
Prepare release 3.3.15.RELEASE
7768 passed
REACTOR › RNEXT › #3027 1 month ago
Polish after #2576: ScalarSubscription has RunStyle.SYNC (#2613)
This commit makes ScalarSubscription advertise a RunStyle.SYNC, which
can be safely assumed of any ScalarSubscription, and is congruent with
the RunStyle of `FluxJust` prior to it switching to the mutualized
implementation.
7737 passed
REACTOR › RNEXT › #3016 2 months ago
Merge #2581 into 3.4.3
 - also fixed Mono.timed
 - also fixed Mono.metrics
7714 passed
REACTOR › RNEXT › #3011 2 months ago
Polish #2574 on master (fix additional http in svgs)
7705 passed
REACTOR › RNEXT › #3002 2 months ago
Prepare release 3.4.2
7701 passed
REACTOR › RNEXT › #2989 4 months ago
[build] Add jcenter for plugins too
Merge ee947ff9 (jcenter for plugins) to 3.3.12.RELEASE
Merge ee947ff9 (jcenter for plugins) to 3.4.1
7656 passed
REACTOR › RKAFKA › #911 4 months ago
Merge #186 into 1.3.1
156 passed