← Back to issue list

Add support for enabling ci systems (start with travis)

View original Launchpad issue

Metadata

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

Current evaluation

CI setup support was implemented in snapcore/snapcraft PR #901 via commit d7d550741, adding the initial enable-ci command for Travis CI.

Resolution: closed resolved

Reason: The requested facility was delivered by snapcore/snapcraft PR #901, recorded as commit d7d550741 and linked in the issue’s resolution comment. PR #932 subsequently added refresh support.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Add a facility to setup ci systems

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved CI setup support was implemented in snapcore/snapcraft PR #901 via commit d7d550741, adding the initial enable-ci command for Travis CI.
stealth/space-bunny-alpha — closed resolved CI enablement was implemented by snapcore/snapcraft PR #901 in commit d7d550741; follow-up PR #932 added `enable-ci travis --refresh`.
stealth/space-bunny-alpha — closed resolved Maintainer-opened feature request to add CI system setup was implemented by snapcraft PR #901 (commit d7d550741), adding the initial `enable-ci` command for Travis CI, later extended by #932 and removed in #3164.
stealth/space-bunny-alpha — closed resolved CI setup was implemented with enable-ci in #901, followed by enable-ci travis --refresh in #932 (fe7e10826).
qwen/qwen3.6-35b-a3b — — Closed without comments or implementation. The request to add CI support, starting with Travis, was abandoned or superseded by later project CI integrations.
qwen/qwen3.6-35b-a3b — — Closed without discussion or implementation. The request to add CI system support, starting with Travis, was abandoned or superseded by modern CI practices.
qwen/qwen3.6-35b-a3b — — The request to implement CI system support, starting with Travis, was closed without discussion or implementation. No pull requests or resolution details were provided, indicating the feature was abandoned.
qwen3.6-35b-a3b-mtp-q6 — — CI system support, starting with Travis, was closed without implementation. Zero comments or commits indicate the request was abandoned or superseded by modern CI practices.

Update history

Date Change
created

Related work

  • Likely Fixed By: snapcore/snapcraft#901 (confidence 99%)

    Merged implementation of the enable-ci command, tracked as commit d7d550741.

  • Related To: snapcore/snapcraft#932 (confidence 95%)

    Follow-up PR adding enable-ci travis --refresh functionality.

Related issues

Issue Project State Summary Similarity
#901 Basic 'enable-ci' implementation. snapcraft merged Merged into snapcraft 2.0 via commit d7d550741, adding the `snapcraft enable-ci` command that drives travis-cli to set up Travis CI builds/releases with attenuated per-project store macaroons.
78%
#1679441 the enable-ci travis command is not using the snapcraft docker image snapcraft (launchpad) closed Fixed by snapcore/snapcraft#1331, merged as commit 6d777f770; Travis enable-ci now uses the snapcore/snapcraft Docker image.
76%
#1646660 Refresh `enable-ci` credentials snapcraft (launchpad) closed Feature delivered: `snapcraft enable-ci travis --refresh` added by merged PR snapcore/snapcraft#932 (commit fe7e10826); Launchpad bug closed by sergiusens on 2016-12-02 pointing at that PR.
71%
#1331 integrations: use the snapcore/snapcraft docker image in travis snapcraft merged Merged PR #1331 as commit 6d777f770, switching generated Travis CI integrations from the Xenial container to the snapcore/snapcraft Docker image; existing projects were not auto-migrated.
70%