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

Pipeline Only Mode #3518

Closed
Lite5h4dow opened this issue May 21, 2024 · 1 comment
Closed

Pipeline Only Mode #3518

Lite5h4dow opened this issue May 21, 2024 · 1 comment

Comments

@Lite5h4dow
Copy link

Given that Gitness builds on Drone, are there plans to allow someone deploying this to disable the git repo management side of this application?

I tried Gitness for a good few months. but with it missing issues, projects, discussions, time tracking and all the other features my workflow requires, I decided to switch to Gitea and use Drone instead. now that I've been building out my repos and such in Gitea, I don't want to switch again even if gitness does end up getting all the features, I don't want to be in a situation where I'm forced to either switch to Gitness down the line or be stuck with Drone as it slowly decays from Harness' priority list.

Basically, I'm asking if I should hold onto Drone until gitness launches, fully featured and replace Drone or if I should be looking to replace Drone now with some other CI/CD Pipeline system.

@bradrydzewski
Copy link

bradrydzewski commented May 21, 2024

hey there, please see this thread which should answer you question: #3374 (comment). The tldr; is that we are working on supporting pipelines for third party repositories and we will never force anyone to host their code in Gitness

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants