Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate Opni to GHA #45406

Open
MKlimuszka opened this issue May 7, 2024 · 0 comments
Open

Migrate Opni to GHA #45406

MKlimuszka opened this issue May 7, 2024 · 0 comments
Assignees
@alexandreLamarre
Labels
kind/enhancement Issues that improve or augment existing functionality kind/tech-debt Formerly issues labeled as ci-improvements, tasks, flaky tests, and post-release. QA/None Indicates that the task or issue does not need QA. team/observability&backup the team that is responsible for monitoring/logging and BRO

Comments

@MKlimuszka
Copy link
Collaborator

MKlimuszka commented May 7, 2024 •
edited

Migrate Opni to GHA

  | SURE-8019 | Migrate rancher/opni from Drone to GH Actions |
  | SURE-8020 | Migrate rancher/opni-drain-service from Drone to GH Actions |
  | SURE-8021 | Migrate rancher/opni-inference-service from Drone to GH Actions |
  | SURE-8022 | Migrate rancher/opni-insights-service from Drone to GH Actions
  | SURE-8023 | Migrate rancher/opni-kibana-dashboard from Drone to GH Actions |
  | SURE-8024 | Migrate rancher/opni-metrics-service from Drone to GH Actions |  s
  | SURE-8025 | Migrate rancher/opni-nulog-train from Drone to GH Actions |  
  | SURE-8026 | Migrate rancher/opni-payload-receiver-service from Drone to GH Actions |
  | SURE-8027 | Migrate rancher/opni-preprocessing-service from Drone to GH Actions |  
  | SURE-8028 | Migrate rancher/opni-training-controller from Drone to GH Actions |
  | SURE-8029 | Migrate rancher/opni-ui from Drone to GH Actions
@MKlimuszka MKlimuszka added kind/enhancement Issues that improve or augment existing functionality kind/tech-debt Formerly issues labeled as ci-improvements, tasks, flaky tests, and post-release. QA/None Indicates that the task or issue does not need QA. team/observability&backup the team that is responsible for monitoring/logging and BRO labels May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexandreLamarre alexandreLamarre

Labels
kind/enhancement Issues that improve or augment existing functionality kind/tech-debt Formerly issues labeled as ci-improvements, tasks, flaky tests, and post-release. QA/None Indicates that the task or issue does not need QA. team/observability&backup the team that is responsible for monitoring/logging and BRO
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MKlimuszka @alexandreLamarre