-
Notifications
You must be signed in to change notification settings - Fork 164
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
new p2 repo to replace bintray #511
Comments
@guillaumecle , thanks for the reminder. Thanks |
No sorry, I don't have any recommendation. |
http://www.lorenzobettini.it/2021/03/publishing-an-eclipse-p2-composite-repository-on-github-pages/
the bandwidth limit might be an issue |
@missedone I think it is the best solution for, at least, the short term. 👍 |
Yeah, I think the bandwidth will be a problem. As you know, my personal
site is still hammered by requests for our old Eclipse update site to the
point that my web host refused to handle it until I put it behind
Cloudflare... And that's for a URL that's no longer used.
But yes, this is definitely what we need to do right now.
…--
Cédric
On Mon, Mar 15, 2021 at 3:02 PM Nick Tan ***@***.***> wrote:
http://www.lorenzobettini.it/2021/03/publishing-an-eclipse-p2-composite-repository-on-github-pages/
sites have a soft bandwidth limit of 100GB per month and sites have a soft
limit of 10 builds per hour
the bandwidth limit might be an issue
CC @cbeust <https:/cbeust> @juherr <https:/juherr>
@krmahadevan <https:/krmahadevan>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#511 (comment)>,
or unsubscribe
<https:/notifications/unsubscribe-auth/AAAWRITHCE2TU4SSQ6JJQFTTDZ7YVANCNFSM4ZA2Z4CQ>
.
|
@juherr @cbeust @missedone - Just a curious question. What if we moved away to making TestNG eclipse plugin available as an offline plugin that would need to be downloaded and installed in eclipse manually ? |
Definitely something we should do anyway since there are quite a few users
who can't use p2 sites for firewall or other reasons.
…--
Cédric
On Tue, Mar 16, 2021 at 10:05 PM Krishnan Mahadevan < ***@***.***> wrote:
@juherr <https:/juherr> @cbeust <https:/cbeust>
@missedone <https:/missedone> - Just a curious question. What
if we moved away to making TestNG eclipse plugin available as an offline
plugin that would need to be downloaded and installed in eclipse manually ?
That way we could publish the newer versions as releases on the github
project and then we could may have some good document with screenshots that
shows how to go about doing this, if the rate limiting on GitHub Pages is
going to be a problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#511 (comment)>,
or unsubscribe
<https:/notifications/unsubscribe-auth/AAAWRIXDPISX2I4OEWKYCT3TEA2A3ANCNFSM4ZA2Z4CQ>
.
|
we will replace the bintray repository, for now as workaround we hosted the plugin update site on github, pls use this update site url: https://testng.org/testng-eclipse-update-site i will update the README.md shortly with new URL. |
@missedone Thanks a ton, it works and you made my day. |
readme is updated to use new update site url. @cbeust , could you update the url on eclipse marketplace with |
Hi Although The new Eclipse contain the new link: https://testng.org/testng-eclipse-update-site Even if the follow the steps:
I got "Unable to read repository at https://testng.org/testng-eclipse-update-site/7.4.0/content.xml " Error I will be great full for any assist. |
@liorst99-IS it took a while for it to resolve for me. and thank you for the nice note it helped me get to the plugin |
@liorst99-IS , you may try with the specific version url: https://testng.org/testng-eclipse-update-site/7.4.0 |
… --
Cédric
On Sun, May 2, 2021 at 9:38 AM Nick Tan ***@***.***> wrote:
readme is updated to use new update site url.
@cbeust <https:/cbeust> , could you update the url on eclipse
marketplace with https://testng.org/testng-eclipse-update-site
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#511 (comment)>,
or unsubscribe
<https:/notifications/unsubscribe-auth/AAAWRIVLYPKJHZTZHB3G243TLV5YHANCNFSM4ZA2Z4CQ>
.
|
@cbeust , i see it's still old update-site: |
Hi. I work with Oxygen Release (4.7.0), It will be difficult to change the eclipse version. Is it make sense that the testNG doesn't support Oxygen Release (4.7.0)? Thanks a lot |
@liorst99-IS , since https:/cbeust/testng-eclipse/releases/tag/6.14.3.201902250526 it requires eclipse 4.8, so i'm afraid either you use one version older: https:/cbeust/testng-eclipse/releases/tag/6.14.0.201802161500 |
Really thanks a lot for all of you. For your great support. Thanks a lot |
Ah yes, there was a second Save button. I saved it but now that download
button is greyed out... Wonder if it takes a bit to update.
…--
Cédric
On Tue, May 4, 2021 at 3:51 PM Nick Tan ***@***.***> wrote:
@cbeust <https:/cbeust> , i see it's still old update-site:
[image: image]
<https://user-images.githubusercontent.com/555134/117079404-8a753e00-acf0-11eb-9406-fbe630734bdb.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#511 (comment)>,
or unsubscribe
<https:/notifications/unsubscribe-auth/AAAWRITXNV2SWDX5MMF3HILTMB27BANCNFSM4ZA2Z4CQ>
.
|
@cbeust thanks it works, just verified on a new eclipse instance. thx |
https://testng.org/testng-eclipse-update-site does not support 7.5 or 7.6. When will they be supported? |
hi @leerho , by the design we de-coupled the Eclipse Plugin and TestNG runtime, if you are asking for the TestNG runtime 7.5 and 7.6, they are available here https:/testng-team/testng-p2-update-site |
nevermind, it works as long as has automatic update enabled. |
Hi, Your original request has been modified. In location - C:\Users\shiva.p2\pool\plugins |
@ShivamPandit1213 - Please check if you have followed the below instructions https://testng.org/testng-eclipse/download |
JFrog is announcing Bintray sunset and that is where TestNG eclipse plugins are served.
A new p2 hosting service is need to replace it.
The text was updated successfully, but these errors were encountered: