[OSCI] Setup branches and CI for Sustaining team

Bug #1417625 reported by Vitaly Sedelnik
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Invalid
High
Fuel for Openstack
5.1.x
Fix Released
High
Alexander Tsamutali
6.0.x
Fix Released
High
Alexander Tsamutali
6.1.x
Invalid
High
Fuel for Openstack

Bug Description

Sustaining team needs following infrastructure to be created:
- Branch 6.0_updates (from stable 6.0)
- updates dir on http://fuel-repository.mirantis.com/fwm/6.0/
- CI setup to build ISO and updated packages from 6.0_updates

The sampe environment should be created for 5.1.1 (and probably for 5.1) - see the milestones

Tags: osci
summary: - Setup branches and CI for Sustaining team
+ [OSCI] Setup branches and CI for Sustaining team
Changed in mos:
milestone: none → 6.0
milestone: 6.0 → none
no longer affects: fuel
Changed in mos:
importance: Undecided → High
assignee: nobody → Fuel for Openstack (fuel)
tags: added: osci
Changed in mos:
milestone: none → 6.0.1
status: New → In Progress
Revision history for this message
Alexander Tsamutali (astsmtl) wrote :
Revision history for this message
Vitaly Sedelnik (vsedelnik) wrote :

Please create "updates" branches and appropriate CI for 5.1 and 5.1.1 releases:
- branch 5.1-updates (from stable 5.1)
- branch 5.1.1-updates (from stable 5.1.1)

Revision history for this message
Alexander Tsamutali (astsmtl) wrote :

Created 5.1-updates and 5.1.1-updates (everything is analogous to 6.0-updates).

Changed in mos:
milestone: 6.0.1 → 6.1
status: In Progress → New
Revision history for this message
Vitaly Sedelnik (vsedelnik) wrote :

Next step: create public CentOS/Ubuntu repositories for every "updates" branch to host updated packages.
- First priority is repos for 6.0-updates branch
- We need Jenkins job to copy all updated packages to these repositories
- Please consider 100 packages/month as capacity needed, avg size of the package could be obtained from existing repos

Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

The issue is not applicable to 6.1

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.