Closed QU3B1M closed 1 month ago
I will request changes.
First change: Create a table by team. If the pipeline does not have a responsible team, that table will be called "Deprecated".
Second change: Add a column to each table with a brief description and a list of the use cases covered by that pipeline. It will help to identify what should be maintained or not.
Regards.
I modified the Pipelines details.xlsx file to improve the information. I am waiting to respond to some questions and then move the status question.
Description
This issue aims to read and analyze the current Jenkins pipelines documentation, identifying which ones must be migrated for
v4.10.0
and listing their code location and dependencies.Tasks
Conclusion
All the pipelines were analyzed, and considering the migrations to GitHub Actions (GHA) that are planned or in progress by the development teams, and the DTT development by the QA team, this is the list of pipelines that are candidates to be removed or migrated to the new platforms.