Libraries, builds and revisions

If ReactorSDK is being used to automate Launch promotion, this area is the operational center of the gem. Libraries collect rules, data elements, and extensions into deployable bundles, builds turn those bundles into artifacts, and revisions let you inspect or compare exact point-in-time resource state. This overview page now points you to smaller pages for each part of the workflow.

Use this area

Read this area when you need to answer questions like:

• How do I create and manage libraries?
• How do I compare one resource against its upstream libraries?
• How do I trigger and poll builds?
• How do I inspect revision snapshots?
• Where do audit events, search, profiles, and notes fit into release tooling?

Page map

• Libraries Read this when you need library CRUD, relationships, workflow transitions, or find_with_resources.
• Library comparison Read this when you need a Development-versus-Staging style review across the entire library.
• Upstream chain Read this when you need upstream-library resolution or resource-level comparison.
• Builds Read this when you need build triggering, polling, or republish behavior.
• Revisions Read this when you need point-in-time snapshots for rules, data elements, or extensions.
• Supporting discovery Read this when you need audit events, search, profiles, or direct note lookup.

Common journeys

1. Assemble the deployment bundle in Libraries.
2. Run Library comparison when you want a release-wide diff.
3. Use Upstream chain when you need a resource-specific upstream lookup.
4. Trigger and poll the build in Builds.
5. Inspect exact snapshots in Revisions when you need to explain or diff a change.
6. Use Supporting discovery for audit trails, admin lookups, and search.