[CI] Publish nightly builds to OBS

[straight-shoota]

The base is laid out in crystal-lang/distribution-scripts#94

Maintenance releases are automatically pushed to the unstable channel. I'm not sure if we want that, but it was simple to set up with just duplicating the OBS integration for nightlies.

[bcardiff]

I was going to say that I've used dist_ for building the packages and push_ for publishing them, in that regard the job should be named push_obs_nightly. Yet, it seems I broke this rule when I added dist_bintray 😅 .

I am not sure if we should publish maintenance packages directly to unstable. I imagined that unstable packages will be used for pre releases manually. No strong opinions, maybe we should start with restoring nightlies only for now.

[straight-shoota]

I am not sure if we should publish maintenance packages directly to unstable. I imagined that unstable packages will be used for pre releases manually. No strong opinions, maybe we should start with restoring nightlies only for now.

Yes, that sounds like a better plan. With the current configuration, any ci branch would be published as an unstable release. That's not the intention of the unstable channel. Then we'd have to introduce different CI workflows for maintenance and and pre-releases to avoid pushing the former to the package repository.

[straight-shoota]

Maybe we could try making push_obs_maintenance manually triggered? Then you would have to push a button in circleci to push to OBS, but everything would run automatically.

However, it might be better to just leave that off. We haven't been using unstable releases a lot (if at all?) and it probably doesn't hurt doing everything manually for a while until we figure we could use some assistance. It's easy to set up if necessary.

[bcardiff]

However, it might be better to just leave that off. We haven't been using unstable releases a lot (if at all?) and it probably doesn't hurt doing everything manually

Let's avoid pushing unstable releases for now until we figure a workflow for unstable.