#6350 integrate atomic (host and other) CI/CD into Fedora
Closed: Duplicate 2 years ago Opened 5 years ago by walters.

Breaking out from:

https://fedorahosted.org/rel-eng/ticket/6313

Let's define a system and process for CD (Continuous Delivery) that bypasses manual integration via Koji/Bodhi and ships as quickly as possible to a small audience on dl.fedoraproject.org.

Specifically, use rpmdistro-gitoverlay to mirror upstream sources that we know have been peer reviewed already, and build/ship them automatically.

Also generate a devel/ ostree ref based on this content, and potentially images.

Integrate pull request testing into this too.

Resources required:
- OpenStack tenant resources
- Ability to write to dl.fedoraproject.org somewhere


Adding cloud mailing list.

We will not be bypassing bodhi for anything that goes on dl.fedoraproject.org we will have to use a atlernate delivery mechanism

Replying to [comment:2 ausil]:

We will not be bypassing bodhi for anything that goes on dl.fedoraproject.org we will have to use a atlernate delivery mechanism

I'm not sure I understand this without punctuation.

Surely there is plenty of content now under http://dl.fedoraproject.org/pub/alt/ which hasn't gone through bodhi, right?

What is the specific concern?

Could be something other than dl.fedoraproject.org, say dev.atomic.fedoraproject.org. Perhaps that is better indeed.

Replying to [comment:3 mattdm]:

I'm not sure I understand this without punctuation.

I don't mean that to be rude -- sorry if it was taken that way. I literally don't know if you mean "We will not be bypassing bodhi for anything that goes on dl.fedoraproject.org. We will have to use an alternate delivery mechanism" or "We will not be bypassing bodhi. For anything that goes on dl.fedoraproject.org, we will have to use an alternate delivery mechanism."

Replying to [comment:3 mattdm]:

Replying to [comment:2 ausil]:

We will not be bypassing bodhi for anything that goes on dl.fedoraproject.org we will have to use a atlernate delivery mechanism

I'm not sure I understand this without punctuation.

Surely there is plenty of content now under http://dl.fedoraproject.org/pub/alt/ which hasn't gone through bodhi, right?
AFAIK it all has unless it has come from rawhide

What is the specific concern?

the concern I have is that dl.fp.o is targeted at a really wide group of people, who likely have set ideas about content that comes from dl.fp.o or a mirror of it that will not be true. I am also concerned about mirror churn when atomic has no ability today afaik to actually use mirrormanager and take advantage of the mirror network

afaik this would be targeted at a really small set of people wanting to test something super raw. likely a non mirrored location such as kojipkgs.fedoraproject.org/atomic would be more appropriate.

Replying to [comment:6 ausil]:

AFAIK it all has unless it has come from rawhide

I was looking at stuff like http://dl.fedoraproject.org/pub/alt/purpleidea/ -- I think something like this is what's meant. But sounds like it's fine if it's not even that.

What is the specific concern?

the concern I have is that dl.fp.o is targeted at a really wide group of people, who likely have set ideas about content that comes from dl.fp.o or a mirror of it that will not be true. I am also concerned about mirror churn when atomic has no ability today afaik to actually use mirrormanager and take advantage of the mirror network

Yeah, that sounds completely valid, and as I understand it the request for "dl.fpo" wasn't meant to mean that. Just... somewhere not a personal box and which Atomic developers can feel confident in using. Colin, do I understand correctly?

Speaking as Atomic Community Guy, I would be thrilled to be at atomic.fedoraproject.org. That doesn't solve anyone else's CI needs, though, does it?

Metadata Update from @walters:
- Issue set to the milestone: Fedora 24 Alpha

4 years ago

Metadata Update from @syeghiay:
- Issue close_status updated to: None

2 years ago

Metadata Update from @syeghiay:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata