-
Notifications
You must be signed in to change notification settings - Fork 7
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
Comments
please let me know what can i do. thanks |
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
|
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]
|
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). @missedone Do you have a bintray account? |
just create one account: |
hi @juherr , @cbeust i will create a DEPLOY.md later to document the release process, |
as you might know, Bintary does not support uploading snapshot artifacts. only release bits can. |
here is the release procedure: https://github.com/testng-team/testng-remote/blob/release_to_bintray/RELEASE.md |
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? |
im ok with this 👍 let's clean up the rest of them |
later, we might need add travis-ci as well? |
Yes! #20 |
Not yet, you can ask for a new one. Le jeu. 7 juil. 2016 06:28, Nick Tan [email protected] a écrit :
|
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 |
@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 |
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 @krmahadevan not sure who can set the gpg key on this github repo secrets for the maven publish. |
@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. |
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 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. |
I didnt know this :)
LIke I mentioned earlier, I can access the page, but I don't know what values to put in there. |
is there any place we can publish the snapshot? |
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.
The text was updated successfully, but these errors were encountered: