fedora-ci / metadata

#16 Detailed specification for the "prepare" step
Closed by psss. Opened by psss.

Closed
Reopen Issue

@mrc0mmand shared with us the systemd use case for storing different requires for different distribution releases. See also this github issue for more details. After discussion we've agreed that the most straightforward solution seems to be to use L2 metadata for this, specifically the prepare step. Let's create detailed specification for this step, so that Franta can start experimenting with this. For the start, the how: ansible implementation should be enough.

Example prepare section:

prepare:
    how: ansible
    playbooks:
        - 'common.yml'
        - 'rhel7.yml'

Several playbooks can be provided and will be applied using ansible-playbook in the given order.

Metadata Update from @psss:
- Issue assigned to psss

Metadata Update from @psss:
- Issue tagged with: L2 Metadata

@mvadkert, @happz do you agree with the above-mentioned syntax?

this looks good to me :)

Thanks, detailed description available for review in #18.

Merged a long time ago.

Metadata Update from @psss:
- Issue status updated to: Closed (was: Open)
Metadata

L2 Metadata

None
None
None
Related Pull Requests
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.