search

dotnet / source-build

A repository to track efforts to produce a source tarball of the .NET Core SDK and all its components
MIT License
265 stars 132 forks source link

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

Open mmitche opened 10 months ago

mmitche commented 10 months ago

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?

dotnet-issue-labeler[bot] commented 10 months ago

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

mmitche commented 10 months ago

@ViktorHofer @hoyosjs @wtgodbe

jkoritzinsky commented 1 month ago

If we do the following items, we can remove the requirement for separate containers to build Linux packages.