1495829 - [android-components] remove support for publishing to bintray jcenter

Status: RESOLVED FIXED

(Release Engineering :: Release Automation: Uploading, enhancement)

Description

[Mihai Tabara [:mtabara]⌚️GMT]

Sebastian confirmed the migration plans for apps still using the old artifact/groupId is roughly a couple of weeks. Ideally that’s no more than ~2-3 milestone releases.

* Once that happens, we can retire Massager 
* Once that happens we can retire the artifacts.yml
* Once above are done, we could integrate the artifacts.yml as being generated from settings.gradle instead in a for loop in a generative way.

Comment 1

[Mihai Tabara [:mtabara]⌚️GMT]

We can also track here the retirement of jcenter publishing, once it's official that we only publish to maven.m.o[1]

[1]: http://maven.mozilla.org/

Comment 2

[Mihai Tabara [:mtabara]⌚️GMT]

(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #1)
> We can also track here the retirement of jcenter publishing, once it's
> official that we only publish to maven.m.o[1]
> 
> [1]: http://maven.mozilla.org/

This includes:
* removing the publishing part from the build task
* removing the secrets from TC
* removing all the scopes and cleanup in the decision task for releases

Comment 3

[Mihai Tabara [:mtabara]⌚️GMT]

Tracked in here[1].

[1]: https://github.com/mozilla-mobile/android-components/pull/1102

Comment 4

[Mihai Tabara [:mtabara]⌚️GMT]

We'll track the removal of `artifacts.yml' file and relying on `settings.gradle` in a different bug. Let's keep this for the removal of bintray jcenter publishing and the removal of massager + dependencies.

Comment 5

[Mihai Tabara [:mtabara]⌚️GMT]

https://github.com/mozilla-mobile/android-components/commit/c90f4f0c06e8ac289d278d1da275b3f4d2e1d02d got merged. Next releases should stop pushing to bintray.

Comment 6

[Mihai Tabara [:mtabara]⌚️GMT]

This landed and 0.28 no longer published to bintray.
Thanks Johan for taking care of this!