Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-dev] [equinox-dev] Perform Freeze Periode Verification as dedicated GitHub workflow
  • From: Sravan K Lakkimsetti <sravankumarl@xxxxxxxxxx>
  • Date: Tue, 5 Apr 2022 03:28:14 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=in.ibm.com; dmarc=pass action=none header.from=in.ibm.com; dkim=pass header.d=in.ibm.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=ON3aC1pKFJIEPFoInKQIniNHHcJxaM31AYUPPHDpWhk=; b=KvwuDrgfIX1ak5VXqW24ePRxe8RcGqOjfWTazJZy4G8xrPhTVhCIxeF586ENJvyO+r0cRnqLniAX7qDrTyu6v4JBZA1WoPAAmpWNdkw+J7vKp8n9FvVb0zJGVguPXhpFXgBvWq8PSqgjnPZjB6F3ut0QHQj0RpooT25vJxSOP6Vy1j8HZiEcpTfqtrzCp8TeVPZG2NwHK770ftG6/wCtGMtSDOMWROhtSpvfS/c6onXFaccVPOtLVTE2VKxeRQCYsmfj4HcHQL+OkD9ragu2hCkRZfxbi2WhnjGIZMLATtrRiS7PWazNAES401n6v5K0LAv0t8nIOebITisLpld84w==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YWyyZOrOO8udX1p+DA3xkZJELMQqZ3rmQuve3t82aXePg0ywYS2K/dFBcEKhlvzrKBbFbMkYHnZpQlYRpFF0df0LYaek+ovdVLgvFKchWC3vV5fWBDXOhs2doAq6HI2sN+Tz1vnzHVAeufFfcx+DcpjUZA/1cxBk7L1VVrjOws7UJEixkrDnwRVsUjvFRdNwepWrR+sTT6pvo1WruazwCq6kwEx7VI+XMUaxwrX93rAcdjZHQ1zlFhrUCWVmDL6qFscYn1TWzoWayVPX8L/ptNMCrS5VgCAYgFX77eCdOoqqyLjNSevGSIrFe6u0PDj6K6HVqvGSfETTtRcdx5MqzA==
  • Delivered-to: platform-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/platform-dev/>
  • List-help: <mailto:platform-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/platform-dev>, <mailto:platform-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/platform-dev>, <mailto:platform-dev-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHYSFXsyGNuViqdc0ef7wgcOBMzBKzgqK7A
  • Thread-topic: [EXTERNAL] [equinox-dev] Perform Freeze Periode Verification as dedicated GitHub workflow

Hi,

 

This is a very good idea. Please go ahead with the workflow implementation in g.c/eclipse-platform/eclipse.platform.releng.

 

By the way, the calendar is publicly available. https://calendar.google.com/calendar/u/0?cid=cHJmazI2ZmRtcHJ1MW1wdGxiMDZwMGpoNHNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ you can read the calendar here

 

Thanks

Sravan

 

From: equinox-dev <equinox-dev-bounces@xxxxxxxxxxx> On Behalf Of Hannes Wellmann
Sent: 05 April 2022 00:28
To: Eclipse platform general developers list. <platform-dev@xxxxxxxxxxx>; platform-releng-dev@xxxxxxxxxxx; equinox-dev@xxxxxxxxxxx; pde-dev@xxxxxxxxxxx
Subject: [EXTERNAL] [equinox-dev] Perform Freeze Periode Verification as dedicated GitHub workflow

 

For Platform-Projects hosted on GitHub the Freeze-Period-Check for PRs is currently performed as last step of the verification build-pipeline on Jenkins. This has the disadvantage that in case the freeze period is active and the build therefore fails, the cause of the failure is not directly obvious.

 

Therefore I want to suggest to run the freeze-period-check in a dedicated GH action workflow.

The freeze-period check would then appear as separate check in the "checks-overview" of a PR.

 

The workflow could be implemented as a reusable workflow [1] that is for example defined in the g.c/eclipse-platform/eclipse.platform.releng or eclipse-platform/eclipse.platform.releng.buildtools repo. The workflow could then be called by all other Eclipse repos that have to run this check.

Because the workflow is only defined once it could also be considered to avoid the use of the "verifyfreezeperiod.sh" script and to implement the logic directly into the workflow.

 

In case the check requires credentials to log into the calendar, which at least the mentioned script does, then the secrets could be stored in GitHub's secret store at organization level ([2] and [3]).
But I actually expected the calendar could be publicly available for read.

 

If you others are interested I could set up a corresponding workflow.

 

 

 

Back to the top