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.

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

Spike: Evaluate swapping Maru with Dagger / Tekton #57

Open
Racer159 opened this issue Jun 3, 2024 · 2 comments
Open

Spike: Evaluate swapping Maru with Dagger / Tekton #57

Racer159 opened this issue Jun 3, 2024 · 2 comments
Labels
enhancement ✨ New feature or request

Comments

@Racer159
Copy link
Contributor

Racer159 commented Jun 3, 2024

Is your feature request related to a problem? Please describe.

We should evaluate the benefits of continuing our pipeline component implementation with Maru runner vs using an existing tool like Dagger or Tekton.

Describe the solution you'd like

We should swap Maru for Dagger and Tekton within the pipeline vertical slice and document our decision in an ADR and the design document being worked in #43 .

Additional context

Both of these technologies were previously evaluated but we should reevaluate changes that have occurred in the past several months as both projects have evolved quite a lot.

@Racer159 Racer159 added the enhancement ✨ New feature or request label Jun 3, 2024
@Racer159
Copy link
Contributor Author

Racer159 commented Jun 3, 2024

Marked as blocked on defenseunicorns/uds-package-gitlab-runner#87 and #55 as these will be needed to have a practical example to test with.

@docandrew
Copy link

The HNCD team is happy to share some lessons learned from our experience with Dagger if this ticket is unblocked or reconsidered in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement ✨ New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants