# Workshop: Ready to use Pulp CI jobs for everyone?

[Back to PulpCon2023 Schedule](https://hackmd.io/@pulp/pulpcon_2023)

Speaker: Quirin Pamp
GitHub/Matrix: quba42
Company: [ATIX](https://atix.de/en/)
Slot: Wednesday, November 8 (day #3) 11:00am EST, 17:00 CET

## Agenda

* Presentation part: How ATIX manages Pulp using CI
* Workshop part:
* Can this approach be generalized as a community library of reusable Pulp CI jobs?
* Is there even demand for such a library?
* Is this just what https://github.com/pulp/pulp-ci is?
* How general re-usable is this project?
* Where is the approach similar to the one I sketched where is it different?
* Does anyone actually have time to put work into doing this?
* Use Cases:
* Caching publicly available content
* https://slsa.dev/spec/v1.0/levels
* https://gitlab.com/groups/gitlab-org/-/epics/5128

## Example CI jobs

Does this:

.pulp_ci_resources_base_job:
  before_script: pip install pulp_ci_resources
  script:
    - python3 -c "from pulp_ci_resources import ci_job_entrypoint" ${CI_JOB_NAME} || EXIT_CODE=$?
    
create_pulp_repo:
  extends: .pulp_ci_resources_base_job
  variables:
    PULP_REPO_NAME: "my_repo/el${EL_VERSION}"
  parallel:
    matrix:
      - EL_VERSION: "8"
      - EL_VERSION: "9"

Add any value over:

.pulp_ci_resources_base_job:
  before_script: pip install pulp-cli
    
create_pulp_repo:
  extends: .pulp_ci_resources_base_job
  script:
    -  pulp rpm repository create --name "my_repo/${EL_VERSION}"
  parallel:
    matrix:
      - EL_VERSION: "8"
      - EL_VERSION: "9"

=> Probably not in this case.