React to expected Arcade change: removing some channels

[dagood]

The installer build depends on the list of channels, so we have to react:

runtime/eng/pipelines/installer/azure-pipelines.yml

Lines 214 to 229 in 666923a

	# Publish channel configuration. The publish template wraps Arcade publishing and adds some
	# extras that aren't implemented in Arcade yet.
	#
	# - dependsOn: <ID of the Arcade stage that finalization should run after>
	# channel:
	# name: <Name of this channel, for logging and readability>
	# bar: <Name of the Arcade variable that contains the ID of this channel in BAR>
	# storage: <Name of the Latest channel to publish to in dotnetcli blob storage>
	dependsOnPublishStages:
	- dependsOn: NetCore_Release30_Publish
	channel:
	name: .NET Core 3 Release
	bar: PublicRelease_30_Channel_Id
	storage: release/3.0-preview9
	public: true

@mmitche will be removing the release channels from the templates in master Arcade.

We don't need to wait for the arcade change, it's fine to have channels exist with no entry in the installer build's mapping, there just won't be custom steps run on them if they happen to get assigned.

[ViktorHofer]

@jkoritzinsky @dagood do you intend to submit a fix for this?

[dagood]

@mmitche asked when it would be best to send a PR to make the change (before or after your work, @ViktorHofer), I don't think anyone else is tracking doing it. I mentioned that I wouldn't think the timing would matter on this but if that's not true, good time to clear it up.

[mmitche]

Yeah, I can easily send a PR, question was just whether the repo was open for those kind of PRs.

[ViktorHofer]

Yes, the repo is now open internally.

[dagood]

Closing, obsolete: the runtime official build no longer has the custom publish infra that used this list, and the list has been removed from the repo.