Project

General

Profile

Actions

action #123661

closed

Use non-personal or in-team tokens for openQA OBS CI integration size:M

Added by okurz over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Feature requests
Target version:
Start date:
2023-01-25
Due date:
% Done:

0%

Estimated time:

Description

Motivation

coolo noticed that there are some obs packages that use his token for CI integration:

<entry id="12" string="L8QrNuC50kjUlZWQmD4+mMAYApbF9w2sgXOEHvdj" kind="service" description="" triggered_at="2023-01-23 16:23:23 UTC" project="devel:openQA" package="openQA"/>
<entry id="3046" string="THZ7YadHSbAa5Kwg5Jy4ud3w" kind="service" description="" triggered_at="2023-01-23 16:23:23 UTC" project="devel:openQA" package="openqa_dev"/>
<entry id="3055" string="pqpAr26bZQGTo2TwyPLJX5VV" kind="service" description="" triggered_at="2023-01-23 16:23:23 UTC" project="devel:openqa:ci" package="base"/>
<entry id="3058" string="nSiTjKwRQzWn3umDvBx8C4Vc" kind="service" description="" triggered_at="2023-01-23 16:23:22 UTC" project="devel:openqa:ci" package="dependency_bot"/>

We should switch to non-personal or in-team tokens like we already do with os-autoinst using a token and account from okurz. It might be desired to use a person in changelogs, not a bot-account.

Acceptance criteria

  • AC1: no token owned by coolo is used

Suggestions


Related issues 1 (0 open1 closed)

Related to openQA Project - action #123867: [sporadic][ci] circleCI job "build-docs-nightly" failedResolvedtinita2023-02-01

Actions
Actions

Also available in: Atom PDF