Nemcio/SCM-Manager
1
0
Fork 0
mirror of https://github.com/scm-manager/scm-manager.git synced 2025-10-26 08:06:09 +01:00
Code Issues Packages Projects Releases Activity

Update release process (#1514)

Browse Source 
Updates the SCM-Manager release process after the transition to gradle as build tool.

Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
This commit is contained in:
Eduard Heimbuch
2021-02-02 10:32:57 +01:00
committed by GitHub
parent e283195530
commit 4966a389a3
1 changed files with 11 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/en/release-process.md
View File

@@ -42,7 +42,7 @@ git commit -m "Adjust changelog for release <version>"
Jenkins will
- update `pom.xml` and `package.json`
- update `gradle.properties` and `package.json`
- merge with master branch
- build and deploy everything
- set the new development version for the develop branch
@@ -54,6 +54,10 @@ Jenkins will
To release a new version of a Plugin for SCM-Manager v2 you have to do the following steps (replace placeholder `<version>` accordingly, eg. with `2.1.0`):
## Attention: Migrate plugin to gradle
If an SCM-Manager plugin hasn't been migrated to gradle yet, this is highly recommended before release the next version.
The migration from maven to gradle can easily be done using [this tool](https://github.com/scm-manager/smp-maven-to-gradle).
## Check out default branch
Make sure you have no changes you want to keep!
@@ -74,7 +78,7 @@ git merge origin/support/<support branch>
If you need to update the parent of the plugin to a new release of SCM-Manager, change it now:
- `pom.xml`: `parent.version`
- `build.gradle`: `scmVersion`
- `package.json`: `dependencies.ui-plugins`
## Plugin dependencies
@@ -84,8 +88,8 @@ Check if all plugin dependencies are proper versions and not SNAPSHOT!
## Build, commit and push
```
rm -rf node_modules yarn.lock && mvn clean install \
&& git add yarn.lock pom.xml package.json \
./gradlew build \
&& git add yarn.lock build.gradle package.json \
&& git commit -m "Update to new version of SCM-Manager" \
&& git push origin develop
```
@@ -109,13 +113,14 @@ export VERSION=<version> \
Jenkins will
- update versions in pom.xml and package.json
- update versions in gradle.properties and package.json
- merge with master branch
- build and deploy everything
- set the new development version for the develop branch
- delete the release branch
## Attention: Creating new plugins
If you are creating a new plugin which doesn't exist in the SCM-Manager Plugin-Center yet, your plugin will not be shown after the release. First you have to create a `index.md` in the Plugin-Center Repository.
If you are creating a new plugin which doesn't exist in the SCM-Manager Plugin-Center yet, your plugin will not be shown after the release.
First you have to create a `plugin.yml` in the website repository.
Example: https://github.com/scm-manager/website/blob/master/content/plugins/scm-teamscale-plugin/plugin.yml