← Back to issue list

Update remote build login when Launchpad infrastructure is ready

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1827679
Type
issue
State
closed
Author
~cmatsuoka
Labels
—
Created
Updated
Closed

Current evaluation

Remote builds now authenticate with Launchpad personal access tokens instead of SSH keys via snapcraft#4270 (commit 7c80a055b).

Resolution: closed resolved

Reason: Resolved by merged PR snapcraft#4270 at commit 7c80a055b, which replaced SSH-key authentication with personal access tokens. The maintainer closing comment confirms remote builds now support auth tokens instead of SSH keys.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Remote building, as described in bug #1805220, allows snapcraft to dispatch build jobs to Launchpad builders. Further work is needed on Launchpad to allow HTTP pushes to repositories (bug #1824399). Currently remote build is implemented to use authenticated access and requires ssh keys, change that after Launchpad infrastructure is ready.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Remote builds now authenticate with Launchpad personal access tokens instead of SSH keys via snapcraft#4270 (commit 7c80a055b).
stealth/space-bunny-alpha — closed resolved Remote builds now use personal access tokens instead of SSH keys, completing the deferred Launchpad authentication update in PR #4270 (commit 7c80a055b).
stealth/space-bunny-alpha — closed stale Closed without action after infrastructure evolution made the planned SSH-to-HTTP authentication follow-up obsolete; HTTPS-token support had landed separately in commit 21eba33c9 and PR #4270.
stealth/space-bunny-alpha — closed stale Launchpad bug #1827679 was closed without implementation: the planned remote-build authentication change was abandoned as obsolete after Launchpad infrastructure changed; no resolving PR or commit was recorded.
qwen/qwen3.6-35b-a3b — — Closed without action. The planned authentication update for remote builds was abandoned after Launchpad infrastructure changes made the task obsolete.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 10
Confidence: 85
Support Request: 0
close stale Tracking ticket to switch remote build authentication from SSH to HTTP once Launchpad infrastructure supports it. Inactive for over 7 years with no maintainer response or labels.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 15
Confidence: 90
Support Request: 5
close stale Feature request to update snapcraft's remote build authentication from SSH to HTTP once Launchpad infrastructure supports it. Currently inactive for over 7 years with no maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 15
Confidence: 90
Support Request: 5
close stale Placeholder task to switch snapcraft remote builds from SSH to HTTP authentication once Launchpad infrastructure supports it. Inactive for ~7 years with no maintainer response.

Update history

Date Change
created

Related work

  • Likely Fixed By: snapcraft#4270 (confidence 100%)

    Commit 7c80a055b changed remote-build authentication to use personal access tokens.

Related issues

Issue Project State Summary Similarity
#4892 fix(remotebuild): use legacy launchpad credentials if they exist snapcraft merged Merged in snapcraft#4892 as c1c70a249, adding legacy Launchpad credential fallback, build-for: all support, and expanded remote-build tests; fixes #4889.
76%
#4270 remote-build: Use personal access tokens snapcraft merged Merged PR #4270 as 7c80a055b, replacing deprecated Launchpad bearer macaroons with scoped, revocable, short-lived personal access tokens for remote builds.
74%
#4821 remote build: hangs when logging into Launchpad snapcraft closed Partly mitigated by Launchpad retries in craft-application; the CI login hang was closed as unsupported, with snapcraft.io recommended for CI builds.
74%
#4762 fix(remote): use launchpad credentials from legacy location snapcraft closed Closed unmerged; snapcraft#4892 later implemented the legacy Launchpad credential fallback in commit c1c70a249.
73%
#2825 remote-build: remove need to specify user snapcraft merged Merged #2825, removing the remote-build user requirement and adding automatic Launchpad login; it also fixed public-upload handling and cleaned up LaunchpadClient.
72%
#4889 Use launchpad credentials from the new location and fallback to the legacy location snapcraft closed Fixed in canonical/snapcraft#4892 (c1c70a249): both remote builders now fall back to legacy Launchpad credentials and emit a deprecation warning.
71%