testng-team / testng-remote

Remote TestNG
Apache License 2.0
12 stars 7 forks source link

Make and deploy release on maven centrale #1

Open juherr opened 8 years ago

juherr commented 8 years ago

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.

missedone commented 8 years ago

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

thanks

cbeust commented 8 years ago

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 commented 8 years ago

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

Le lun. 11 janv. 2016 22:25, Cedric Beust notifications@github.com 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 https://github.com/testng-team/testng-remote/issues/1#issuecomment-170694437 .

cbeust commented 8 years ago

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 notifications@github.com wrote:

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

Le lun. 11 janv. 2016 22:25, Cedric Beust notifications@github.com 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 < https://github.com/testng-team/testng-remote/issues/1#issuecomment-170694437

.

— Reply to this email directly or view it on GitHub https://github.com/testng-team/testng-remote/issues/1#issuecomment-170706479 .

juherr commented 8 years ago

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 commented 8 years ago

just create one account: missedone thanks

missedone commented 8 years ago

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 commented 8 years ago

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

missedone commented 8 years ago

here is the release procedure: https://github.com/testng-team/testng-remote/blob/release_to_bintray/RELEASE.md

juherr commented 8 years ago

For snapshots, we can use Sonatype or JFrog

missedone commented 8 years ago

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 commented 8 years ago

Or just https://bintray.com/testng-team/testng/testng-remote/view

missedone commented 8 years ago

im ok with this :+1:

let's clean up the rest of them

missedone commented 8 years ago

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

juherr commented 8 years ago

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

Yes! #20

missedone commented 8 years ago

it requires a sonatype account to sync jcenter to maven central:

maven_central

is there any existing account we can use?

juherr commented 8 years ago

Not yet, you can ask for a new one.

Le jeu. 7 juil. 2016 06:28, Nick Tan notifications@github.com 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 https://github.com/testng-team/testng-remote/issues/1#issuecomment-230976323, or mute the thread https://github.com/notifications/unsubscribe/AAPi6V2PckyqwRVDy2OIR3KP6-KrMJ_Kks5qTIBrgaJpZM4GZIFP .

juherr commented 7 years ago

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 commented 7 years ago

@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 commented 2 years ago

Up.

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

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

missedone commented 2 years ago

@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 commented 2 years ago

@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 commented 2 years ago

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 commented 2 years ago

@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 commented 2 years ago

is there any place we can publish the snapshot?

juherr commented 2 years ago

@missedone yes, see https://central.sonatype.org/publish/publish-maven/#other-prerequisites and https://central.sonatype.org/publish/publish-guide/#accessing-repositories