Skills and Automation
2 min
min

Skills and Automation

Automate further with Skills

Skills are pre-built script templates that combine Solsta CLI commands to handle common studio workflows.

Nightly Build Sync

Queue an update for all environments across all machines before the workday begins.

solsta_cli local update --all --queue
solsta_cli queue run

Set as a scheduled task (e.g. 2:00 AM) so builds are ready when the team arrives.

Notes: 

  • The queue arguments assume the machines are part of a throttled network. See Orchestration Service for details.
  • The solsta_cli needs to be on each machine and each machine needs to execute the arguments

CI/CD Pipeline Install

Trigger installs or updates in Jenkins, TeamCity, GitHub Actions, or any CI system using M2M credentials.

solsta_cli login client_credentials \  
--client_id=$CLIENT_ID \  
--client_secret=$CLIENT_SECRETsolsta_cli local install \  
--product_name=LlamaCraft \  
--env_name=dev-daily \  
--location=c:/builds/lc/dev/ \  
--debugfile


Store CLIENT_ID and CLIENT_SECRET as secure environment variables in your CI system. M2M tokens expire after 24 hours, so authenticate at the start of each job.

Multi-Machine Rollback

Roll every machine in a lab back to a specific snapshot using the orchestration queue.

Snapshot history IDs are available in the Solsta GUI under the History tab for any environment.

Token Keep-Alive

User tokens expire if the CLI is not used for 30 days. On machines that sit idle, schedule a lightweight local read to keep the token refreshed.

solsta_cli local read

This reads local install data without making any changes and keeps the session token active.

Optional Repositories

When working with optional repositories, be explicit in every session. Optional repositories not named in a command string will be removed.


solsta_cli local install \  
--product_name=LlamaCraft \  
--env_name=dev-daily \  
--repository_name=dev-tools \  
--release_version=latest \  
--location=c:/builds/lc/dev/

Snapshot history IDs are available in the Solsta GUI under the History tab for any environment.

Token Keep-Alive

User tokens expire if the CLI is not used for 30 days. On machines that sit idle, schedule a lightweight local read to keep the token refreshed.

solsta_cli local read

This reads local install data without making any changes and keeps the session token active.

Optional Repositories

When working with optional repositories, be explicit in every session. Optional repositories not named in a command string will be removed.

solsta_cli local install \  
--product_name=LlamaCraft \  
--env_name=dev-daily \  
--repository_name=dev-tools \  
--release_version=latest \  
--location=c:/builds/lc/dev/


Use --queue for all multi-machine operations so the Orchestration Service can manage network bandwidth and prevent bottlenecks.