UNH CI is offline

[Lincoln Lavoie]

Hello All,

Just a quick follow up. Jenkins upgrades have been completed and the system
is getting caught up to the patches that have come in. Please let us know
if you would like any patches rerun.  We'll also take a pass through the
history this week to look for anything that needs to be rerun as well.

Next for upgrades will be the dashboard system and our vpn / router.  The
dashboard will not impact running just, just browsing results. The vpn /
router upgrade will require us to stop the existing jobs.  We expect both
of these to be completed this week.

Cheers,
Lincoln

On Thu, Dec 9, 2021 at 11:01 AM Thomas Monjalon <thomas at monjalon.net> wrote:

> 09/12/2021 15:33, Aaron Conole:
> > Lincoln Lavoie <lylavoie at iol.unh.edu> writes:
> > > That does raise a question on storage of historical results (i.e. the
> > > results tar balls) and how long we need to keep those available. The
> > > results (i.e. pass / fail indication) would live on in the dashboard
> and
> > > database, but the actual results archives (tar balls) are stored in
> Jenkins
> > > as a job.  Would limiting that storage to 4 or 6 months be acceptable
> to
> > > the community?  This will reduce the future issues of upgrades and
> > > migration, in terms of processing time required by Jenkins. A test
> could
> > > always be rerun, if we needed to recreate an older set of logs/results.
> > > I'll add this as a discussion item for the next community call.
> >
> > +1 - thanks.
>
> I think we don't need more history than current and previous releases.
> So I bet 8 months is a fair amount of test history.
>
>
>

-- 
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie at iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>