Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moving plugin release process to Bintray #961

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

langsmith
Copy link
Contributor

Resolves #915 by moving the plugin artifact release process to Bintray. The work in this pr is largely based off of similar work done in mapbox-gl-native and in the Java SDK.

@langsmith
Copy link
Contributor Author

Right now on this pr, I get the following error when I run make publish after running build-release:

* What went wrong:
Execution failed for task ':plugin-annotation:publishMapboxPluginPublicationPublicationToMavenLocal'.
> Failed to publish publication 'MapboxPluginPublication' to repository 'mavenLocal'
   > Invalid publication 'MapboxPluginPublication': multiple artifacts with the identical extension and classifier ('aar', 'null').

Screen Shot 2019-07-02 at 11 03 10 AM

I'm still looking into it. The fix might be making a separate MavenPublication for each plugin in the gradle-bintray.gradle file 😕 .

@langsmith langsmith force-pushed the ls-moving-release-process-to-bintray branch from c57521a to cf55713 Compare July 2, 2019 20:36
@langsmith
Copy link
Contributor Author

So weird because there's only one .aar file per plugin after I do make build-release. I guess I'm misunderstanding something about a MavenPublication.

Screen Shot 2019-07-02 at 3 29 33 PM

@langsmith langsmith force-pushed the ls-moving-release-process-to-bintray branch 2 times, most recently from 8752c98 to 91228eb Compare July 11, 2019 17:31
@langsmith langsmith force-pushed the ls-moving-release-process-to-bintray branch 2 times, most recently from abbd010 to d5e3642 Compare July 25, 2019 17:37
@langsmith langsmith force-pushed the ls-moving-release-process-to-bintray branch from d5e3642 to 2ad8078 Compare July 25, 2019 18:40
@langsmith
Copy link
Contributor Author

This is on hold as we continue to explore alternative ways to deploy our products

@langsmith langsmith force-pushed the ls-moving-release-process-to-bintray branch from 2ad8078 to 34d693b Compare November 12, 2019 00:05
@stale
Copy link

stale bot commented Jan 11, 2020

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the archived Archived by Stale bot. label Jan 11, 2020
@stale
Copy link

stale bot commented Jan 11, 2020

This pull request has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions.

@stale stale bot closed this Jan 11, 2020
@langsmith langsmith reopened this Jan 11, 2020
@stale stale bot removed the archived Archived by Stale bot. label Jan 11, 2020
@stale
Copy link

stale bot commented Mar 11, 2020

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the archived Archived by Stale bot. label Mar 11, 2020
@stale
Copy link

stale bot commented Mar 11, 2020

This pull request has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions.

@stale stale bot closed this Mar 11, 2020
@langsmith langsmith reopened this Mar 11, 2020
@stale stale bot removed the archived Archived by Stale bot. label Mar 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Refactor the release process to be based on Bintray
1 participant