Buildbot: Build run statuses from UATEST are shown in Gitea Production #95

New Issue

Bastien Montagne · 2024-07-25T09:54:23+02:00

Bastien Montagne commented

2024-07-25 09:54:23 +02:00

Yesterday @bartvdbraak was doing some upgrade tests in UATEST buildbot (related to #57 and #94).

When he built some PRs on the UATEST buildbot servers, these builds became listed under the PR page on gitea, overriding previous ones made on the production buildbot for the same PR.

See e.g. blender/blender!125365, which currently links to https://builder-uatest.blender.org/admin/#/builders/22/builds/71

I would not expect any such connection between production gitea and UATEST buildbot. If this cannot be avoided, then using production gitea with UATEST buildbot should probably be avoided?

Yesterday @bartvdbraak was doing some upgrade tests in UATEST buildbot (related to #57 and #94). When he built some PRs on the UATEST buildbot servers, these builds became listed under the PR page on gitea, overriding previous ones made on the production buildbot for the same PR. See e.g. blender/blender!125365, which currently links to https://builder-uatest.blender.org/admin/#/builders/22/builds/71 I would not expect any such connection between production gitea and UATEST buildbot. If this cannot be avoided, then using production gitea with UATEST buildbot should probably be avoided?

Bart van der Braak added this to the DevOps Progress Board project 2024-07-25 09:58:17 +02:00

Bart van der Braak self-assigned this 2024-07-25 09:58:33 +02:00

Bart van der Braak changed title from ~~Running PR builds in UATEST buildbot will appear in gitea (and override previous builds done for the PR on the production buildbot)~~ to Buildbot: Build run statuses from UATEST are shown in Gitea Production

2024-07-26 12:04:46 +02:00

Bart van der Braak commented

2024-07-26 14:50:28 +02:00

def setup_service(devops_env_id: str):
    import conf.worker

    importlib.reload(conf.worker)
    worker_config = conf.worker.get_config(devops_env_id)
    gitea_api_token = worker_config.gitea_api_token(devops_env_id)

    if gitea_api_token:
        log.msg("Found Gitea API token, enabling status push")
        return gitea.reporter.GiteaStatusService11(gitea_url, gitea_api_token, verbose=False)
    else:
        log.msg(f"No Gitea API token found, status push disabled")
        return None

I renamed the Gitea API token to gitea-api-token.disabled and restarted the master:

blender@pvep-lvm-buildbot-master-01:~/.devops/services/buildbot-master$ cat twistd.log | grep "Gitea API token"
2024-07-24 16:32:59+0200 [-] Found Gitea API token, enabling status push
...
2024-07-26 14:48:13+0200 [-] No Gitea API token found, status push disabled

``` def setup_service(devops_env_id: str): import conf.worker importlib.reload(conf.worker) worker_config = conf.worker.get_config(devops_env_id) gitea_api_token = worker_config.gitea_api_token(devops_env_id) if gitea_api_token: log.msg("Found Gitea API token, enabling status push") return gitea.reporter.GiteaStatusService11(gitea_url, gitea_api_token, verbose=False) else: log.msg(f"No Gitea API token found, status push disabled") return None ``` I renamed the Gitea API token to `gitea-api-token.disabled` and restarted the master: ``` blender@pvep-lvm-buildbot-master-01:~/.devops/services/buildbot-master$ cat twistd.log | grep "Gitea API token" 2024-07-24 16:32:59+0200 [-] Found Gitea API token, enabling status push ... 2024-07-26 14:48:13+0200 [-] No Gitea API token found, status push disabled ```

Bart van der Braak closed this issue

2024-07-26 14:50:29 +02:00

Sign in to join this conversation.