SMB Deployment

Transfer build artifacts to SMB network shares as a native pipeline step. Credentials stored in Opsera's encrypted vault — never exposed in logs or config files.

Prerequisites

• SMB server accessible from Opsera's pipeline execution environment

• SMB server credentials (server IP, share name, username, password) available

• An upstream build step in the pipeline that produces the artifact to transfer

Pipeline setup

1

Register SMB Server in Tool Registry

Add server IP, share name, username, and password. All credentials are encrypted in Opsera's vault on save.

2

Add SMB Deployment step

Click +. Step Setup: Tool = SMB Server, Step Type = Publish. Set Dependencies to the upstream build step. Add optional tags for log filtering.

3

Configure step settings

Select the SMB Tool registered in Step 1. Choose the Build Step that produced the artifact. Save.

4

Run and verify

Trigger the pipeline. Check console logs for transfer confirmation messages. Navigate to the SMB share to verify files are present in the destination directory.

Points to remember

• Register the SMB tool once in Tool Registry — it can then be reused across any number of pipelines in your Opsera workspace without reconfiguration.

• If the SMB server is unreachable, the pipeline fails immediately with a connectivity error — check network access and firewall rules between Opsera's execution environment and the SMB host.

• Use file path patterns in the Source Path field to deploy specific artifact types rather than the entire build output directory.

• Add multiple SMB deployment steps in one pipeline to deploy to different network shares simultaneously — each step uses its own registered SMB tool.