Original link: https://blog.est.im/2022/stdout-07
The current blog is based on pelican’s static-site generator. A python module is rendered into static files locally and published through github pages.
The source code is stored on bitbucket. Before, I was lazy and ran it locally. I always wanted to change it to a CI/CD pipeline. Today, I finally configured it. Record some pits
- The data is not shared between the different steps of the bitbucket pipeline. I originally wanted to use the parallel function to download the pip module and git clone skin in parallel, but later found that the speed of artifact copying is not as good as running serially. Just play one step for all the steps, just sit and finish
- The blog source code and the generated result can directly synchronize the submission information: msg=$(git log -1 –pretty=%B) cd output git config user.name est git config user.email mailbox git add .git commit -m “$msg”
git push
- Since the pip module is installed and I don’t know where it is, debug the pip installation path method:
python -c ‘import site; print(*site.getsitepackages(), sep=”\n”)’ - pelican doesn’t support Markdown by default, it’s drunk
python -m pip install pelican==4.8.0 Markdown - Custom skin dependencies, because I didn’t play with submodules, so I installed them like this:
git clone –depth=1 [email protected]:est/aether-pelican.git || (cd aether-pelican; git pull –rebase)
This article is reproduced from: https://blog.est.im/2022/stdout-07
This site is for inclusion only, and the copyright belongs to the original author.