diff --git a/doc/src/nextlevel-ci/ciWithinBitbucket.rst b/doc/src/nextlevel-ci/ciWithinBitbucket.rst
new file mode 100644
index 0000000..1f105df
--- /dev/null
+++ b/doc/src/nextlevel-ci/ciWithinBitbucket.rst
@@ -0,0 +1,39 @@
+.. _ciInBitbucket:
+
+******************************
+CI Pipelines withing Bitbucket
+******************************
+Introduction
+############
+As mentioned in :ref:`ciUseCases` it makes more sense to develop user-space application test driven and use these unit
+tests as indicator for merge/pull requests. NetModule used the CI capabilities for a library and small user-space
+applications already within GitLab and Bitbucket provides a similar feature. Thus, this chapter shows the work of using
+the Bitbucket CI feature for a specific project.
+
+
+Getting Started
+###############
+So far I understood we would need to link Bitbucket and Jenkins. Therefore Jenkins needs an additional plugin:
+
+*  atlassian-bitbucket-server-integration
+
+    -  `web docu <https://plugins.jenkins.io/atlassian-bitbucket-server-integration/>`_
+
+.. note::
+    From the Jenkins plugin documentation I have found this:
+
+    Bitbucket Server 6.0 to 7.3 are also supported, but they're not recommended. This is because some plugin features
+    are not available when using these versions. Instead, we recommend using Bitbucket Server 7.4+. With 7.0+ you can
+    make use of pull request triggers for jobs. With 7.4+ you can set up an Application Link to have access to all
+    plugin features.
+
+
+We would need to configure the plugin on Jenkins:
+
+*  Adding the Bitbucket instance details including a HTTP access token
+
+
+At the current moment I am not sure about how to proceed. I have no admin permissions on the Jenkins instance I am using
+on the HAC infrastructure and on Bitbucket I cannot see the pipeline setting maybe as well due to a lack of permissions.
+
+Thus, I postpone this topic until I get some news :-)