You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,7 @@ General rules:
4
4
5
5
- check the [general Jenkins development guide](https://www.jenkins.io/doc/developer/book/)
6
6
- make sure to provide tests
7
+
- when adding new fields, make sure to [include backward-compatibility](https://www.jenkins.io/doc/developer/persistence/backward-compatibility/) and tests for that
7
8
- mark the Pull Request as _draft_ initially, to make sure all the checks pass correctly, then convert it to non-draft.
Use [docker-compose](./docker-compose.yml) to run a local Jenkins instance with the plugin installed. The configuration includes local volumes for both: Jenkins and ssh-agent, so you can easily test the plugin in a clean environment.
24
25
25
-
```bash
26
26
27
27
### Atlassian sources import
28
28
29
-
To resolve some binary compatibility issues [JENKINS-48357](https://issues.jenkins-ci.org/browse/JENKINS-48357),
29
+
To resolve [some binary compatibility issues](https://github.com/jenkinsci/jira-plugin/pull/140),
30
30
the sources from the artifact [com.atlassian.httpclient:atlassian-httpclient-plugin:0.23](https://packages.atlassian.com/maven-external/com/atlassian/httpclient/atlassian-httpclient-plugin/0.23.0/)
31
31
has been imported in the project to have control over http(s) protocol transport layer.
32
32
The downloaded sources didn't have any license headers but based on the [pom](https://packages.atlassian.com/maven-external/com/atlassian/httpclient/atlassian-httpclient-plugin/0.23.0/atlassian-httpclient-plugin-0.23.0.pom)
33
-
sources are Apache License (see pom in src/main/resources/atlassian-httpclient-plugin-0.23.0.pom)
33
+
sources are Apache License (see pom in src/main/resources/atlassian-httpclient-plugin-0.23.0.pom)
34
34
35
35
### Testing
36
36
37
37
There is a [Jira Cloud](https://jenkins-jira-plugin.atlassian.net/) test instance that the changes can be tested against, official maintainers are admins that can grant access for testing to PR submitters on a need-to-have basis.
38
38
39
39
### Releasing the plugin
40
40
41
-
Make sure you have your `~/.m2/settings.xml` configured accordingly - refer to [releasing Jenkins plugins](https://www.jenkins.io/doc/developer/publishing/releasing/).
41
+
See [releasing Jenkins plugins](https://www.jenkins.io/doc/developer/publishing/releasing-manually/).
@@ -22,10 +24,3 @@ See user documentation at [https://jenkinsci.github.io/jira-plugin/](https://jen
22
24
23
25
This plugin uses [CrowdIn platform](https://jenkins.crowdin.com/jira-plugin) as the frontend to manage translations. If you would like to contribute translation of this plugin in your language, you're most welcome! For details, see [jenkins.io CrowdIn introduction](https://www.jenkins.io/doc/developer/crowdin/translating-plugins/).
24
26
25
-
## Contributing
26
-
27
-
There have been many developers involved in the development of this plugin and there are many downstream users who depend on it. Tests help us assure that we're delivering a reliable plugin and that we've communicated our intent to other developers in a way that they can detect when they run tests.
28
-
29
-
- each change should be covered by appropriate unit tests
30
-
- in case it is not testable via a unit test, it should be tested against a real Jira instance - possibly both Jira Server and Jira Cloud. There is a [Jira Cloud test instance](https://jenkins-jira-plugin.atlassian.net/) that we are using for testing the plugin releases - let us know in the Pull Request in case you need access for testing
0 commit comments