Skip to content

Figure out what to do about installers that can only be built in specific containers #3986

@mmitche

Description

@mmitche

There are some assets (deb and rpm bits) that are built in specific containers. Up till this point, the plan has been to divide up the verticals based on the existing runtime legs, and invoke a build command for each one. This should then produce all outputs required to ship .NET. How do we handle deb and rpm packages in this case? The runtime build usually invokes builds of those packages in separate containers. This is less desirable as it uses AzDO tasks to accomplish this, meaning you'd have to exit the build and re-enter.

What should be done here?

Sub-issues

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions