Skip to content

[jenkins] Improve api/generator diff reporting to say if there were changes, and if they were breaking or not. - #4138

Merged
rolfbjarne merged 11 commits into
dotnet:masterfrom
rolfbjarne:jenkins-descriptive-diffs
May 30, 2018
Merged

[jenkins] Improve api/generator diff reporting to say if there were changes, and if they were breaking or not.#4138
rolfbjarne merged 11 commits into
dotnet:masterfrom
rolfbjarne:jenkins-descriptive-diffs

Conversation

@rolfbjarne

@rolfbjarne rolfbjarne commented May 28, 2018

Copy link
Copy Markdown
Member

For the api diff for this PR we now show:

  • 🔥 breaking changes 🔥: If there are any breaking changes in the api diff (for this PR).
  • please review changes: If there are any non-breaking changes in the api diff.
  • no change: If the api diff is empty.

For the generator diff we show:

  • only version changes: If there were only changes related to version numbers (since the XI/XM version number is added to the generator, that version number will always show up as a diff when comparing the generated source code)
  • please review changes: If anything other that version numbers changed in the generated source code.

@rolfbjarne rolfbjarne added skip-all-tests Skip all the tests do-not-merge Do not merge this pull request labels May 28, 2018
@rolfbjarne

Copy link
Copy Markdown
Member Author

do-not-merge since I'll have to push a few test commits to actually test this properly.

@monojenkins

Copy link
Copy Markdown
Contributor

Build success
Build comment file:

Provisioning succeeded
Build succeeded
API Diff (from stable)
API Diff (from PR only) (🔥 breaking changes 🔥)
Generator Diff (please review changes)
Test run succeeded


grep isn't capable enough to remove multiple script block in a file (at least
mac-api-diff.html contains multiple other files, each with its own script
block), so step up a bit and use perl instead.
@monojenkins

Copy link
Copy Markdown
Contributor

Build success
Build comment file:

Provisioning succeeded
Build succeeded
API Diff (from stable)
API Diff (from PR only) (please review changes)
Generator Diff (only version changes)
Test run succeeded


@dotnet dotnet deleted a comment from monojenkins May 30, 2018
@dotnet dotnet deleted a comment from monojenkins May 30, 2018
@dotnet dotnet deleted a comment from monojenkins May 30, 2018
@dotnet dotnet deleted a comment from monojenkins May 30, 2018
@rolfbjarne

Copy link
Copy Markdown
Member Author

@spouliot this is ready for review now.

The two monojenkins comments above show how it shows up with breaking API changes and generator changes (first comment), and non-breaking API changes (second comment)

@monojenkins

Copy link
Copy Markdown
Contributor

Build success
Build comment file:

Provisioning succeeded
Build succeeded
API Diff (from stable)
API Diff (from PR only) (no change)
Generator Diff (only version changes)
Test run succeeded


@VincentDondain VincentDondain left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool

@rolfbjarne
rolfbjarne merged commit e24a6f6 into dotnet:master May 30, 2018
@rolfbjarne rolfbjarne removed the do-not-merge Do not merge this pull request label May 30, 2018
rolfbjarne added a commit to rolfbjarne/macios that referenced this pull request Jun 12, 2018
…hanges, and if they were breaking or not. (dotnet#4138)

For the api diff for this PR we now show:

* `🔥 breaking changes 🔥`: If there are any breaking changes in the api diff (for this PR).
* `please review changes`: If there are any non-breaking changes in the api diff.
* `no change`: If the api diff is empty.

For the generator diff we show:

* `only version changes`: If there were only changes related to version numbers (since the XI/XM version number is added to the generator, that version number will always show up as a diff when comparing the generated source code)
* `please review changes`: If anything other that version numbers changed in the generated source code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-all-tests Skip all the tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants