10x for your reply. It seems that it took just about a day. https://wiki.jenkins-ci.org/display/JENKINS/BlazeMeter+Plugin
May I ask for a bit more direction? How do I make the wiki show the link to the .hpi itself so that people won't have to compile the code for themselves? Do I have to link to it directly, or can I somehow add it to the template of the plugin info? I see no other reason to release the plugin. I can just commit to github, and the most up to date version will be there. Can someone elaborate? Thanks again, Doron. On Monday, September 24, 2012 3:52:30 PM UTC+2, Robert Sandell wrote: > > It takes a day or so for the update center backend to scan through the > repository and update itself. > But it also only checks a specific set of namespaces; like > org/jenkins-ci/plugins > and some others.Probably an admin needs to add “com/blazemeter” to the > list of groups to scan. > > * * > > *Robert Sandell* > > Software Tools Engineer - Tools and Integration > > Sony Mobile Communications > > > > *From:* jenkin...@googlegroups.com <javascript:> [mailto: > jenkin...@googlegroups.com <javascript:>] *On Behalf Of *Doron Bloch > *Sent:* den 24 september 2012 09:34 > *To:* jenkin...@googlegroups.com <javascript:> > *Subject:* Help releasing plugin > > > > I've unsuccessfully tried to release our plugin. > > The release:prepare release:perform, seemed to go well, but I can't see > the update in either of the sites mentioned or the > json<https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins> > . > > > > The output of the release says it was uploaded to: > http://maven.jenkins-ci.org:8081/content/repositories/releases/com/blazemeter/plugins/BlazeMeterJenkinsPlugin/ > And > I can see it there. > > Will it move from there to the download center? > > > > If you need to see the output of the command, just tell me. > > > > 10x in advance, > > Doron. >
