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

[Leo Arias]

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
    services:
    - docker
    after_success:
    - openssl aes-256-cbc -K <travis-key> -iv <travis-iv>
        -in .snapcraft/travis_snapcraft.cfg
        -out .snapcraft/snapcraft.cfg -d
    deploy:
        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"
        on:
          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 https://docs.google.com/document/d/1vPUMH9UNOP8AqjhcslMZ5LQHMV3xvMYYKb7slC4s_Gc/edit#

[David Callé (davidc3)]

The URL is not working yet, but this is the expected one for the tutorial: https://tutorials.ubuntu.com/tutorial/continuous-delivery-from-travis-ci

[Leo Arias (elopio)]

Come on! I've waited for yeeeears for this bug fix. 😘🤗

On August 17, 2023 11:44:40 AM CST, Sergio Schvezov <email address hidden> wrote:
>** Changed in: snapcraft
> Status: Confirmed => Won't Fix
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1680571
>
>Title:
> The enable-ci travis message includes an example that makes it too
> long and ugly
>
>Status in Snapcraft:
> Won't Fix
>
>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
>     services:
>     - docker
>     after_success:
>     - openssl aes-256-cbc -K <travis-key> -iv <travis-iv>
>         -in .snapcraft/travis_snapcraft.cfg
>         -out .snapcraft/snapcraft.cfg -d
>     deploy:
>         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"
>         on:
>           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
> https://docs.google.com/document/d/1vPUMH9UNOP8AqjhcslMZ5LQHMV3xvMYYKb7slC4s_Gc/edit#
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/snapcraft/+bug/1680571/+subscriptions
>

--
¡paz y baile!