From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <ci-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id F169D4399D; Mon, 22 Jan 2024 20:32:38 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E9BE8402C9; Mon, 22 Jan 2024 20:32:38 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id C425D40298 for <ci@dpdk.org>; Mon, 22 Jan 2024 20:32:36 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1705951956; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=e++XeMrINwcgD4Zuxunz9Z76HYhII6+SvexINwHNztk=; b=QLFwudrkRCQFhq46fkVm8nI2gJjnxklRpogqt0ewlpIZOn03dJ/IlFvnpZBvR3lCWi4QAh vuxNaaiKiLq1BwnryB1szmKIw9P5OKIvyUKTA5dvtf5cXlrfJROy+WAaDzCSbMKdJ9h45I T+nnks3frh7RVL4fEf41tECASIBW/t8= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-387-4LlC9FsPO_OOFwXJ1UrZaQ-1; Mon, 22 Jan 2024 14:32:33 -0500 X-MC-Unique: 4LlC9FsPO_OOFwXJ1UrZaQ-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id C6170101A526; Mon, 22 Jan 2024 19:32:32 +0000 (UTC) Received: from RHTPC1VM0NT.redhat.com (unknown [10.22.33.141]) by smtp.corp.redhat.com (Postfix) with ESMTP id 8EECF492BC7; Mon, 22 Jan 2024 19:32:32 +0000 (UTC) From: Aaron Conole <aconole@redhat.com> To: ci@dpdk.org Cc: Michael Santana <msantana@redhat.com>, Ilya Maximets <i.maximets@ovn.org>, Jeremy Kerr <jk@ozlabs.org> Subject: [PATCH v2 0/2] Reduced checks API usage Date: Mon, 22 Jan 2024 14:32:30 -0500 Message-ID: <20240122193232.3734371-1-aconole@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.9 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions <ci.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/ci>, <mailto:ci-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/ci/> List-Post: <mailto:ci@dpdk.org> List-Help: <mailto:ci-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/ci>, <mailto:ci-request@dpdk.org?subject=subscribe> Errors-To: ci-bounces@dpdk.org As Jeremy Kerr reports, we aren't being as nice as we should be w.r.t. API usage - especially around the checks API reporting. While the initial version *worked* for what we wanted, we are heavily using the checks API, especially when we don't need to be. This series should reduce the number of API calls we make into patchwork with respect to the checks API specifically. Additionally, we add a simple token to identify that the requests coming in are from a patchwork robot project (so at least a site admin can start identifying who is actually sending the requests). Aaron Conole (2): treewide: Add a User Agent for CURL requests post_pw: Store submitted checks locally as well ci_mon | 2 +- github_get_logs.sh | 8 ++++---- github_mon | 2 +- github_restart | 6 ++++-- jenkins_lib.sh | 5 +++-- post_pw.sh | 46 +++++++++++++++++++++++++++++++++++++++++----- pw_mon | 14 +++++++------- series_db_lib.sh | 25 +++++++++++++++++++++++++ 8 files changed, 86 insertions(+), 22 deletions(-) -- 2.41.0