From 945ad95baef908a3fbe90806817d379fabb8de21 Mon Sep 17 00:00:00 2001 From: Dawid Dziurla Date: Mon, 11 Nov 2019 12:36:04 +0100 Subject: [PATCH] Comment out snapcraft stuff It's failing the release pipeline and we do not use it currently. --- .circleci/config.yml | 28 +++++------ .goreleaser.yml | 116 +++++++++++++++++++++---------------------- 2 files changed, 72 insertions(+), 72 deletions(-) diff --git a/.circleci/config.yml b/.circleci/config.yml index 0be01eff..d8f383dd 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -60,20 +60,20 @@ jobs: - image: circleci/golang:1.12 steps: - checkout - - run: - name: Install snapcraft - command: | - ./.circleci/install_snapcraft.sh - - run: - name: Login to snapcraft - # if you ever lose this, you can recreate it via - # `snapcraft export-login snapcraft.login && base64 snapcraft.login` and then chuck that - # in circle ci as the SNAPCRAFT_LOGIN_FILE env variable - # You'll need your ubuntu one password - command: | - echo $SNAPCRAFT_LOGIN_FILE | base64 --decode --ignore-garbage > snapcraft.login - snapcraft login --with snapcraft.login - rm snapcraft.login + #- run: + # name: Install snapcraft + # command: | + # ./.circleci/install_snapcraft.sh + #- run: + # name: Login to snapcraft + # # if you ever lose this, you can recreate it via + # # `snapcraft export-login snapcraft.login && base64 snapcraft.login` and then chuck that + # # in circle ci as the SNAPCRAFT_LOGIN_FILE env variable + # # You'll need your ubuntu one password + # command: | + # echo $SNAPCRAFT_LOGIN_FILE | base64 --decode --ignore-garbage > snapcraft.login + # snapcraft login --with snapcraft.login + # rm snapcraft.login - run: name: Run gorelease command: | diff --git a/.goreleaser.yml b/.goreleaser.yml index 559d882e..8e29c896 100644 --- a/.goreleaser.yml +++ b/.goreleaser.yml @@ -73,61 +73,61 @@ brews: # Default is empty. description: 'A simple terminal UI for docker, written in Go' -snapcrafts: - - builds: - - snap - - replacements: - linux: Linux - 386: x86 - amd64: x86_64 - - # Wether to publish the snap to the snapcraft store. - # Remember you need to `snapcraft login` first. - # Defaults to false. - publish: false - - # Single-line elevator pitch for your amazing snap. - # 79 char long at most. - summary: The lazier way to manage everything docker - - # This the description of your snap. You have a paragraph or two to tell the - # most important story about your snap. Keep it under 100 words though, - # we live in tweetspace and your description wants to look good in the snap - # store. - description: 'A simple terminal UI for docker, written in Go' - - # A guardrail to prevent you from releasing a snap to all your users before - # it is ready. - # `devel` will let you release only to the `edge` and `beta` channels in the - # store. `stable` will let you release also to the `candidate` and `stable` - # channels. More info about channels here: - # https://snapcraft.io/docs/reference/channels - # TODO: reset to `stable` when we've been manually reviewed: https://forum.snapcraft.io/t/request-for-classic-confinement-for-lazydocker/12155 - grade: devel - - # Snaps can be setup to follow three different confinement policies: - # `strict`, `devmode` and `classic`. A strict confinement where the snap - # can only read and write in its own namespace is recommended. Extra - # permissions for strict snaps can be declared as `plugs` for the app, which - # are explained later. More info about confinement here: - # https://snapcraft.io/docs/reference/confinement - confinement: classic - - # Your app's license, based on SPDX license expressions: https://spdx.org/licenses - # Default is empty. - license: MIT - - # # Each binary built by GoReleaser is an app inside the snap. In this section - # # you can declare extra details for those binaries. It is optional. - # apps: - - # # The name of the app must be the same name as the binary built or the snapcraft name. - # lazydocker: - - # # If your app requires extra permissions to work outside of its default - # # confined space, declare them here. - # # You can read the documentation about the available plugs and the - # # things they allow: - # # https://snapcraft.io/docs/reference/interfaces. - # plugs: [] +#snapcrafts: +# - builds: +# - snap +# +# replacements: +# linux: Linux +# 386: x86 +# amd64: x86_64 +# +# # Wether to publish the snap to the snapcraft store. +# # Remember you need to `snapcraft login` first. +# # Defaults to false. +# publish: false +# +# # Single-line elevator pitch for your amazing snap. +# # 79 char long at most. +# summary: The lazier way to manage everything docker +# +# # This the description of your snap. You have a paragraph or two to tell the +# # most important story about your snap. Keep it under 100 words though, +# # we live in tweetspace and your description wants to look good in the snap +# # store. +# description: 'A simple terminal UI for docker, written in Go' +# +# # A guardrail to prevent you from releasing a snap to all your users before +# # it is ready. +# # `devel` will let you release only to the `edge` and `beta` channels in the +# # store. `stable` will let you release also to the `candidate` and `stable` +# # channels. More info about channels here: +# # https://snapcraft.io/docs/reference/channels +# # TODO: reset to `stable` when we've been manually reviewed: https://forum.snapcraft.io/t/request-for-classic-confinement-for-lazydocker/12155 +# grade: devel +# +# # Snaps can be setup to follow three different confinement policies: +# # `strict`, `devmode` and `classic`. A strict confinement where the snap +# # can only read and write in its own namespace is recommended. Extra +# # permissions for strict snaps can be declared as `plugs` for the app, which +# # are explained later. More info about confinement here: +# # https://snapcraft.io/docs/reference/confinement +# confinement: classic +# +# # Your app's license, based on SPDX license expressions: https://spdx.org/licenses +# # Default is empty. +# license: MIT +# +# # # Each binary built by GoReleaser is an app inside the snap. In this section +# # # you can declare extra details for those binaries. It is optional. +# # apps: +# +# # # The name of the app must be the same name as the binary built or the snapcraft name. +# # lazydocker: +# +# # # If your app requires extra permissions to work outside of its default +# # # confined space, declare them here. +# # # You can read the documentation about the available plugs and the +# # # things they allow: +# # # https://snapcraft.io/docs/reference/interfaces. +# # plugs: []