FlowFuse
DevOps Pipeline - External Integrations
Description
In talking with @robmarcer, and hearing from other customers about their requests for Pipeline features, we have an opportunity to extend Pipelines way beyond just pushing from one Instance to another. This Epic captures various steps we can take to improve the Pipeline feature set:
- Allow multiple "actions" per stage of a pipeline
- Provide a "Webhook" action in a Pipeline
- Provide a GitHub action in a Pipeline
Which customers would this be available to
Team + Enterprise Tiers (EE)
@robmarcer can you detail what you shared with me please, around the advantage/use-case here for web-hooks in Pipelines, etc. that you would have valued in the PS enagagements
Where a user runs more than one FlowFuse server, it is useful to be able to automate the migration of snapshots from pipelines on one FF instance to another. The most common way this seems to be done is using GitHub as an intermediary, where a snapshot is first sent up to a GH project then pulled back down into the second FF server. This can be used to facilitate other devops actions such as testing. This also gives the user the benefit of having a complete history of their changes in GH
I'm unsure if this would be best facilitated by a GH specific 'action' on the devops pipelines or if it would be better to have a configureable stage where actions to be taken can be selected or coded.
We have two paying enterprise customers (that I am aware of) who work in this way but they currently utilise our APIs to extract the snapshots so it's not really productised but does work. An alternative solution would be to create a NR blueprint which automates migration, I have built various proofs of concept showing how to do that if they are useful to share.
