How it works Docs Prices
Login Sign up
Browse documentation

Getting started

Before you begin

You need a Codinamo account and a source repository that the execution worker can clone. If the repository requires authentication, configure the credentials in a secret group rather than writing values in action parameters or ICE.

Select an owner and workspace

  1. Sign in to Codinamo.

  2. Open the context switcher beside the Codinamo name.

  3. Select your personal organization or create a shared organization.

  4. Select an existing workspace or create one inside the chosen organization.

The closed switcher displays Organization > Workspace. The organization owns the public namespace used by Git repositories and Registry images; the workspace isolates operational resources such as projects, pipelines, variables, secrets, agents, and deployment targets.

See Organizations and namespaces when setting up shared ownership.

Create a project

  1. Enter the workspace context.

  2. Open Projects and select Create Project.

  3. Enter a project name.

  4. Enable the Git repository toggle only if Codinamo should host the project’s source.

Project names are unique within the organization namespace because they also participate in repository and Registry paths.

Create a pipeline

  1. Open Pipelines and select New Pipeline.

  2. Select the project and enter a pipeline name.

  3. Open the pipeline editor.

  4. Add a source action, a build action, and any required packaging action.

  5. Connect the actions in execution order.

  6. Attach a variable group for non-sensitive configuration and a secret group for credentials when required.

  7. Save the pipeline.

For a complete example, continue with Build a Java project.

Read an execution

A run page separates four kinds of information:

Status

Overall run and action state, identified by a stable RUN-…​ ID.

Progress

User-facing steps and their current state.

Logs

Ordered output emitted by actions and the runtime.

Test reports

Aggregated JUnit results produced by TEST_REPORT.

Action outputs are also written to the execution log so references can be diagnosed without inspecting internal storage. Exact occurrences of attached secret values are replaced before logs are persisted.

See Secrets when the pipeline needs credentials.

Share access

Organization owners can open Teams to group existing accounts and Access to assign roles. Grant at workspace scope when the same responsibility should cover multiple projects, or use a narrower project or pipeline scope for focused access.

See Teams and membership and Manage access.