Keeping Different Versions of the Python Script in VCS
The Python Script Component supports integration with a Version Control System (VCS) to manage script versions. This allows users to maintain multiple versions of a script, pull older versions for reuse, and push new versions for version tracking and collaboration.
Each committed version is tracked sequentially as V1, V2, V3, ….
Key Capabilities
Pull Script – Retrieve a previously committed version from VCS.
Push Script – Commit and version new script changes to VCS.
Maintain a complete version history with commit messages.
Restore older versions for troubleshooting or rollback scenarios.
Pull Script from VCS
Navigate to the Python Script Component → Configuration section.
Click the Pull Script from VCS icon.
The Pull Script from VCS dialog box opens.
Select the desired version number from the list of committed versions.
Click OK.
Notification messages appear in sequence:
Fetching available versions.
Pulling selected version.
Success – confirms the script has been pulled from VCS.
The selected version of the script replaces the current script in the component editor.
Push Script to VCS
Navigate to the Python Script Component → Configuration section.
Click the Push Script to VCS icon.
The Push Script to VCS dialog box opens.
Enter a commit message describing the script changes.
Example:
"Added data filtering by customer region"
Click OK.
A success notification confirms the script has been committed to VCS.
Note:
If the script in the component is identical to the latest committed version, it will not be pushed again.
New scripts must include a unique commit message.
Committed scripts are versioned sequentially (V1, V2, V3...).
Example Workflow
Pull Script – Developer pulls
V3of the Python script to reproduce a previous pipeline run.Modify Script – Adjusts transformation logic to filter data differently.
Push Script – Commits the modified script as
V4with a commit message"Updated filter logic for high-value transactions".