OpenGrok maintenance is complete

On 05/09/2018 03:01 PM, Vanessa Valderrama wrote:
>
> OpenGrok maintenance starting shortly
>
>
> On 05/09/2018 02:45 PM, Vanessa Valderrama wrote:
>>
>> JIRA maintenance will be starting shortly
>>
>>
>> On 05/08/2018 07:14 PM, Vanessa Valderrama wrote:
>>>
>>> Nexus maintenance is complete for tonight.  We'll continue cleaning
>>> out repositories tomorrow but it should be transparent.
>>>
>>> Thank you,
>>>
>>> Vanessa
>>>
>>>
>>> On 05/08/2018 11:28 AM, Vanessa Valderrama wrote:
>>>>
>>>> Jenkins is in shutdown mode to prepare for the Nexus maintenance
>>>>
>>>>
>>>> On 05/08/2018 09:18 AM, Vanessa Valderrama wrote:
>>>>>
>>>>> Sonar maintenance has been rescheduled to 2018-05-17
>>>>>
>>>>> Thank you,
>>>>> Vanessa
>>>>>
>>>>> On 05/07/2018 12:10 PM, Vanessa Valderrama wrote:
>>>>>>
>>>>>> *Reminder of upcoming maintenance*
>>>>>>
>>>>>>
>>>>>> On 04/26/2018 10:02 AM, Vanessa Valderrama wrote:
>>>>>>>
>>>>>>> Please let me know if the following maintenance schedule
>>>>>>> conflicts with your projects.
>>>>>>>
>>>>>>> *Nexus 2018-05-08 - **1700 UTC*
>>>>>>>
>>>>>>> The Nexus maintenance will require a restart of Nexus to bump up
>>>>>>> the JVM and run scheduled tasks to clean up the VPP CentOS
>>>>>>> repositories.  The size of the repositories, specifically master
>>>>>>> is causing intermittent timeouts and slowness.  There is risk in
>>>>>>> crashing the JVM when we run the scheduled tasks.
>>>>>>>
>>>>>>> *JIRA & OpenGrok AWS Migration 2018-05-09 - **2100 UTC to 0100 UTC*
>>>>>>>
>>>>>>> Services will be unavailable for approximately 2-3 hours
>>>>>>> depending on data transfer.
>>>>>>>
>>>>>>> *Gerrit 2018-05-15 - 2100 UTC to 0100 UTC*
>>>>>>>
>>>>>>> Gerrit will be unavailable for approximately 2-3 hours depending
>>>>>>> on data transfer.  Jenkins will be placed in shutdown mode 1
>>>>>>> hour prior to the start of maintenance.
>>>>>>>
>>>>>>> *Sonar 2018-05-16 - **2100 UTC to 0100 UTC*
>>>>>>>
>>>>>>> Sonar will be unavailable for approximately 2-3 hours depending
>>>>>>> on data transfer.
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to