Public Semaphore build project #92
AleksandarCole
started this conversation in
Collaboration Improvements
Replies: 1 comment
-
@lucaspin is working on this initiative, but we agreed that @VeljkoMaksimovic will help us out in:
Acceptance Criteria (by apr 14th):
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have discussed this prior to the launch of
Community Edition
Semaphore, and it popped up again in this ticket:#84
However, there are still a few unknowns so I'm opening a discussion to help scope this out.
Problem Statement
We've launched Semaphore Community Edition as an open source project, but our CI/CD infrastructure is still running in a private Semaphore project. This prevents external contributors from seeing build results for their PRs, which is crucial for a successful open source project.
Current State
Desired Outcome
A public CI pipeline that:
Discussion Points
What should the public CI pipeline include and exclude?
What modifications are needed to our existing pipeline?
How will the public CI and internal CD pipelines coexist?
Next Steps
Let's discuss these points and define a clear implementation plan that balances openness for contributors with security for our deployment process.
Beta Was this translation helpful? Give feedback.
All reactions