Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update readme with consumers guide and features #18

Merged
merged 8 commits into from
Aug 26, 2020
Merged

Conversation

XiongKezhi
Copy link
Contributor

@XiongKezhi XiongKezhi commented Aug 25, 2020

  • Update readme

@XiongKezhi XiongKezhi requested a review from a team August 25, 2020 16:58
Copy link
Member

@timja timja left a comment

Choose a reason for hiding this comment

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

no blockers but a number of suggested improvements.

README.md Outdated

Inspired by the [GitHub Checks API](https://docs.github.com/en/rest/reference/checks#runs), this plugin aims to provide a general API to allow Jenkins plugins publishing checks (or reports) to remote source code management (SCM) platforms (e.g. GitHub, GitLab, BitBucket, etc.).
By consuming this API, other plugins can publish check with customized parameters for a Jenkins build, such as status, summary, warnings, code annotations, or even images.
Copy link
Member

Choose a reason for hiding this comment

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

Let's add some line breaks to break up the paragraphs this is a new topic.

Suggested change
By consuming this API, other plugins can publish check with customized parameters for a Jenkins build, such as status, summary, warnings, code annotations, or even images.
By consuming this API, other plugins can publish check with customized parameters for a Jenkins build, such as status, summary, warnings, code annotations, or even images.

README.md Outdated

Inspired by the [GitHub Checks API](https://docs.github.com/en/rest/reference/checks#runs), this plugin aims to provide a general API to allow Jenkins plugins publishing checks (or reports) to remote source code management (SCM) platforms (e.g. GitHub, GitLab, BitBucket, etc.).
By consuming this API, other plugins can publish check with customized parameters for a Jenkins build, such as status, summary, warnings, code annotations, or even images.
Then, the implementations of this API will decide on how to make use of these parameters and where to publish the checks.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Then, the implementations of this API will decide on how to make use of these parameters and where to publish the checks.
Implementations of this API decide on how to make use of these parameters and where to publish the checks.

README.md Outdated

This a [Google Summer of Code](https://summerofcode.withgoogle.com/) project for [Jenkins Organization](https://www.jenkins.io/), it is still under development.
Current consumers of this plugin include [Warnings Next Generation Plugin](https://github.com/jenkinsci/warnings-ng-plugin) and [Code Coverage API Plugin](https://github.com/jenkinsci/code-coverage-api-plugin); current implementations include [GitHub Checks Plugin](https://github.com/jenkinsci/github-checks-plugin).
Copy link
Member

Choose a reason for hiding this comment

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

I think this looks better, might be nice to add integration pull requests so others can see how to add their own one

Suggested change
Current consumers of this plugin include [Warnings Next Generation Plugin](https://github.com/jenkinsci/warnings-ng-plugin) and [Code Coverage API Plugin](https://github.com/jenkinsci/code-coverage-api-plugin); current implementations include [GitHub Checks Plugin](https://github.com/jenkinsci/github-checks-plugin).
Known consumers:
* [Warnings Next Generation Plugin](https://plugins.jenkins.io/warnings-ng)
* [Code Coverage API Plugin](https://plugins.jenkins.io/code-coverage-api)
Implementations:
* [GitHub Checks Plugin](https://plugins.jenkins.io/github-checks)

README.md Outdated
* [Project Idea](https://www.jenkins.io/projects/gsoc/2020/project-ideas/github-checks/)
* [Project Design](https://docs.google.com/document/d/1hVQTd9jKw0sx8JQR8KjbM-7lWW84e2vFjmmkzBpBbSk/edit?usp=sharing)
* [Meeting Notes](https://docs.google.com/document/d/1TZLmu3nBPbwUjzLVYGnV_YtYvmzxzw6A4eEVYpbmi3Y/edit?usp=sharing)
## Consumers Guide
Copy link
Member

Choose a reason for hiding this comment

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

I think the guide belongs in its own file in the docs directory.

I would consider moving pipeline above this, as users will want this.

README.md Outdated
.build();
```

Then you can create a publisher based on a Jenkins `run` to publish the check you just constructed:
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Then you can create a publisher based on a Jenkins `run` to publish the check you just constructed:
Then you can create a publisher based on a Jenkins `Run` to publish the check you just constructed:

README.md Outdated
- `ChecksDetails`: the top-level model of a check, including all other models and some basic parameters like status and conclusion;
- `ChecksOutput`: the output of a check, providing some displayed details like title, summary, URL, and code annotations;
- `ChecksAnnotation`: a code annotation of a check, providing a specific comment for one or multiple lines of code;
- `ChecksImage`: an image of a check, providing an intuitive graph for the build like issues trend, coverage chart;
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
- `ChecksImage`: an image of a check, providing an intuitive graph for the build like issues trend, coverage chart;
- `ChecksImage`: an image of a check, providing an intuitive graph for the build like issues trend, coverage chart, must be a public URL that GitHub can fetch from

README.md Outdated
Consumers can set these parameters through the checks models:

- `ChecksDetails`: the top-level model of a check, including all other models and some basic parameters like status and conclusion;
- `ChecksOutput`: the output of a check, providing some displayed details like title, summary, URL, and code annotations;
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
- `ChecksOutput`: the output of a check, providing some displayed details like title, summary, URL, and code annotations;
- `ChecksOutput`: the output of a check, providing some displayed details like title, summary, URL, and code annotations

README.md Outdated
The checks are highly customized by consumers due to a number of optional parameters provided.
Consumers can set these parameters through the checks models:

- `ChecksDetails`: the top-level model of a check, including all other models and some basic parameters like status and conclusion;
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
- `ChecksDetails`: the top-level model of a check, including all other models and some basic parameters like status and conclusion;
- `ChecksDetails`: the top-level model of a check, including all other models and some basic parameters like status and conclusion

README.md Outdated
- `ChecksOutput`: the output of a check, providing some displayed details like title, summary, URL, and code annotations;
- `ChecksAnnotation`: a code annotation of a check, providing a specific comment for one or multiple lines of code;
- `ChecksImage`: an image of a check, providing an intuitive graph for the build like issues trend, coverage chart;
- `ChecksAction`: an action of a check, providing further actions to be performed by users, like rerun a Jenkins build;
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
- `ChecksAction`: an action of a check, providing further actions to be performed by users, like rerun a Jenkins build;
- `ChecksAction`: an action of a check, providing further actions to be performed by users, like rerun a Jenkins build

README.md Show resolved Hide resolved
@codecov
Copy link

codecov bot commented Aug 26, 2020

Codecov Report

Merging #18 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master      #18   +/-   ##
=========================================
  Coverage     90.87%   90.87%           
  Complexity       69       69           
=========================================
  Files            11       11           
  Lines           274      274           
  Branches          6        6           
=========================================
  Hits            249      249           
  Misses           23       23           
  Partials          2        2           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f0da812...762ef55. Read the comment docs.

README.md Outdated
Implementations:
* [GitHub Checks Plugin](https://plugins.jenkins.io/github-checks)

This plugin, alone with it's [GitHub implementation](https://plugins.jenkins.io/github-checks), has been installed on [ci.jenkins.io](https://ci.jenkins.io/Plugins) to help maintain hundreds of Jenkins plugins. You can take a look at the [action](https://github.com/jenkinsci/checks-api-plugin/runs/1025532156) for this repository or other plugin repositories under [Jenkins organization](https://github.com/jenkinsci) for the results.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
This plugin, alone with it's [GitHub implementation](https://plugins.jenkins.io/github-checks), has been installed on [ci.jenkins.io](https://ci.jenkins.io/Plugins) to help maintain hundreds of Jenkins plugins. You can take a look at the [action](https://github.com/jenkinsci/checks-api-plugin/runs/1025532156) for this repository or other plugin repositories under [Jenkins organization](https://github.com/jenkinsci) for the results.
This plugin, along with it's [GitHub implementation](https://plugins.jenkins.io/github-checks), has been installed on [ci.jenkins.io](https://ci.jenkins.io/Plugins) to help maintain over 1500 Jenkins plugins. You can take a look at the [action](https://github.com/jenkinsci/checks-api-plugin/runs/1025532156) for this repository or other plugin repositories under [Jenkins organization](https://github.com/jenkinsci) for the results.

README.md Outdated
## Guides

- [Consumers Guide](docs/consumers-guide.md)
- [Implementation Guide](docs/implementation-guide.md)
Copy link
Member

Choose a reason for hiding this comment

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

doesn't appear to exist?

it should be added in the PR that adds it if I'm not misunderstanding

Suggested change
- [Implementation Guide](docs/implementation-guide.md)

README.md Outdated

## Acknowledgements

This plugin is started as a [Google Summer of Code 2020 project](https://summerofcode.withgoogle.com/projects/#5139745388101632), you can find more about it on [Jenkins GSoC SIG](https://www.jenkins.io/sigs/gsoc/).
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
This plugin is started as a [Google Summer of Code 2020 project](https://summerofcode.withgoogle.com/projects/#5139745388101632), you can find more about it on [Jenkins GSoC SIG](https://www.jenkins.io/sigs/gsoc/).
This plugin was started as a [Google Summer of Code 2020 project](https://summerofcode.withgoogle.com/projects/#5139745388101632), you can find more about it on [Jenkins GSoC SIG](https://www.jenkins.io/sigs/gsoc/).

README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@XiongKezhi XiongKezhi merged commit d0557d1 into master Aug 26, 2020
@XiongKezhi XiongKezhi deleted the document branch August 26, 2020 08:41
XiongKezhi added a commit that referenced this pull request Oct 25, 2020
…gins-checks-api-0.2.0

Bump checks-api from 0.1.1-rc24.26e46eb1548a to 0.2.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants