Skip to content

Draft: Pipeline does not trigger automatically after importing new project

Javiera Tapia requested to merge 438786-pipeline-is-not-available-in-ui-after-creating-new-project-from-template into master

What does this MR do and why?

This MR fixes the behavior once a project is created from an import or template, and a pipeline is not automatically created. After the project is successfully imported, a CreatePipelineWorker is queued using the current fix. This bugfix is behind a short-lived FF to monitor the Sidekiq and CI stability.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screen_Recording_2024-03-27_at_11.07.51

How to set up and validate locally

  • Follow these steps to create and register a runner locally. A runner needs to be enabled to allow the CI to run the pipeline.
  • Enable the FF locally: 
    rails c

Feature.enable(:create_pipeline_after_project_import)
  • Create two new projects, one from importing and the other from templates.
  • Go to pipelines; a newly created pipeline should be triggered automatically once the import process finishes.

Related to #438786

Edited by Javiera Tapia

Merge request reports