I am considering n8n as a replacement of our jenkins workflow. To check it twice I will ask some point. : )
A workflow in the end can trigger another workflow?
A node can be shared among some workflow?
Because I have 3 workflows in jenkins which each has 10 jobs that 8 are exactly same, 2 totally different.
If I can connect multiple workflow, same part will be defined as a single shared workflow, and 2 different jobs will be defined as 3 of partial workflow.
workflow 1
a b c d e f u v o p
workflow 2
a b c d e f w x o p
workflow 3
a b c d e f y z o p
Another questuon.
How can we manage the workflow based on vcs. for example, workflow import from git. workflow version control(e.g. rollback).
A workflow can trigger another workflow if you use the “Execute Workflow” node at the end of it, A node however would only exist in the workflow so you can use the same node in multiple workflows but it wouldn’t share the data between them (assuming this is what you mean).
There is no guidelines for using VCS with n8n but we are currently looking at options to allow this, At the moment you can use the API, CLI or UI to export and import workflows that you could store in git or anywhere else but how you would actually use it would be up to you and what fits your requirements.
