GSoC 2020 Jenkins Custom Distribution Service Update Center Persistence Discussion

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

GSoC 2020 Jenkins Custom Distribution Service Update Center Persistence Discussion

Sladyn Nunes
Hi all, 

This discussion thread pertains to the [GSoC 2020]  Custom Distribution Service Project feature implementation decision that the GsoC team would like feedback on. Basically the problem right now is that the update center.json is quite a big file and making an api call to it takes a minimum of 30 seconds, therefore we would like to know out of the below two designs which one would users prefer:

a) We download the update-center.json and store it in a temporary folder, every time the service is started and thus for the entire duration of the running of the service we would be able to make use of this file. On exit or shutdown of this service the temporary folder is deleted.

b) We persist the update-center.json and store it only when the service is started for the first time and on every subsequent run thereafter we would not make any api call. Instead we would provide the user with a button on the UI saying that "Hey the update center has not been updated for x amount of time would you like to pull in the latest changes"

Would love to get some feedback on this thread

Thanks and Cheers

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1bf950ef-edee-47c6-bbdd-a95566778891o%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: GSoC 2020 Jenkins Custom Distribution Service Update Center Persistence Discussion

Tim Jacomb
Could you have a background job that updates it every hour?

On Thu, 23 Jul 2020 at 19:35, Sladyn Nunes <[hidden email]> wrote:
Hi all, 

This discussion thread pertains to the [GSoC 2020]  Custom Distribution Service Project feature implementation decision that the GsoC team would like feedback on. Basically the problem right now is that the update center.json is quite a big file and making an api call to it takes a minimum of 30 seconds, therefore we would like to know out of the below two designs which one would users prefer:

a) We download the update-center.json and store it in a temporary folder, every time the service is started and thus for the entire duration of the running of the service we would be able to make use of this file. On exit or shutdown of this service the temporary folder is deleted.

b) We persist the update-center.json and store it only when the service is started for the first time and on every subsequent run thereafter we would not make any api call. Instead we would provide the user with a button on the UI saying that "Hey the update center has not been updated for x amount of time would you like to pull in the latest changes"

Would love to get some feedback on this thread

Thanks and Cheers

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1bf950ef-edee-47c6-bbdd-a95566778891o%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BienkmakyNsofM15uszM-EgbSdjPGnZNyXqLd6R74%3De4ig%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: GSoC 2020 Jenkins Custom Distribution Service Update Center Persistence Discussion

Martin d'Anjou
Hi Tim,

I see two use cases: an on-line community service, and behind a firewall. We're just not sure whether the update centre data should be 1) persistent when the service is stopped and restarted  (thus we need a persistent docker volume along with the two docker containers), or 2) downloaded every time it starts.

For the hourly update, that can work on top of either one.

Maybe I am complicating something that is simple.

Martin

On Thursday, July 23, 2020 at 2:36:54 PM UTC-4, Tim Jacomb wrote:
Could you have a background job that updates it every hour?

On Thu, 23 Jul 2020 at 19:35, Sladyn Nunes <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="JAMJij-rCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">sladyn...@...> wrote:
Hi all, 

This discussion thread pertains to the [GSoC 2020]  Custom Distribution Service Project feature implementation decision that the GsoC team would like feedback on. Basically the problem right now is that the update center.json is quite a big file and making an api call to it takes a minimum of 30 seconds, therefore we would like to know out of the below two designs which one would users prefer:

a) We download the update-center.json and store it in a temporary folder, every time the service is started and thus for the entire duration of the running of the service we would be able to make use of this file. On exit or shutdown of this service the temporary folder is deleted.

b) We persist the update-center.json and store it only when the service is started for the first time and on every subsequent run thereafter we would not make any api call. Instead we would provide the user with a button on the UI saying that "Hey the update center has not been updated for x amount of time would you like to pull in the latest changes"

Would love to get some feedback on this thread

Thanks and Cheers

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="JAMJij-rCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/1bf950ef-edee-47c6-bbdd-a95566778891o%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/1bf950ef-edee-47c6-bbdd-a95566778891o%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/1bf950ef-edee-47c6-bbdd-a95566778891o%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/1bf950ef-edee-47c6-bbdd-a95566778891o%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f2a4ec44-30f6-4b18-a7bf-e893f5988547o%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: GSoC 2020 Jenkins Custom Distribution Service Update Center Persistence Discussion

Richard Bywater-3
If the update centre data isn't persisted then if the service restarts then you are relying on external infrastructure being available in order to serve your own infrastructure. This seems to be not the best idea so personally I'd do a bit of both - that is, persist the results but on service start trigger a background job to go and refresh the update centre data. This background refresh is then what can be re-used to keep the data up-to-date over time while the service is running.

Richard.

On Mon, 27 Jul 2020 at 09:23, martinda <[hidden email]> wrote:
Hi Tim,

I see two use cases: an on-line community service, and behind a firewall. We're just not sure whether the update centre data should be 1) persistent when the service is stopped and restarted  (thus we need a persistent docker volume along with the two docker containers), or 2) downloaded every time it starts.

For the hourly update, that can work on top of either one.

Maybe I am complicating something that is simple.

Martin

On Thursday, July 23, 2020 at 2:36:54 PM UTC-4, Tim Jacomb wrote:
Could you have a background job that updates it every hour?

On Thu, 23 Jul 2020 at 19:35, Sladyn Nunes <[hidden email]> wrote:
Hi all, 

This discussion thread pertains to the [GSoC 2020]  Custom Distribution Service Project feature implementation decision that the GsoC team would like feedback on. Basically the problem right now is that the update center.json is quite a big file and making an api call to it takes a minimum of 30 seconds, therefore we would like to know out of the below two designs which one would users prefer:

a) We download the update-center.json and store it in a temporary folder, every time the service is started and thus for the entire duration of the running of the service we would be able to make use of this file. On exit or shutdown of this service the temporary folder is deleted.

b) We persist the update-center.json and store it only when the service is started for the first time and on every subsequent run thereafter we would not make any api call. Instead we would provide the user with a button on the UI saying that "Hey the update center has not been updated for x amount of time would you like to pull in the latest changes"

Would love to get some feedback on this thread

Thanks and Cheers

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1bf950ef-edee-47c6-bbdd-a95566778891o%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f2a4ec44-30f6-4b18-a7bf-e893f5988547o%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwctnpV-1BQr1UBrHGYTmDX_18Wfcq2KFDqD1O-dMYsXQQ%40mail.gmail.com.