Discussion: Dependencies on pipeline artefacts in upstream

Besides the more political arguments we exchanged over the mailing list, I’d like to raise some technical and organizational concerns around having dependencies on -fuse artefacts in upstream Syndesis:

• The pipeline build of fabric8-maven-plugin (with -fuse extension) uses base images for the builds which are not freely available on Docker Hub. See #3872 where this bites us.
• Who is responsible with an issue in these dependencies (e.g. d-m-p, f-m-p, kubernetes-client) ? Where can an issue be raised to fix this ? The source code for these pipeline builds are not freely available, so how could I fix this and can send a PR ? (asking for a non Red Hat friend).
• Are the referenced pipelines builds guaranteed to be available forever (to make syndesis release reproducible even when done in 5 years) ? Sure, stuff on Maven central can disappear, too, but then I can still recreate the upstream dependencies on my own from source.

Wdyt, could we resolve these issues ?

I would be happy to track fuse specific branches (as we already do in other projects), I just think its not appropriate on upstream branches (master, bug fix branches)

// cc @cunningt @chirino @heiko-braun

[lburgazzoli]

@oscerd sounds like we should move to the same spring-boot version Camel master is on.

I think moving to sb2 is something for a major release.

Maybe we could also think to remove the sb bits from integration runtime. I know @chirino disagree 😃 but as the runtime used is an “implementation detail” and not directly impacting users it may be an option.

[stale[bot]]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!