Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update BBDC docs to reflect "pipeline definitions" changes #9014

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update BBDC docs to reflect "pipeline definitions" changes #9014

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9d75806
Update BBDC docs to reflect "pipeline definitions" changes
BeFunes Oct 14, 2024
3f3b4af
Merge branch 'master' into DOCSS-1624/bbdc
BeFunes Oct 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions jekyll/_cci2/bitbucket-data-center-integration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,10 +57,13 @@ NOTE: If you are using both CircleCI's Bitbucket Data Center and GitLab Self-Man
.. Select **Pipelines** in the sidebar.
.. Select **Set Up Pipeline**. Fill in the required fields:
** Give your pipeline a descriptive name.
** Select **Bitbucket Data Center** under Config Source.
** Select **Bitbucket Data Center** under Integration.
** Provide the project HTTP access token you created in the previous step. Select btn:[Connect].
** Select your repository and branch.
** In the Config File Path field enter the path to the config file in your repository. Typically this is `.circleci/config.yml` but can be whatever you have configured in your project.
** Define where the config file for this pipeline is stored:
#Rosie, I wanted to do a further level of indentation here but I can't test if it works#
** Select a repository from the dropdown.
** Enter the path to the config file. Typically this is `.circleci/config.yml` but can be any file path with extension `*.yml`.
** Under Build Assets, select a Checkout Source for this pipeline. This is the repository that will be checked out when a link:https://circleci.com/docs/configuration-reference/#checkout[checkout step] is run. If your config is stored in the same repository as your code, pick the same repository you selected under Config Source.
.. Select btn:[Save].

. **Set up a trigger**:
Expand All @@ -70,8 +73,11 @@ NOTE: If you are using both CircleCI's Bitbucket Data Center and GitLab Self-Man
.. Fill in the required fields:
** Give your trigger a descriptive name.
** Provide the project HTTP access token you created above. Select btn:[Connect].
** Select your repository and branch.
** Select the Trigger source repository
** Choose the pipeline you created in the previous step under the dropdown to show CircleCI which pipeline to trigger.
** If prompted, enter a Config branch. This is the name of the branch that should be used to fetch your config file when a pipeline is triggered. This field is only required if your config is stored in a repository that is not the source of your trigger.
** If prompted, enter a Checkout branch. This is the name of the branch that should be used to check out your code when a link:https://circleci.com/docs/configuration-reference/#checkout[checkout step] is run. This field is only required if the *Checkout source* repository you configured in your Pipeline is not the source of your trigger.

.. Select btn:[Save].

. If you have not already done so, **create a `.circleci` directory to the root of your repository, then add a `config.yml` file in that directory**. When you commit this change in your repository, you should see the pipeline trigger for the first time on the CircleCI dashboard.
Expand Down