- 
                Notifications
    
You must be signed in to change notification settings  - Fork 101
 
How to create a release
- 
Build of the branch from which release is planned shall be clean and all tests shall be passed OK (because release itself skips tests)
 - 
Job for staging release is: https://jenkins.eclipse.org/yasson/job/yasson-release-oss
 
it has parameters: RELEASE_VERSION, NEXT_VERSION, BRANCH, OVERWRITE and DRY_RUN
to run staging job correctly it's enough to fill BRANCH parameter with required github branch (default master) and run the job. DRY_RUN shall not be checked, OVERWRITE may by checked if the expected version already was staged. Or just for precaution. RELEASE_ and NEXT_ version may be filled but if pom.xml in source branch is correct all versions will be taken/generated from pom.xml After job is done released artifact gets visible in sonatype staging at https://oss.sonatype.org/content/groups/staging/org/eclipse/yasson/
Since it is visible it is possibly to work with published artifact (like build dependent projects, check by TCK ect)
- After it is proved that staged artifact is correct it is possible to release it to central.
Release is been done using several helper jobs:
- https://jenkins.eclipse.org/yasson/job/list-staging/ which will give you list of available repositories related to yasson. Like orgeclipseyasson-1009. Repository has description so it is visible by description which version is inside. And it shall be in CLOSED state.
 - After required repository id is identified it is possible to run https://jenkins.eclipse.org/yasson/job/oss-release which shall be configured before run and appropriate repository id shall be set in order to perform proper release to central.