Content Comparison

Depending on your role, there are different approaches on how to contribute to Kieker.

Drawiozoom1Image Added

Original draw.io (only available when draw.io subscription active):

Drawio

Kieker deployment workflowcontentVer

simple	0
zoom	1
inComment	0
custContentId
pageId	25952261
diagramDisplayNamecustContentId	Kieker deployment workflow
lbox	1	diagramDisplayName
contentVer
hiResPreview	0
revision	2
baseUrl	https://kieker-monitoring.atlassian.net/wiki
diagramName	Kieker deployment workflow
pCenter	0
aspect
width	1986
links	auto
tbstyle	top
height	309

Contributing not being a member of the Kieker development team

...

Create a new ticket in the Kieker JIRA https://kieker-monitoring.atlassian.net/secure/Dashboard.jspa
Create a corresponding branch in the Kieker repository named like the following: KIEKER-<ticketID> (if the ticket ID would be 1234, the branch should be named "KIEKER-1234")
1. Example:
```
git checkout -b KIEKER-1234
```
Develop on the created branch. If you push your branch, the Snap-CI pipeline is automatically triggered and gives feedback whether it passed all checks.
1. ```
git push origin KIEKER-1234
```
When you completed your work, you can create a pull request from your branch to the Kieker master branch.
(a guide on the general steps you have to take can be found here: https://help.github.com/articles/using-pull-requests/ )
The code will be checked by our Jenkins pipeline and a Kieker developer will be notified to review the pull request.
If both finished successfully, the merge is initiated by a Kieker developer.
Finally the new state of the master branch will run through the Jenkins pipeline and eventually (if the pipeline succeeded) pushed to the stable branch.