[Jenkins-infra] plugins.jenkins.io Static site deployment

Gavin Mogan gavin at gavinmogan.com
Wed Jan 8 09:59:39 UTC 2020


So really we are only blocked by the deployment plan.

I have helm charts ready. I have the docker images ready. It just needs to
be merge and Cron triggered.

I still think the docker image isn't going to work well cause it'll deploy
a new image every couple hours which we need to update.

Keen (https://github.com/keel-hq/keel/blob/master/readme.md) seems like the
easiest solution, especially if we switch the docker hub tags to semver
instead of $id-hash

Or if trusted can commit to GitHub, as part of the job I can make it pull
down charts. Commit a change and push.

Or if trusted has access to kubectl, I could just update the image field.

Or original suggestion of azure blob / netlify.

I can do the work I just need people with actual access to make decisions.

Gavin

On Mon., Jan. 6, 2020, 9:04 p.m. Tim Jacomb, <timjacomb1 at gmail.com> wrote:

> Looks like at least for December the pluginsite was well under the free
> bandwidth of 100GB offered by netlify
>
> Also note that the Jenkins project qualifies for the pro plan for free
> under the open source offering which provides 400gb of bandwidth
>
> https://www.netlify.com/legal/open-source-policy/
>
> https://www.netlify.com/pricing/#teams
>
> It would be good to try out a CDN imo, our users across the globe should
> benefit from it rather than us just serving from one location
>
> Tim
>
> On Thu, 2 Jan 2020 at 14:08, Olblak <me at olblak.com> wrote:
>
>> As some of you might know, i've been poking at making a static version of
>> plugins.jenkins.io like jenkins.io, that just gets rebuilt periodically
>> (PR @ https://github.com/jenkins-infra/plugin-site/pull/76), Its pretty
>> much done, just needs jenkinsfile/deployment tweaking.
>>
>>
>> That's really great to hear
>>
>> all) add plugins-api.jenkins.io to the current helm chart
>>
>> What's wrong to keep plugins.jenkins.io/api/? we just have to forward to
>> a different docker container
>>
>> 1) Update the helm chart, manually or automatically, every build of the
>> site content
>>
>> Why not if the helm chart is automatically updated, I can finalize a
>> small tool to do it.
>>
>> 2) Upload the content to azure blob storage like jenkins.io
>>
>>
>> Do you have an idea of how often that content will be generated? Once per
>> hour?
>> Azure Storage makes more sense to me, as we already have a process and
>> billing information in place.
>>
>> To give you an idea
>> jenkinsio storage for december 2019 -> 217$
>> javadoc storage for december 2019 -> 17$
>>
>> plugins.jenkins.io traffic seems to be one third of jenkins.io
>>
>> And here a screenshot of jenkinsio storage traffic over December 2019
>>
>>
>> 3) If desired to reduce Azure dependencies, netlify is what I use for the
>> demo site, its pretty easy, and they have a free tier for open source
>> projects - pro with unlimited users -
>> https://www.netlify.com/legal/open-source-policy/
>>
>>
>> At the moment I have some concerned about bringing a new SAAS account in
>> the infrastructure as It implies some billing information, and the free
>> tier CDN bandwidth will be quickly consumed.
>>
>>
>> ---
>> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
>> ---
>>
>>
>> On Sat, Dec 28, 2019, at 7:04 AM, Gavin Mogan wrote:
>>
>> Hey ya'll,
>>
>> As some of you might know, i've been poking at making a static version of
>> plugins.jenkins.io like jenkins.io, that just gets rebuilt periodically
>> (PR @ https://github.com/jenkins-infra/plugin-site/pull/76), Its pretty
>> much done, just needs jenkinsfile/deployment tweaking.
>>
>> I started to create a PR to update the helm chart to split the backend
>> image (/api) and the frontend image (/) into two different docker images.
>> This was supposed to be short term until a new CDN style deployment. About
>> 5 minutes into this PR, I realized it'll be a pain if the content is
>> generated through cron.
>>
>> So, options
>>
>> all) add plugins-api.jenkins.io to the current helm chart
>>
>> 1) Update the helm chart, manually or automatically, every build of the
>> site content
>> 2) Upload the content to azure blob storage like jenkins.io (See
>> https://github.com/jenkins-infra/jenkins.io/blob/a7cf4218dba77ab07e4e4ef691d5142e986a4949/Jenkinsfile#L94-L101
>> )
>> 3) If desired to reduce Azure dependencies, netlify is what I use for the
>> demo site, its pretty easy, and they have a free tier for open source
>> projects - pro with unlimited users -
>> https://www.netlify.com/legal/open-source-policy/
>>
>> I think 1 is really gross and don't want to do it.
>>
>> But looking for more ideas/feedback.
>>
>> Gavin
>> _______________________________________________
>> Jenkins-infra mailing list
>> Jenkins-infra at lists.jenkins-ci.org
>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>>
>>
>> _______________________________________________
>> Jenkins-infra mailing list
>> Jenkins-infra at lists.jenkins-ci.org
>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>>
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20200108/808e686d/attachment-0001.html>


More information about the Jenkins-infra mailing list