-
-
Notifications
You must be signed in to change notification settings - Fork 364
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
Multiple pipeliens per repository #10
Comments
The design that I'm implementing: The pipeline is either in the
For multiple pipelines you must use separate files
With this approach we tackle two problems:
|
Even if a limitation is set to an agent / process? I understand the thoughts behind and this is very useful to accelerate everything. But your idea is thought through. |
If you ask about the per agent limit of Continuing on the above example, if you have The behavior is exactly the same how matrix builds work today. |
That's great! - Thanks for the answer. |
I've still have a question or maybe a feature request. Example: drone server and drone agent are always running on Fileserver... Default = Fileserver Some bash logic for demonstrating: if [ "Workstation" == "online" ] ; then
DRONE_USE_AGENT="Workstation"
else
DRONE_USE_AGENT="Fileserver"
fi I hope that I have shown understandable. |
Distinguishing between agent capabilities is not in scope for this task. I believe that it's best if agents have identical capabilities in general. Now some cases would require named agents, like when you attach some special hardware to your agent nodes. But even then, the mapping would be static, so the presented if-else logic would not be a feature I would implement. |
The if-else logic I have just introduced for more clarity. |
Docs: How to try it out on a branch while keep existing builds running?
It will search for the pipeline files under |
Find a way that repositories can have multiple pipelines triggered in a webhook.
For shorter feedback loop back to Github.
Today in a typical linting - building - testing pipeline the result of a lint only makes back to Github if all steps are done. The goal is to be able to lint in one pipeline, build and test in another one. This way developers can see linting results way quicker.
The text was updated successfully, but these errors were encountered: