Notes

Notes

• Backend (database?) or GitHub repository (Like JSON files)
  • Permission? Who is allowed to push? From the CLI? GH action?
• High level model of migration (list of recipes? Other metadata?)
• Other infra reports stored on https://reports.jenkins.io/
• In the meantime, let’s open pull request on a public repo
  • Let’s see if we can use some kind of auto-merge feature
• How to store files on the GitHub repo?
  • Timestamp? Consolidate data (urgent)
• Each time we open a PR on a Jenkins plugin, we need to track this PR?
• We also need to track failed PR
• We cannot use PR tags (permission, failed recipe execution)
• Available logs for the migration run (perhaps we need a different logger)

Next steps

• Each time we run Plugin Modernizer, a PR is open on a public repo to track the status
  • Include execution status (success, fail, etc.)
  • Recipes applied
  • PR link if any
  • Metadata (plugin name, etc.)
  • Probably a new repo on jenkins-infra but we can test with any repo

Transcript