The plugin seems to be appearing on several of the mirrors, in the
regular update centre JSON.

Was the wiki page for this plugin always a child of the "Plugins" wiki
page?  It seems like it was, but the update centre generator was
complaining about this for a while.  Though looking through the past few
days of update centre logs didn't reveal anything strange.

But it seems like it should start appearing now.

Regards,
Chris


On 31/08/15 19:29, John Zeller wrote:
> Yeah, I noticed all those same things :/
> 
> To release 0.1.1, I used the command `mvn release:prepare
> release:perform`. Perhaps there is something awry in our pom.xml
> <https://github.com/jenkinsci/datadog-plugin/blob/master/pom.xml>? I too
> am new to plugin development, but it seems like I reproduced all the
> steps mentioned in the Hosting Plugins
> <https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins> wiki
> 
> On Monday, August 31, 2015 at 1:23:02 PM UTC-4, R Tyler Croy wrote:
> 
>     (replies inline)
> 
>     On Mon, 31 Aug 2015, John Zeller wrote:
> 
>     > I tried to release our
>     (https://github.com/jenkinsci/datadog-plugin
>     <https://github.com/jenkinsci/datadog-plugin>) new
>     > plugin (version 0.1.1) on Friday, and I am still not seeing it in the
>     > Update Center, or the `update-center.json`. However, it does show
>     up in the
>     > maven release repo... Our artifact ID is `datadog-build-reporter`.
>     >
>     > Does anyone have any idea what may have gone wrong here?
> 
> 
>     The update center generation appears to be working fine from the
>     infrastructure
>     side of things.
> 
>     I also see the artifact in updates.jenkins-ci.org
>     <http://updates.jenkins-ci.org> fwiw.
> 
> 
> 
>     I see the datadog-build-reporter in the stable (LTS) update-center.json
>     (http://ftp-nyc.osuosl.org/pub/jenkins/updates/stable/update-center.json
>     <http://ftp-nyc.osuosl.org/pub/jenkins/updates/stable/update-center.json>)
>     but
>     not in the "normal" update-center.json. I'm not familiar enough with
>     the
>     current means of plugin deployment so perhaps you may have
>     inadvertently only
>     released it for LTS users?
> 
>     Cheers
>     - R. Tyler Croy
> 
>     ------------------------------------------------------
>          Code: <https://github.com/rtyler>
>       Chatter: <https://twitter.com/agentdero>
> 
>       % gpg --keyserver keys.gnupg.net <http://keys.gnupg.net>
>     --recv-key 3F51E16F
>     ------------------------------------------------------
> 
> -- 
> 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 [email protected]
> <mailto:[email protected]>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/3dc83451-10eb-4a2e-ad19-77c581120132%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/3dc83451-10eb-4a2e-ad19-77c581120132%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55E4A31F.7080002%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Reply via email to