Simon Baslé <[email protected]>: Author Summary

Builds triggered by Simon Baslé <[email protected]>

Builds triggered by an author are those builds which contains changes committed by the author.
248
26 (10%)
222 (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.
23 (9% of all builds triggered)
18 (7% of all builds triggered)
-5
Build Completed Code commits Tests
REACTOR › SITE2 › #26 2 weeks ago
[polish] Apply spotless in CI only for pull_request events
[chores] Copyright switch from Pivotal to VMware, polish headers (#68)
This commit changes the copyright header from Pivotal to VMware.

It ensures that all occurrences of "Pivotal" are turned into their
VMware equivalent (notably links to eg. security policy).

It also polishes the copyright notice headers using the newly introduced
Spotless plugin as well as some manual editing:

 - format the header (blank line, url)
 - recompute the start year of the copyright notice range from git
 history for java files
 - align end year of said ranges to 2021
 - ensure headers for misc files (html, js, css) is also updated and
 formatted

 See reactor/reactor#682.
Released 2020.0.9
[build] Add Spotless plugin to enforce license headers (#68)
This commit introduces Spotless plugin and configures it to allow
checking and enforcing copyright notice headers via a template, for
java files only.

The license check is added to the ci workflow, ensuring only files
touched by a PR will get checked (in order to allow incremental updates
to the end of the year range).

The build can be parameterized to deactivate the ratchet feature ("only
changed files" vs "all files") or choose a difference base branch for
comparison.

See reactor/reactor#701.
Testless build
REACTOR › SITE2 › #25 1 month ago
Released Dysprosium-SR21 and 2020.0.8
Testless build
REACTOR › SITE2 › #24 2 months ago
Polish shadow configuration to overwrite projectreactor-home.jar
Testless build
REACTOR › SITE2 › #23 2 months ago
Delete legacy src/main/static/, doesn't seem to be used (#60)
This PR deletes `/src/main/static`, which doesn't seem to be used.
The images and content of the legacy documentation have previously
moved to `/src/resources/static/legacy`.
Polish footer links and listVersion title (#59)
This commit reorganizes the categories of links in the footer.
It displays "list of all core/netty versions" links which were
previously undiscoverable when navigating.
Bump all dependencies to latest releases and clean up some code (#65)
 - mainly, bump Reactor (netty + core) to latest Europium release (with BOM) from
 Californium (sic)
 - bump all other dependencies to their latest versions (Spring-Core, Jackson,
   Thymeleaf, AssertJ, etc...)
 - clean up code a bit (unused imports, unnecessary throws in tests,
   commented tests, use of sysout instead of logger...)
 - Bump Gradle to 6.9, using Shadow plugin's last compatible version 6.1.0
   and newer dependency syntax
 - Add jsr305 dependency to avoid compilation warning
Testless build
REACTOR › SITE2 › #22 2 months ago
Add /maintenance page driven by maintenanceXxx env vars (#66)
The environment variables change the message to indicate there is an
expected maintenance window:
 - `maintenanceDate` is the YYYY/MM/DD date of the scheduled maintenance
 - `maintenanceEnd` is the expected end time of said maintenance

Both are Strings interpolated in the message, so there's no format
enforced.

The page is kept minimal (no external css or scripts) as it is
intended to be cached for the CDN to serve in case of errors, and
the CDN puts a size limit of such a page.
Testless build
REACTOR › SITE2 › #20 2 months ago
Released Dysprosium-SR20 and 2020.0.7
Testless build
REACTOR › SITE2 › #18 3 months ago
Released 2020.0.6
Testless build
REACTOR › SITE2 › #17 3 months ago
Release Dysprosium-SR19
Testless build
REACTOR › REACTORBOM › #280 3 months 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 3 months 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
Build Completed Code commits Tests
REACTOR › SITE2 › #26 2 weeks ago
[polish] Apply spotless in CI only for pull_request events
[chores] Copyright switch from Pivotal to VMware, polish headers (#68)
This commit changes the copyright header from Pivotal to VMware.

It ensures that all occurrences of "Pivotal" are turned into their
VMware equivalent (notably links to eg. security policy).

It also polishes the copyright notice headers using the newly introduced
Spotless plugin as well as some manual editing:

 - format the header (blank line, url)
 - recompute the start year of the copyright notice range from git
 history for java files
 - align end year of said ranges to 2021
 - ensure headers for misc files (html, js, css) is also updated and
 formatted

 See reactor/reactor#682.
Released 2020.0.9
[build] Add Spotless plugin to enforce license headers (#68)
This commit introduces Spotless plugin and configures it to allow
checking and enforcing copyright notice headers via a template, for
java files only.

The license check is added to the ci workflow, ensuring only files
touched by a PR will get checked (in order to allow incremental updates
to the end of the year range).

The build can be parameterized to deactivate the ratchet feature ("only
changed files" vs "all files") or choose a difference base branch for
comparison.

See reactor/reactor#701.
Testless build
REACTOR › SITE2 › #23 2 months ago
Delete legacy src/main/static/, doesn't seem to be used (#60)
This PR deletes `/src/main/static`, which doesn't seem to be used.
The images and content of the legacy documentation have previously
moved to `/src/resources/static/legacy`.
Polish footer links and listVersion title (#59)
This commit reorganizes the categories of links in the footer.
It displays "list of all core/netty versions" links which were
previously undiscoverable when navigating.
Bump all dependencies to latest releases and clean up some code (#65)
 - mainly, bump Reactor (netty + core) to latest Europium release (with BOM) from
 Californium (sic)
 - bump all other dependencies to their latest versions (Spring-Core, Jackson,
   Thymeleaf, AssertJ, etc...)
 - clean up code a bit (unused imports, unnecessary throws in tests,
   commented tests, use of sysout instead of logger...)
 - Bump Gradle to 6.9, using Shadow plugin's last compatible version 6.1.0
   and newer dependency syntax
 - Add jsr305 dependency to avoid compilation warning
Testless build
REACTOR › REACTORBOM › #280 3 months 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 3 months 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 3 months 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 4 months 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 4 months 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 4 months 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 4 months ago
Prepare release 1.5.2
1 of 105 failed
REACTOR › RPOOL › #153 4 months ago
Prepare release 0.2.3
Testless build
Build Completed Code commits Tests
REACTOR › SITE2 › #24 2 months ago
Polish shadow configuration to overwrite projectreactor-home.jar
Testless build
REACTOR › NETTYWIN › #1383 4 months ago
Prepare release 1.0.5
900 passed
REACTOR › REACTORRMQ › #467 4 months ago
Fix Prepare release: remove jcenter() from build
105 passed
REACTOR › RPOOL › #154 4 months ago
Fix Prepare release 0.2.3 - remove jcenter()
359 passed
REACTOR › RNEXT › #3047 4 months ago
Merge-ignore release 3.3.15.RELEASE into master
Prepare release 3.3.15.RELEASE
7768 passed
REACTOR › RNEXT › #3027 5 months 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 5 months ago
Merge #2581 into 3.4.3
 - also fixed Mono.timed
 - also fixed Mono.metrics
7714 passed
REACTOR › RNEXT › #3011 6 months ago
Polish #2574 on master (fix additional http in svgs)
7705 passed
REACTOR › RNEXT › #3002 6 months ago
Prepare release 3.4.2
7701 passed
REACTOR › RNEXT › #2989 7 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