Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] Sign files using gpg --yes #7201

Merged
merged 1 commit into from Nov 14, 2019

Conversation

christophermaier
Copy link
Contributor

We've seen intermittent failures to upload manifest.json files
because when we go to sign it, gpg says there's already a
manifest.json.asc file present, and asks whether we want to
overwrite it or not. As it's a tiny bit tricky to get STDIN in a
Buildkite stage, the stage ends up timing out.

Here, we simply add the --yes option, to automatically answer such
questions in the affirmative.

I'm not exactly sure how a manifest.json.asc could be present in a
clean runner, though.

Signed-off-by: Christopher Maier cmaier@chef.io

We've seen intermittent failures to upload `manifest.json` files
because when we go to sign it, `gpg` says there's already a
`manifest.json.asc` file present, and asks whether we want to
overwrite it or not. As it's a tiny bit tricky to get STDIN in a
Buildkite stage, the stage ends up timing out.

Here, we simply add the `--yes` option, to automatically answer such
questions in the affirmative.

I'm not exactly sure how a `manifest.json.asc` could be present in a
clean runner, though.

Signed-off-by: Christopher Maier <cmaier@chef.io>
@christophermaier christophermaier merged commit dedf94e into master Nov 14, 2019
@chef-expeditor chef-expeditor bot deleted the cm/force-gpg-to-do-the-thing branch November 14, 2019 18:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants