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

Make and deploy release on maven centrale #1

Open
2 of 3 tasks
juherr opened this issue Oct 30, 2015 · 26 comments · Fixed by #139
Open
2 of 3 tasks

Make and deploy release on maven centrale #1

juherr opened this issue Oct 30, 2015 · 26 comments · Fixed by #139

Comments

@juherr
Copy link
Member

juherr commented Oct 30, 2015

I made an organization on Bintray: https://bintray.com/testng-team

@missedone I can add you that will allow you to make a release there.

We will see later with @cbeust if/how to link it with central.

  • Manage release
  • Deploy snapshots
  • Sync with maven central
@juherr juherr changed the title Make and deploy release on Bintray Make and deploy release on Bintray and maven centrale Jan 11, 2016
@missedone
Copy link
Contributor

please let me know what can i do.
do we need authorize any script to build and upload the binaries to Bintray?

thanks

@cbeust
Copy link
Collaborator

cbeust commented Jan 11, 2016

I think @juherr looked into it and it doesn't seem possible for all members of the team to deploy, only one person. Was that right, @juherr?

@juherr
Copy link
Member Author

juherr commented Jan 11, 2016

It should be possible for the bintray team I created. I will try it.

Le lun. 11 janv. 2016 22:25, Cedric Beust [email protected] a
écrit :

I think @juherr https://github.com/juherr looked into it and it doesn't
seem possible for all members of the team to deploy, only one person. Was
that right, @juherr https://github.com/juherr?


Reply to this email directly or view it on GitHub
#1 (comment)
.

@cbeust
Copy link
Collaborator

cbeust commented Jan 11, 2016

Also, I suspect one of us could create a key and then we all share it.

And uploading stuff to bintray is trivial with Kobalt ;-)

Cédric

On Tue, Jan 12, 2016 at 2:06 AM, Julien Herr [email protected]
wrote:

It should be possible for the bintray team I created. I will try it.

Le lun. 11 janv. 2016 22:25, Cedric Beust [email protected] a
écrit :

I think @juherr https://github.com/juherr looked into it and it
doesn't
seem possible for all members of the team to deploy, only one person. Was
that right, @juherr https://github.com/juherr?


Reply to this email directly or view it on GitHub
<
#1 (comment)

.


Reply to this email directly or view it on GitHub
#1 (comment)
.

@juherr
Copy link
Member Author

juherr commented Jan 12, 2016

In fact, it is not possible to share a personal bintray repo between 2 accounts, but it is possible with group repositories (what I did).
After, we will have to use your personal sonatype account to push from bintray to maven centrale (via bintray ui)

@missedone Do you have a bintray account?

@missedone
Copy link
Contributor

just create one account: missedone
thanks

@missedone
Copy link
Contributor

hi @juherr , @cbeust
i just had a try with releasing onto bintary, it works as you can see artifacts uploaded here: https://bintray.com/testng-team/test/testng-remote/view#files/org/testng

i will create a DEPLOY.md later to document the release process,

@missedone
Copy link
Contributor

as you might know, Bintary does not support uploading snapshot artifacts. only release bits can.

@missedone
Copy link
Contributor

@juherr
Copy link
Member Author

juherr commented Jan 19, 2016

For snapshots, we can use Sonatype or JFrog

@missedone
Copy link
Contributor

i created a new repo with package: https://bintray.com/testng-team/testng-extras/testng-remote/view to replace https://bintray.com/testng-team/test/testng-remote/view, what do you think about the name?

@juherr
Copy link
Member Author

juherr commented Jan 19, 2016

@missedone
Copy link
Contributor

im ok with this 👍

let's clean up the rest of them

@missedone
Copy link
Contributor

later, we might need add travis-ci as well?

@juherr
Copy link
Member Author

juherr commented Jan 19, 2016

later, we might need add travis-ci as well?

Yes! #20

@missedone
Copy link
Contributor

it requires a sonatype account to sync jcenter to maven central:
maven_central
is there any existing account we can use?

@juherr
Copy link
Member Author

juherr commented Jul 7, 2016

Not yet, you can ask for a new one.

Le jeu. 7 juil. 2016 06:28, Nick Tan [email protected] a écrit :

it requires a sonatype account to sync jcenter to maven central:
[image: maven_central]
https://cloud.githubusercontent.com/assets/555134/16642495/713355a6-43c0-11e6-9673-e79fbaa6b0b1.png
is there any existing account we can use?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAPi6V2PckyqwRVDy2OIR3KP6-KrMJ_Kks5qTIBrgaJpZM4GZIFP
.

@juherr
Copy link
Member Author

juherr commented May 18, 2017

Rultor could be used to deploy on maven central if needed: http://www.yegor256.com/2014/08/19/how-to-release-to-maven-central.html

@juherr
Copy link
Member Author

juherr commented May 18, 2017

@missedone About your old question, I think @cbeust will have to set its credentials if we want to sync bintray with maven central because he owns the org.testng groupId

@juherr
Copy link
Member Author

juherr commented Mar 1, 2022

Up.

Bintray is dead and the artifact could not be used by others. For example, Gradle: see gradle/gradle#19960

@krmahadevan I think you've already published a lot of artifacts and know what should be done, right?

@juherr juherr changed the title Make and deploy release on Bintray and maven centrale Make and deploy release on maven centrale Mar 1, 2022
@missedone
Copy link
Contributor

@juherr @krmahadevan not sure who can set the gpg key on this github repo secrets for the maven publish.
also, it need @cbeust help to claim the ownership of the groupId org.testng, i'm not quite family with this process.

@juherr
Copy link
Member Author

juherr commented Mar 2, 2022

@krmahadevan and I can publish under the org.testng groupId.

@krmahadevan and you should be able to declare secrets under the testng-team github org. If not, ping me and I will promote your rights.

@krmahadevan
Copy link
Member

Up.

Bintray is dead and the artifact could not be used by others. For example, Gradle: see gradle/gradle#19960

@krmahadevan I think you've already published a lot of artifacts and know what should be done, right?

Yes. Here are the steps. First we need to add below secrets into the repository settings (I have access to that web page, but I dont know the actual secrete values there)

Below is a screenshot of the secrets that I have for my github organisation https:// github.com/rationaleemotions

image

Then we can create a github workflow that looks like this

We then alter the pom file to look like this essentially adding a release profile

That should be sufficient.

We also need to be removing this distribution management section from our pom file and also remove the repositories tag as well.

@krmahadevan
Copy link
Member

@krmahadevan and I can publish under the org.testng groupId.

I didnt know this :)

@krmahadevan and you should be able to declare secrets under the testng-team github org. If not, ping me and I will promote your rights.

LIke I mentioned earlier, I can access the page, but I don't know what values to put in there.

@missedone
Copy link
Contributor

is there any place we can publish the snapshot?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants