Plugin releases Twitter bot source?

42 views
Skip to first unread message

Christopher Orr

unread,
Oct 20, 2015, 9:07:42 AM10/20/15
to jenkin...@googlegroups.com
Hi all,

I just saw this, which claims Log Parser 2.0 is a new plugin:
https://twitter.com/jenkins_release/status/656450179571150849

I know it's not a new plugin, and the artifactId hasn't changed, and the
Update Centre JSON looks good (i.e. we haven't accidentally released a
duplicate of the existing plugin).

So I *assume* the Twitter bot flagged it as a new release because the
*groupId* changed in the POM since the last release? It would be nice
to confirm this, but I don't know where the source code is, or where the
bot runs.

This is just out of curiosity, so it's not really important — but I find
it quite a useful resource, so it would be nice to know where it runs,
and how contributions can be made. Does anybody know? :)

Regards,
Chris

PS. If anyone knows where the JIRA SCM link daemon lives, that would
also be nice to know!

domi

unread,
Oct 20, 2015, 9:09:42 AM10/20/15
to Jenkins Developers
and by the way: it also tweet every release twice…
/Domi
> --
> 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-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/56263C96.6070605%40orr.me.uk.
> For more options, visit https://groups.google.com/d/optout.

Daniel Beck

unread,
Oct 20, 2015, 9:15:19 AM10/20/15
to jenkin...@googlegroups.com

On 20.10.2015, at 15:07, Christopher Orr <ch...@orr.me.uk> wrote:

> t would be nice
> to confirm this, but I don't know where the source code is, or where the
> bot runs.
>
> This is just out of curiosity, so it's not really important — but I find
> it quite a useful resource, so it would be nice to know where it runs,
> and how contributions can be made. Does anybody know? :)

The Twitter bot just tweets the http://jenkins-ci.org/releases.rss feed.

Which gets generated here: https://ci.jenkins-ci.org/job/infra_release.rss/
With sources here: https://github.com/jenkinsci/backend-release.rss

And that's where the group is relevant although it should not be:
https://github.com/jenkinsci/backend-release.rss/blob/master/release.rss.groovy#L24

Daniel Beck

unread,
Oct 20, 2015, 9:26:47 AM10/20/15
to jenkin...@googlegroups.com

On 20.10.2015, at 15:07, Christopher Orr <ch...@orr.me.uk> wrote:

> t would be nice
> to confirm this, but I don't know where the source code is, or where the
> bot runs.
>
> This is just out of curiosity, so it's not really important — but I find
> it quite a useful resource, so it would be nice to know where it runs,
> and how contributions can be made. Does anybody know? :)

Manuel Jesús Recena Soto

unread,
Oct 20, 2015, 9:49:08 AM10/20/15
to Jenkins Developers
Hello Christopher,

I've released this plugin this morning.

It seems the owner did that change:
https://github.com/jenkinsci/log-parser-plugin/commit/398c0efd775de2ae1d4a55f4cc9ca5f0792a7aa2

Regards,
> --
> 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-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/56263C96.6070605%40orr.me.uk.
> For more options, visit https://groups.google.com/d/optout.



--
Manuel Recena Soto
* manuelrecena.com [/blog]
* linkedin.com/in/recena

Christopher Orr

unread,
Oct 20, 2015, 10:20:01 AM10/20/15
to jenkin...@googlegroups.com
Nice, thanks.

Funnily enough, the release-history.json contains a `firstRelease` (and
`latestRelease`) flag, which seems to be generated correctly.

Regards,
Chris

Daniel Beck

unread,
Oct 20, 2015, 10:21:30 AM10/20/15
to jenkin...@googlegroups.com

On 20.10.2015, at 16:19, Christopher Orr <ch...@orr.me.uk> wrote:

> Funnily enough, the release-history.json contains a `firstRelease` (and
> `latestRelease`) flag, which seems to be generated correctly.

release-history.json is a byproduct of the update site generation and doesn't care about group identifier.

Christopher Orr

unread,
Oct 20, 2015, 10:25:27 AM10/20/15
to jenkin...@googlegroups.com
Huh, true. One post per plugin seems to come from https://dlvr.it/ and
another (very unreliably) is posted by http://twitterfeed.com/

Jesse Glick

unread,
Oct 20, 2015, 5:24:27 PM10/20/15
to Jenkins Dev
FYI, there is also a feed for plugins which appear on the CloudBees
update center (which is normally a superset of the regular Jenkins UC,
though it is generated by a different system):

https://twitter.com/jepluginrelease
Reply all
Reply to author
Forward
0 new messages