Skip to content
Tech News
← Back to articles

CI jobs artifacts should not be difficult

read original more articles
Why This Matters

This article highlights how DSCI streamlines the management of job artifacts within CI pipelines by simplifying the process of creating and sharing files across tasks. By standardizing artifact handling through a dedicated directory, it enhances efficiency and reduces complexity for developers and DevOps teams. This approach ensures smoother pipeline execution and easier debugging, ultimately benefiting both industry professionals and end-users.

Key Takeaways

job-artifacts

# Job Artifacts DSCI dramatically simplify working with artifacts process inside pipelines. To create artifact file just create it in `~/artifacts/` directory in some task file, for example: ```bash #!/bin/bash echo "DSCI is cool" > ~/artifacts.txt ``` The the next job will see it in the same directory: ```python #!/usr/bin/python3 from pathlib import Path file_path = Path.home() / "artifacts.txt" # 2. Read the file safely using a context manager try: with open(file_path, "r", encoding="utf-8") as file: content = file.read() print(content) except FileNotFoundError: print(f"Error: The file at {file_path} was not found.") ``` --- That's it. Artifacts de-facto is any file located in `~/artifacts` dir, If some job decides to remove a file from `~/artifacts/` it won't be available for the next jobs. So artifacts works as a pipeline data buffer