Skip to content

Commit 7ac09c9

Browse files
authored
Merge pull request #236 from jenkinsci/bitwiseman-patch-1
Add CONTRIBUTING.adoc with publishing instructions
2 parents 1fb7c66 + 97ec0d7 commit 7ac09c9

File tree

2 files changed

+11
-1
lines changed

2 files changed

+11
-1
lines changed

CONTRIBUTING.adoc

+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
= Contributing
2+
3+
== Publishing a new release
4+
5+
This plugin uses the standard system for publishing
6+
https://www.jenkins.io/doc/developer/publishing/releasing-cd/#releasing[incremental Jenkins releases].
7+
To trigger the system to publish a new version of this plugin, add a descriptive label such as `developer` or `enhancement`
8+
to your PR before it is merged. When the PR is merged, the system will automatically publish a new version of the plugin.
9+
10+
NOTE: the `dependencies`, `chore`, and `java` labels will not trigger publishing of a new version.

README.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ There's no need to install this plugin manually, although you want to keep it up
1616
== Note to plugin developers
1717

1818
If you are developing a plugin that depends on http://kohsuke.org/github-api[github-api],
19-
it's is highly recommended that you depend on this as opposed to bundle the jar locally.
19+
it's is highly recommended that you depend on this plugin as opposed to bundle the jar locally.
2020
Doing so (as opposed to depending on `+org.kohsuke:github-api+` as a jar),
2121
we can eliminate the classloader problems caused by having multiple copies of github-api loaded.
2222
Specifically, if plugin A and B both locally includes its own copy of the `+github-api.jar+` and another plugin C depends on A and B, it'll break.

0 commit comments

Comments
 (0)