[JIRA] (OVIRT-2183) Automate creation of "poll" jobs
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2183?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2183:
--------------------------------
Resolution: Duplicate
Status: Done (was: To Do)
Closing as duplicate of OVIRT-1876
> Automate creation of "poll" jobs
> --------------------------------
>
> Key: OVIRT-2183
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2183
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Standard CI (Pipelines)
> Reporter: Barak Korren
> Assignee: infra
>
> As a developer I would like to be able to configure upstream source polling jobs (In other works jobs that execute the "poll-upstream-sources" STDCI stage) from the STDCI YAML file in my project so that I never have to deal with JJB or the 'jenkins' repository.
> h3. Acceptance Criteria
> # To get "poll-upstream-sources" jobs working for a certain branch developers should only configure some setting in the STDCI YAML file of that project.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2034) Recreate the transactional CI mirrors with Pulp
by eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2034?page=com.atlassian.jir... ]
eyal edri updated OVIRT-2034:
-----------------------------
Epic Link: (was: OVIRT-403)
> Recreate the transactional CI mirrors with Pulp
> -----------------------------------------------
>
> Key: OVIRT-2034
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2034
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: CI Mirrors
> Reporter: Barak Korren
> Assignee: infra
>
> Right now, the CI mirrors are created and maintained by a set of custom scripts and jobs.
> It seems that [Pulp|https://pulpproject.org/] can do what our current system does. The reason behind not using it when we first made the mirrors system was out desire to provide a quick solution and avoid adding more services to maintain.
> There are however, quite a few reasons to want to switch to pulp:
> # Aside from RPMs it can also manage other interesting kinds of resources like Containers, DEB packages and Python packages.
> # If it works well for us - we can maintain less code by dropping the existing mirror management code
> # It has built-in distribution mechanisms that can be useful to scale it up.
> # It seems it has support for assigning packages to multiple repos. This cab be used as a tagging mechanism to implement OVIRT-2033
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2034) Recreate the transactional CI mirrors with Pulp
by eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2034?page=com.atlassian.jir... ]
eyal edri updated OVIRT-2034:
-----------------------------
Epic Link: (was: OVIRT-403)
> Recreate the transactional CI mirrors with Pulp
> -----------------------------------------------
>
> Key: OVIRT-2034
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2034
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: CI Mirrors
> Reporter: Barak Korren
> Assignee: infra
>
> Right now, the CI mirrors are created and maintained by a set of custom scripts and jobs.
> It seems that [Pulp|https://pulpproject.org/] can do what our current system does. The reason behind not using it when we first made the mirrors system was out desire to provide a quick solution and avoid adding more services to maintain.
> There are however, quite a few reasons to want to switch to pulp:
> # Aside from RPMs it can also manage other interesting kinds of resources like Containers, DEB packages and Python packages.
> # If it works well for us - we can maintain less code by dropping the existing mirror management code
> # It has built-in distribution mechanisms that can be useful to scale it up.
> # It seems it has support for assigning packages to multiple repos. This cab be used as a tagging mechanism to implement OVIRT-2033
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months