Re: Release not showing up
The best place to post issues and see issues for infrastructure is here: https://issues.jenkins.io/projects/INFRA On Friday, January 25, 2019 at 7:41:59 AM UTC+1, Steve Springett wrote: > > Hello, > > I released a new version of the OWASP Dependency-Track plugin yesterday, > but it still hasn’t shown up on the update site. The version in question > is 2.1.0. > > > https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/dependency-track/2.1.0/ > > https://updates.jenkins.io/download/plugins/dependency-track/ > > Anything I need to do to make this available? > > —Steve > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/95337a3b-f9f7-438f-b7da-dbfa9e15e31b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Release not showing up
Hello, i'm experiencing the same problem. I released a new version of the Performance-Signature-* plugins but it still hasn't shown up on the update center. The release is available via repo.jenkins-ci.org: https://repo.jenkins-ci.org/releases/de/tsystems/mms/apm/performance-signature-dynatracesaas/3.1.0/ And the update-center was last updated at 2019-01-22 21:18: https://updates.jenkins.io/ Raphael Am Freitag, 25. Januar 2019 07:41:59 UTC+1 schrieb Steve Springett: > > Hello, > > I released a new version of the OWASP Dependency-Track plugin yesterday, > but it still hasn’t shown up on the update site. The version in question > is 2.1.0. > > > https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/dependency-track/2.1.0/ > > https://updates.jenkins.io/download/plugins/dependency-track/ > > Anything I need to do to make this available? > > —Steve > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4b3df278-3d56-4ae1-903a-bc56cb3fbbc0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Release not showing up
Hello, I released a new version of the OWASP Dependency-Track plugin yesterday, but it still hasn’t shown up on the update site. The version in question is 2.1.0. https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/dependency-track/2.1.0/ https://updates.jenkins.io/download/plugins/dependency-track/ Anything I need to do to make this available? —Steve -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CABRTs2zua2cy_5Zwbm8t-9HhYzqpn0WXW%3Dg1u4v%2Bq%3DrCKrWmbQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Release not showing up + repo questions
Am 05.08.2013 um 01:28 schrieb steve.spring...@owasp.org: Hello all. I'm new to releasing on jenkins-ci.org so this may be a newbie mistake. I've successfully ran 'mvn release:prepare release:perform', but the plugin does not appear in http://repo.jenkins-ci.org/releases/org/jvnet/hudson/plugins/ or http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ However, it is showing up here: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/owasp/dependency-check/dependency-check-jenkins-plugin/1.0.1/ Repo: https://github.com/jeremylong/dependency-check-jenkins Forked: https://github.com/jenkinsci/dependency-check-plugin Github ID: stevespringett What am I doing wrong? You need to change your group ID in your pom from groupIdorg.owasp.dependency-check/groupId to groupIdorg.jenkins-ci.plugins/groupId Also, what is the relationship between the original repo (which I commit to), the forked repo (not exactly sure why it's there), and the release that I upload (built from the original repo)? I've made changes to the original repo, but the changes are not showing up in forked repo. So I guess I need a pull request? What purpose does this actually serve if the plugin I'm building and uploading is being built from the original repo? Since you are the owner of the plug-in you should continue your work in the forked repository now (jenkinsci). Pull requests are only for other developers who would like to submit changes to your plug-in. So it is important that the plugin below jenkinsci is up to date so that others see the latest changes. (You can keep the original repository up to date but this is not really required. Actually I'm not sure if you need the original repository anymore…) Ulli Thanks in advance --Steve -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Release not showing up + repo questions
Thanks Ulli. I made the change to the groupId and it appears to have been published. Also, thanks very much for the clarification on the use of repos, etc. Very much appreciated. BTW, I added OWASP Dependency-Check to the analysis-core wiki page. --Steve On Mon, Aug 5, 2013 at 2:02 AM, Ulli Hafner ullrich.haf...@gmail.comwrote: Am 05.08.2013 um 01:28 schrieb steve.spring...@owasp.org: Hello all. I'm new to releasing on jenkins-ci.org so this may be a newbie mistake. I've successfully ran 'mvn release:prepare release:perform', but the plugin does not appear in http://repo.jenkins-ci.org/releases/org/jvnet/hudson/plugins/ or http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ However, it is showing up here: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/owasp/dependency-check/dependency-check-jenkins-plugin/1.0.1/ Repo: https://github.com/jeremylong/dependency-check-jenkins Forked: https://github.com/jenkinsci/dependency-check-plugin Github ID: stevespringett What am I doing wrong? You need to change your group ID in your pom from groupIdorg.owasp.dependency-check/groupId to groupIdorg.jenkins-ci.plugins/groupId Also, what is the relationship between the original repo (which I commit to), the forked repo (not exactly sure why it's there), and the release that I upload (built from the original repo)? I've made changes to the original repo, but the changes are not showing up in forked repo. So I guess I need a pull request? What purpose does this actually serve if the plugin I'm building and uploading is being built from the original repo? Since you are the owner of the plug-in you should continue your work in the forked repository now (jenkinsci). Pull requests are only for other developers who would like to submit changes to your plug-in. So it is important that the plugin below jenkinsci is up to date so that others see the latest changes. (You can keep the original repository up to date but this is not really required. Actually I'm not sure if you need the original repository anymore…) Ulli Thanks in advance --Steve -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Release not showing up + repo questions
Hello all. I'm new to releasing on jenkins-ci.org so this may be a newbie mistake. I've successfully ran 'mvn release:prepare release:perform', but the plugin does not appear in http://repo.jenkins-ci.org/releases/org/jvnet/hudson/plugins/ or http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ However, it is showing up here: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/owasp/dependency-check/dependency-check-jenkins-plugin/1.0.1/ Repo: https://github.com/jeremylong/dependency-check-jenkins Forked: https://github.com/jenkinsci/dependency-check-plugin Github ID: stevespringett What am I doing wrong? Also, what is the relationship between the original repo (which I commit to), the forked repo (not exactly sure why it's there), and the release that I upload (built from the original repo)? I've made changes to the original repo, but the changes are not showing up in forked repo. So I guess I need a pull request? What purpose does this actually serve if the plugin I'm building and uploading is being built from the original repo? Thanks in advance --Steve -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
