EmbedOps Projects

What exactly is an EmbedOps project, and how does it relate to your repository? Let's clear up some important concepts before moving forward. Within the realm of EmbedOps, there are three layers of hierarchy:

Each of these things (orgs, projects, repos) exist on the EmbedOps servers and are visible after logging into the web app. The org refers to an organization, most likely your business name. A project is a logical grouping of repositories. The orgs and projects are created and exist on the EmbedOps servers.

The repositories that exist on EmbedOps are not the same as your code repository; instead, they are EmbedOps repositories that contain memory metrics, HIL tests, and more. Your code, pipelines, and everything else are hosted on a provider of your choosing (GitHub, GitLab, Bitbucket, etc) and EmbedOps provides layers of functionality on top of your existing repositories via the EmbedOps CLI and the web app.

So then, how does a given code repository know that it is connected to an EmbedOps repository? The answer depends on how you're using EmbedOps. In both cases, the solution is already there for you since Dojo Five performs the onboarding process. These descriptions are for informational purposes only.

Web App and CI

When EmbedOps is executed from the web, for instance from a CI pipeline, it knows which EmbedOps repository it is associated with by reading a special repo variable EMBEDOPS_API_REPO_KEY. This variable exists within your repository and is created by EmbedOps. This API key associates a certain repository with a repository on the EmbedOps servers.

EmbedOps CLI

Your repository has a folder at the root called .embedops. Inside this folder there is a file repo_id.yml. This file contains the repo ID, which is a property that every repository has on the EmbedOps servers. This ID is used to associate the repository you have checked out on your computer with repository information that exists within EmbedOps. Without this file, the CLI does not know which EmbedOps repository your local repo is associated with.