← Back to issue list

Use launchpad credentials from the new location and fallback to the legacy location

View original Github issue

Metadata

Project
snapcraft
Number
#4889
Type
issue
State
closed
Author
mr-cal
Labels
—
Created
Updated
Closed

Current evaluation

Fixed in canonical/snapcraft#4892 (c1c70a249): both remote builders now fall back to legacy Launchpad credentials and emit a deprecation warning.

Resolution: closed resolved

Reason: Merged PR canonical/snapcraft#4892, commit c1c70a249, added the credential fallback and warning for both new and legacy remote builders, along with tests.

Evaluated by: mr-cal-bot

No scores available.

Issue body

### What needs to get done For both the new and legacy remote builders, Snapcraft should read launchpad credentials from the new location. If they don't exist, read from the legacy location and emit a deprecation warning. new location: `$XDG_DATA_HOME/snapcraft/launchpad-credentials` legacy location: `$XDG_DATA_HOME/snapcraft/provider/launchpad/credentials` ### Why it needs to get done To improve the UX when switching between the legacy and new remote builders.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Fixed in canonical/snapcraft#4892 (c1c70a249): both remote builders now fall back to legacy Launchpad credentials and emit a deprecation warning.
stealth/space-bunny-alpha — closed resolved Merged PR #4892 (c1c70a249) added legacy Launchpad credential fallback with a deprecation warning, resolving #4889.
stealth/space-bunny-alpha — closed resolved Merged PR canonical/snapcraft#4892 (c1c70a249) added legacy Launchpad credential fallback with a deprecation warning and tests, resolving #4889.
qwen/qwen3.6-35b-a3b — — Closed and migrated to internal Jira ticket CRAFT-3077. No implementation or merge was completed in this repository. The credential fallback logic remains unaddressed.
qwen/qwen3.6-35b-a3b — — Closed without implementation. No pull request or fix was merged. The request appears abandoned or superseded, with only an internal Jira ticket created for tracking.
qwen/qwen3.6-35b-a3b — — Closed without implementation. The feature to read launchpad credentials from a new location with legacy fallback was deferred to an internal Jira ticket and ultimately abandoned.
qwen3.6-35b-a3b-mtp-q6 — — Closed without implementation or linked PR. Synced to internal Jira but lacks resolution or merge details, indicating the feature request was abandoned or deferred.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: canonical/snapcraft#4892 (confidence 100%)

    The merged PR implemented legacy credential fallback and closed #4889.

Related issues

Issue Project State Summary Similarity
#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.
84%
#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.
82%
#1827679 Update remote build login when Launchpad infrastructure is ready snapcraft (launchpad) closed Remote builds now authenticate with Launchpad personal access tokens instead of SSH keys via snapcraft#4270 (commit 7c80a055b).
71%