-
-
Notifications
You must be signed in to change notification settings - Fork 280
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
121 additions
and
218 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,33 +1,36 @@ | ||
#### Developing in Docker | ||
# Notes for maintainers | ||
|
||
*Start dockerized Jenkins (for testing)* | ||
## Developing in Docker | ||
|
||
### Start dockerized Jenkins (for testing) | ||
|
||
The command below will start a local Jenkins using the version specificied as first argument (or lts): | ||
|
||
```bash | ||
$ ./examples/start_docker.sh 2.249.2 | ||
./examples/start_docker.sh 2.249.2 | ||
``` | ||
|
||
*Build the plugin in Docker environment* | ||
### Build the plugin in Docker environment | ||
|
||
The command below allows to build the plugin using maven docker image. This is useful to test building against different Maven/JDK versions. | ||
See also [SDKMan](https://sdkman.io/) for a different approach. | ||
|
||
```bash | ||
$ docker run -it --rm -v "$PWD":/usr/src/mymaven -v "$HOME/.m2:/root/.m2" -w /usr/src/mymaven maven:3.3-jdk-8 mvn clean package | ||
docker run -it --rm -v "$PWD":/usr/src/mymaven -v "$HOME/.m2:/root/.m2" -w /usr/src/mymaven maven:3.3-jdk-8 mvn clean package | ||
``` | ||
|
||
*Atlassian sources import* | ||
### Atlassian sources import | ||
|
||
To resolve some binary compatibility issues [JENKINS-48357](https://issues.jenkins-ci.org/browse/JENKINS-48357), | ||
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/) | ||
has been imported in the project to have control over http(s) protocol transport layer. | ||
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) | ||
sources are Apache License (see pom in src/main/resources/atlassian-httpclient-plugin-0.23.0.pom) | ||
|
||
### Testing | ||
|
||
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. | ||
|
||
#### Releasing the plugin | ||
### Releasing the plugin | ||
|
||
- we use the [Release Drafter](https://github.com/toolmantim/release-drafter) extension to perform releases, make sure that the PRs are [properly labelled](https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml) | ||
- 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 | ||
- make sure you have `~/.m2/settings.xml` configured - refer to [releasing Jenkins plugins](https://www.jenkins.io/doc/developer/publishing/releasing/) | ||
Make sure you have your `~/.m2/settings.xml` configured accordingly - refer to [releasing Jenkins plugins](https://www.jenkins.io/doc/developer/publishing/releasing/). |
Oops, something went wrong.