###### tags: `Monthly Community Meetings`

# 2024-10-10 Eiffel community meeting: Summit follow-up

- ActT linking to SCC
- Jenkins environment
- Bitbucket source of SCC
- Multibranch webhook plugin triggering builds
- Could extract SCC id from the payload and pass it to a downstream build that actually carries out the work. The eiffel-broadcaster plugin has an API endpoint that accepts Eiffel links for the ActT, or you could use the `buildWithEiffel` pipeline step which also supports Eiffel-specific options, but not yet Eiffel links (but that's easily added).
- Generic RabbitMQ trigger also used.
- Compositions for submodules and other subcomponents
- Theoretically, the compositions of submodules or other references is known at the time of the commit, and it should arguably be referenced by the commit event.
- But that's not necessarily possible to achieve, e.g. because the resolution of other references isn't possible to do for the SCM system, in which case sending the CD afterwards is legitimate.
- The CD itself doesn't express the hiearchy inherent in supermodule/submodule relationships:
- The CAUSE link of the CD should point to the supermodule SCC, and that can be used to identify the supermodule in the contents of the composition, which also includes the submodules.
- Another option is to have the CD have two ELEMENT links; one to the SCC/SCS of the supermodule, and one to another CD containing the submodules.