Skip to content

Add bitbucket example for secrets #893

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

Merged
kprosise merged 1 commit into from
Mar 3, 2026
Merged

Add bitbucket example for secrets #893

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
48 changes: 39 additions & 9 deletions source/user-guide/lmp-customization/linux-extending.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -180,7 +180,7 @@ For example, the OP-Tee package is only included in an image if the target machi

.. _ref-ug-private-repo:

Including Private Git+ssh Repositories
Including Private Git+SSH Repositories
--------------------------------------

Custom recipes may need access to private Git repositories only available via SSH.
Expand All @@ -193,17 +193,47 @@ Secrets matching the pattern ``ssh-*.key`` are loaded into an ssh-agent, and ``s

To generate ``ssh-known_hosts``:

.. code-block:: console
.. tab-set::

$ ssh-keyscan github.com > /tmp/ssh-known_hosts
.. tab-item:: GitHub

An example for accessing a private GitHub repo:
.. code-block:: console

.. code-block:: console
$ ssh-keyscan github.com > /tmp/ssh-known_hosts

.. tab-item:: Bitbucket

.. code-block:: console

$ ssh-keyscan bitbucket.org > /tmp/ssh-known_hosts

Examples for accessing a private repo:

.. tab-set::

.. tab-item:: GitHub

.. code-block:: console

$ fioctl secrets update ssh-github.key==/tmp/ssh-github.key
$ fioctl secrets update ssh-known_hosts==/tmp/ssh-known_hosts

At this point new CI jobs will be able to access recipes that have ``SRC_URI`` items like:

.. code-block::

SRC_URI = "git://git@github.com/<repo>;protocol=ssh;branch=main"

.. tab-item:: Bitbucket

.. code-block:: console

$ fioctl secrets update ssh-bitbucket.key==/tmp/ssh-bitbucket.key
$ fioctl secrets update ssh-known_hosts==/tmp/ssh-known_hosts

At this point new CI jobs will be able to access recipes that have ``SRC_URI`` items like:

$ fioctl secrets update ssh-github.key==/tmp/ssh-github.key
$ fioctl secrets update ssh-known_hosts==/tmp/ssh-known_hosts
.. code-block::

At this point new CI jobs will be able to access recipes that have ``SRC_URI`` items like::
SRC_URI = "git://git@bitbucket.org/<repo>;protocol=ssh;branch=main"

SRC_URI = "git://git@github.com/<repo>;protocol=ssh;branch=main"