The enable-ci travis message includes an example that makes it too long and ugly

Bug #1680571 reported by Leo Arias
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Currently, before making the changes in the .travis.yml file we are showing a long message with all the details of what will happen to the file. It includes an example of how the file could look after the command runs:

See the example below::

    sudo: required
    - docker
    - openssl aes-256-cbc -K <travis-key> -iv <travis-iv>
        -in .snapcraft/travis_snapcraft.cfg
        -out .snapcraft/snapcraft.cfg -d
        skip_cleanup: true
          Provider: script
        script: docker run -v $(pwd):$(pwd) -t ubuntu:xenial sh -c
            "apt update -qq && apt install snapcraft -y && cd $(pwd) &&
            snapcraft && snapcraft push *.snap --release edge"
          branch: master

From Gustavo:
"The example here feels a bit dirty [...]. We should simply state that it will be modified and why. Not how or with which content. We know for sure that this file is under revision control, and may be reviewed if desired, and the developer will also need to commit acknowledging the change explicitly before it's put in use."

To reproduce:

$ snapcraft enable-ci travis

A longer explanation on how to set this up from scratch in

Leo Arias (elopio)
tags: added: bitesize
description: updated
Revision history for this message
David Callé (davidc3) wrote :

The URL is not working yet, but this is the expected one for the tutorial:

Leo Arias (elopio)
tags: added: integrations
removed: ci
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers