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

Update pipeline-initialization.md #1406

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update pipeline-initialization.md #1406

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
16 changes: 8 additions & 8 deletions docs/reference/pipeline-initialization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,24 +8,24 @@ For pipelines that need a full clone of the Git repository for evaluation
job that clones the Git repository and evaluates the pipeline files.
Pipelines that use dedicated initialization jobs for evaluation have
an "Initialization" step displayed on the Workflow Page.
Initialization jobs have a duration limit set to 10 minutes.
Initialization jobs have a duration limit (set to 10 minutes).

As a default, initialization jobs use machine and OS image assigned by internal strategy. However, you can customize agent specification for initialization jobs across your organization. If you need to configure it at a project level, you might be interested in [project-level Pre-flight checks](/security/configuring-pre-flight-checks#project-pre-flight-checks).
As a default, initialization jobs use the machine and OS image assigned by the relevant internal strategy. However, you can customize agent specifications for initialization jobs across your organization. If you need to configure it at the project level, you might be interested in [project-level Pre-flight checks](/security/configuring-pre-flight-checks#project-pre-flight-checks).


## Configuring agents for intialization job
## Configuring agents for intialization jobs

1. Open the **Settings** from the **Organization menu** in the right side of the page header.
1. Open the **Settings** tab in the **Organization menu** on the right side of the page header.

2. Click **Initialization jobs** on the left side of the settings view and go to **Agent configuration** section.
2. Click **Initialization jobs** on the left side of the settings panel and go to the **Agent configuration** section.

3. Choose between different machine types:
3. Choose the preferred machine type:
- **Linux Based Virtual Machines** - hosted by Semaphore
- **Mac Based Virtual Machines** - hosted by Semaphore
- **Self-Hosted Machines** - hosted by the customer (if applicable)

For machines hosted by Semaphore, choose a proper **Machine type** and **OS image** of the agent. For self-hosted machines choose a **Machine type** that matches your self-hosted agent type.
For machines hosted by Semaphore, choose a proper **Machine type** and **OS image** for the agent. For self-hosted machines choose a **Machine type** that matches your self-hosted agent type.

4. Click **Save changes** button.
4. Click the **Save changes** button.

[change-in]: https://docs.semaphoreci.com/reference/conditions-reference/#change_in