You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<h3id="open-source-app-schedule">Open-Source App Schedule<aclass="headerlink" href="#open-source-app-schedule" title="Anchor link to this Header on this Page">¶</a></h3>
3927
-
<p>Each Open-Source App has a schedule for when the automatic build happens. This determines when the automatic check for certificate status happens.</p>
3928
-
<p>The times are shifted to make sure only one Open-Source app performs a <code>nuke</code> action. Any other app building later that same day will just create new signing credentials; it will not need to <code>nuke</code> all credentials. This only happens once a year, but we wanted to be sure there are no conflicts. Even if an app doesn't have automatic certificates implemented yet, they are added to the table as suggested values to use when this capability gets added. All times are <abbrtitle="Coordinated Universal Time is a time standard for civil time and time zones worldwide">UTC</abbr>. If other apps decide to add this feature, please make a pull request to LoopDocs so we can add those times to the deconfliction table.</p>
3927
+
<p>Each Open-Source App has a schedule for when the automatic build happens.</p>
3928
+
<blockquote>
3929
+
<p>The table below indicates <strong>planned</strong> minutes. They <strong>may happen at the start of the hour now</strong>, but are planned to be shifted to the indicated minute over time.</p>
<tdstyle="text-align: left;"><spantranslate="no"><abbrtitle="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></span></td>
3941
3943
<tdstyle="text-align: center;">✅</td>
3942
-
<tdstyle="text-align: center;">09:00</td>
3943
-
<tdstyle="text-align: center;">07:00</td>
3944
+
<tdstyle="text-align: center;">09:33</td>
3945
+
<tdstyle="text-align: center;">07:33</td>
3944
3946
</tr>
3945
3947
<tr>
3946
3948
<tdstyle="text-align: left;"><spantranslate="no"><abbrtitle="An app you can build to provide remote commands to `Loop` using `Nightscout`">LoopCaregiver</abbr></span></td>
3947
3949
<tdstyle="text-align: center;">✅</td>
3948
-
<tdstyle="text-align: center;">13:00</td>
3949
-
<tdstyle="text-align: center;">11:00</td>
3950
+
<tdstyle="text-align: center;">13:33</td>
3951
+
<tdstyle="text-align: center;">11:33</td>
3950
3952
</tr>
3951
3953
<tr>
3952
3954
<tdstyle="text-align: left;"><spantranslate="no"><abbrtitle="An app you can build to provide extra alarms and views of important information - can use Dexcom Share or `Nightscout` to include `Loop` information">LoopFollow</abbr></span></td>
<pclass="admonition-title">Why are the Hour and Minute staggered?</p>
3987
+
<p>There are 2 reasons:</p>
3988
+
<ol>
3989
+
<li>You only want one action to <code>nuke</code> profiles and build credentials associated with an expired certificate</li>
3990
+
<li>The <em><abbrtitle="an online service for storing repositories, accessible from a browser">GitHub</abbr></em> resources are more likely to be busy at the beginning of each hour</li>
3991
+
</ol>
3992
+
<detailsclass="abstract">
3993
+
<summary>Do you want to know more? (Click to Open/Close)</summary>
3994
+
<p>This build schedule determines when the automatic check for certificate status happens. The times are shifted to make sure only one Open-Source app performs a <code>nuke</code> action. Any other app building later that same day will just create new signing credentials; it will not need to <code>nuke</code>. This only happens once a year, but we wanted to be sure there are no conflicts. </p>
3995
+
<p>Starting in 2025 May, some people were getting messages that "no runners" were available to perform their build. (Remember, this is a <strong>free</strong> service we are using.)
3996
+
Initially, all builds started at the "top of the hour" (HH:00), but it turns out that is when <em><abbrtitle="an online service for storing repositories, accessible from a browser">GitHub</abbr></em> has the most activity.
3997
+
In an attempt to minimize build failures due to resource limitations, the minute of the hour for all the apps is gradually being shifted.</p>
3998
+
</details>
3999
+
</div>
4000
+
<p>Even if an app doesn't have automatic certificates implemented yet, they are added to the table as suggested values to use when this capability gets added. All times are <abbrtitle="Coordinated Universal Time is a time standard for civil time and time zones worldwide">UTC</abbr>. If other apps decide to add this feature, please make a pull request to LoopDocs so we can add those times to the deconfliction table.</p>
3983
4001
<h2id="modify-automatic-building">Modify Automatic Building<aclass="headerlink" href="#modify-automatic-building" title="Anchor link to this Header on this Page">¶</a></h2>
3984
4002
<p>For someone using <ahref="../build-dev-browser/">development code</a> for their own use, they could decide to choose when to update their <code>fork</code> to the most recent <abbrtitle="a formal change to files in a repository; each commit has an alphanumeric identifier (SHA-1)">commit</abbr>. They can still have the advantage of automatic building without automatic updates; in other words, they want a new build added to <abbrtitle="a method to distribute apps without direct connection">TestFlight</abbr> every month. There may be other configurations someone would choose. These options are available starting with <abbrtitle="Latest release with major updates">Loop 3</abbr>.3.0 (<code>dev</code><abbrtitle="version of code within a single repository or workspace repository">branch</abbr>) and later.</p>
0 commit comments