There's basically 3 ways I could see addressing the Jenkins builds;
1. Install the Jenkins badge plugin (
https://wiki.jenkins.io/display/JENKINS/Embeddable+Build+Status+Plugin).
2. Migrate them to a SaaS provider like Travis or Circle.
3. Write a mapper that consumes the CC tray feed and outputs badges (
https://build.clojure.org/cc.xml?recursive).
Given the limited bandwidth of the Cognitect folks 3 seems the most likely
immediate solution. SaaS CI services provide CC Tray feeds (
https://api.travis-ci.org/repos/boot-clj/boot/cc.xml?branch=master) so
using them as an aggregation method could be useful for 10s to 100s of
projects. It lacks the commit revision but does have time and status which
would be an incremental improvement over reams of pages with red and green
badges. The SaaS providers provide aggregates up to the org level so I
would want to use that for some of the more prolific Clojure community
authors. That being said I don't see cc tray feeds as a scalable solution
for all known libraries;
a) it's dependent on author discipline in keeping a given branch green.
b) it'll be a lot of potential requests to the SaaS providers and I'd like
to be a good netizen.
c) it's not a great way to isolate if a build broke due to a change in a
Clojure SNAPSHOT.
d) it requires community authors to "buy-in" to creating a periodic build
against SNAPSHOT.
Another approach I'm considering is using the org I created to host "sample
projects" that can be community owned with periodic builds that exercise an
"app" with common libraries and plugins against the latest Clojure SNAPSHOT
builds. Something similar to how TechEmpower Web Framework Benchmarks has a
number of authors submit a subproject to the repo (
https://github.com/TechEmpower/FrameworkBenchmarks). I plan to be fairly
liberal in delegating admin access to the org to minimise bottlenecks and
hopefully through that we could get good coverage that doesn't put too much
demand on any one person.
On Sat, 28 Jul 2018 at 21:44 Sean Corfield wrote:
> Have you had any thoughts about incorporating Clojure Contrib projects?
> They all have JVM/Clojure version grids as part of their Jenkins CI builds
> but there isn’t a badge you could link to (although you could link to the
> CI matrix page for each of them). They’re all tested against 1.9 / 1.10 and
> several are tested against earlier versions too. E.g.,
>
>
>
> https://build.clojure.org/job/core.cache-test-matrix/
>
> https://build.clojure.org/job/data.priority-map-test-matrix/
>
> https://build.clojure.org/job/java.jdbc-test-matrix/
>
>
>
> Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
> An Architect's View -- http://corfield.org/
>
> "If you're not annoying somebody, you're not really alive."
> -- Margaret Atwood
>
>
> *From:* clojure@googlegroups.com on behalf of
> Nathan Fisher
> *Sent:* Saturday, July 28, 2018 4:11:13 PM
> *To:* clojure@googlegroups.com
> *Subject:* Re: Rusts Upgrades
>
> Hi Sean,
>
> It would be great if there was a general report that we could integrate
> with Lein, Boot and anything else people happen to be using.
>
> I think for an MVP having folks update the status of their project
> manually as it is verified might not be a bad first step.
>
> To that end I've created a Github page site here;
>
> - https://clojurestatus.github.io/dashboard/
> - https://github.com/ClojureStatus/dashboard
>
> I know it won't scale well to all the projects out there but if we can get
> some of the major ones I think it could be useful. It'll probably need some
> thought about how to improve the aggregate view, date of last build, etc.
>
> Cheers,
> Nathan
>
> On Sat, 28 Jul 2018 at 19:50 Sean Corfield wrote:
>
>> I suspect quite a few Travis-enabled Clojure projects do full
>> multi-version testing – but it’s hard to tell at a glance from Travis’s
>> logs. For example, both HoneySQL and clj-time perform multi-version testing
>> on Travis, but they do it through Leiningen aliases so there’s only one
>> “build” – no grid of Clojure versions. I’d be interested in hearing of
>> techniques to surface a grid of Clojure versions being tested on Travis.
>>
>>
>>
>> Note that clj-time is tested against a grid of JVM versions and that does
>> surface on Travis – and I’ve just noticed that testing against Clojure
>> master on OpenJDK 7 fails, presumably because Clojure master now requires
>> Java 8? (but the Oracle JDK 7 build on Travis doesn’t fail).
>>
>>
>>
>> Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
>> An Architect's View -- http://corfield.org/
>>
>> "If you're not annoying somebody, you're not really alive."
>> -- Margaret Atwood
>>
>>
>> --
>> *From:* clojure@googlegroups.com on behalf of
>> Nathan Fisher
>> *Sent:* Friday, July 27, 2018 4:11:05 PM
>> *To:* clojure@googlegroups.com
>> *Subject:* Rusts Upgrades
>>
>> Hi Folks,
>>
>> Reading up the recent blog post “What is Rust 2018” and happened upon
>> this;
>>
>> “We put in a lot of work to make
