【问题标题】:Using Travis CI to build Jekyll site from master to gh-pages with deploy keys使用 Travis CI 构建 Jekyll 站点,从 master 到 gh-pages 和部署密钥
【发布时间】:2017-05-16 13:53:13
【问题描述】:

我正在我们的网站上工作,其GitHub repo is here。这是一个无插件的网站,但为了安排帖子,我需要运行一个 Cron,而 Travis-CI 就在这里。

我的目标是简单地从 ma​​ster 复制内容并将其提供给 gh-pages。我正在使用部署密钥方法让 Travis 访问 GitHub 存储库。

当我推送更改时,Travis 运行构建,但退出并显示一条消息,The command "bash deploy.sh" exited with 1.

这是我的 Travis 配置:

language: ruby # don't install any environment
rvm:
  2.3.4

branches:
  only:
    master

before_script:
    chmod +x ./deploy.sh

script: bash ./deploy.sh

env:
  global:
  - ENCRYPTION_LABEL: "c68fb307f099"
  - COMMIT_AUTHOR_EMAIL: "myemail@gmail.com"

sudo: false # route your build to the container-based infrastructure for a faster build

这些是deploy.sh的内容:

#!/bin/bash
set -e # Exit with nonzero exit code if anything fails

SOURCE_BRANCH="master"
TARGET_BRANCH="gh-pages"

function doCompile {
  bundle exec jekyll build
}

# Pull requests and commits to other branches shouldn't try to deploy, just build to verify
if [ "$TRAVIS_PULL_REQUEST" != "false" -o "$TRAVIS_BRANCH" != "$SOURCE_BRANCH" ]; then
    echo "Skipping deploy; just doing a build."
    doCompile
    exit 0
fi

# Save some useful information
REPO=`git config github.com/merakipost/merakipost.github.io`
SSH_REPO=${REPO/https:\/\/github.com\//git@github.com:}
SHA=`git rev-parse --verify HEAD`

# Clone the existing gh-pages for this repo into out/
# Create a new empty branch if gh-pages doesn't exist yet (should only happen on first deply)
git clone $REPO out
cd out
git checkout $TARGET_BRANCH || git checkout --orphan $TARGET_BRANCH
cd ..

# Clean out existing contents
rm -rf out/**/* || exit 0

# Run our compile script
doCompile

# Now let's go have some fun with the cloned repo
cd out
git config user.name "Travis CI"
git config user.email "$COMMIT_AUTHOR_EMAIL"

# If there are no changes to the compiled out (e.g. this is a README update) then just bail.
if git diff --quiet; then
    echo "No changes to the output on this push; exiting."
    exit 0
fi

# Commit the "changes", i.e. the new version.
# The delta will show diffs between new and old versions.
git add -A .
git commit -m "Deploy to GitHub Pages: ${SHA}"

# Get the deploy key by using Travis's stored variables to decrypt deploy_key.enc
ENCRYPTED_KEY_VAR="encrypted_${ENCRYPTION_LABEL}_key"
ENCRYPTED_IV_VAR="encrypted_${ENCRYPTION_LABEL}_iv"
ENCRYPTED_KEY=${!ENCRYPTED_KEY_VAR}
ENCRYPTED_IV=${!ENCRYPTED_IV_VAR}
openssl aes-256-cbc -K $ENCRYPTED_KEY -iv $ENCRYPTED_IV -in ../deploy_key.enc -out ../deploy_key -d
chmod 600 ../deploy_key
eval `ssh-agent -s`
ssh-add deploy_key

# Now that we're all set up, we can push.
git push $SSH_REPO $TARGET_BRANCH

请指出其中的错误,并帮助我。

谢谢,
拉姆

【问题讨论】:

    标签: git bash jekyll travis-ci


    【解决方案1】:

    您在密钥的同一级别运行deploy.sh,因此openssl 命令应该在目录树中查找其密钥而无需向上一级:

    openssl aes-256-cbc -K $ENCRYPTED_KEY -iv $ENCRYPTED_IV -in deploy_key.enc -out deploy_key -d
    

    还可以尝试将一些echo 放在那里,这样您就可以看到其他什么失败了(或没有失败)。

    我写了一篇关于它的文章here,并使用了非常相似的方法here(工作)。

    【讨论】:

    • 谢谢你,@marcanuy!我在工作中。将检查并恢复。再次感谢!
    • 对这一切真的很陌生,所以请原谅这个问题。一切都很顺利,直到openssl 步骤,它要求我输入deploy_key 的密码。我应该设置没有密码的部署密钥,还是应该以某种方式传递密码?
    • 这是部件现在的样子:openssl aes-256-cbc -K $ENCRYPTED_KEY -iv $ENCRYPTED_IV -in deploy_key.enc -out deploy_key -d echo "Setting permissions on deploy_key" chmod 600 deploy_key eval `ssh-agent -s` echo "Adding deploy_key" ssh-add deploy_key
    • 再想一想,额外的密码短语感觉就像三层安全。哈哈。重新生成了一对没有密码的密钥,它就像一个魅力。谢谢! :)
    猜你喜欢
    • 2017-08-09
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2022-01-20
    • 2018-02-02
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多