Activity log for bug #1680571

Date Who What changed Old value New value Message
2017-04-06 19:06:19 Leo Arias bug added bug
2017-04-06 19:06:34 Leo Arias tags ci ui bitesize ci ui
2017-04-06 19:07:21 Leo Arias 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." 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#
2017-05-25 16:22:19 Leo Arias tags bitesize ci ui bitesize integrations ui
2023-08-17 17:44:40 Sergio Schvezov snapcraft: status Confirmed Won't Fix