Skip to content

Latest commit

 

History

History
33 lines (22 loc) · 1.96 KB

MAINTAINERS.md

File metadata and controls

33 lines (22 loc) · 1.96 KB

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):

$ ./examples/start_docker.sh 2.249.2

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 for a different approach.

$ 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

To resolve some binary compatibility issues JENKINS-48357, the sources from the artifact com.atlassian.httpclient:atlassian-httpclient-plugin:0.23 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 sources are Apache License (see pom in src/main/resources/atlassian-httpclient-plugin-0.23.0.pom)

Releasing the plugin

  • we use the Release Drafter extension to perform releases, make sure that the PRs are properly labelled
  • there is a Jira Cloud 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