Hi Alex,
I don't think it would be necessary to scrape the Jenkins server too often.
I speculate daily would be enough, hourly at most.
Cheers,
Nathan
On Sun, 29 Jul 2018 at 03:42 Alex Miller wrote:
> On contribs, I just added the emeddable build status plugin - that’s easy.
> Migrating to
On contribs, I just added the emeddable build status plugin - that’s easy.
Migrating to Travis or Circle is not really a viable option based on my last
research on this. I’d be a little worried about adding a lot of traffic that
parsed the feeds. The box running Jenkins is already underpowered
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
