platypush/blog
2
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fixed a couple of typos

Browse source
This commit is contained in:
Fabio Manganiello 2021-03-07 20:25:54 +01:00
parent f761131a24
commit 014b80fcb4
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
static/pages/Set-up-self-hosted-CI-CD-git-pipelines-with-Platypush.md
View file

@ -16,8 +16,8 @@ run integration tests online and a ReadTheDocs integration to automatically gene
## You and whose code? ## You and whose code?
A few things have changed lately, and I don't feel like I should rely much on the tools mentioned above for my CI/CD However, a few things have changed lately, and I don't feel like I should rely much on the tools mentioned above for my
pipelines. CI/CD pipelines.
Github has Github has
[too often taken the wrong side](https://www.bleepingcomputer.com/news/software/github-threatens-to-ban-users-who-bypass-youtube-dl-takedown/) [too often taken the wrong side](https://www.bleepingcomputer.com/news/software/github-threatens-to-ban-users-who-bypass-youtube-dl-takedown/)
@ -48,7 +48,7 @@ to open-source software. And, again, Travis-CI is plagued by the same contradict
open-source friendly, but it's not open-source itself, and you can't install it on your own machine. open-source friendly, but it's not open-source itself, and you can't install it on your own machine.
ReadTheDocs, luckily, seems to be still coherent with its mission of supporting open-source developers, but I'm also ReadTheDocs, luckily, seems to be still coherent with its mission of supporting open-source developers, but I'm also
keeping an eye in them just in case :) keeping an eye on them just in case :)
## Building a self-hosted CI/CD pipeline ## Building a self-hosted CI/CD pipeline
@ -75,12 +75,12 @@ In this article we'll how to use Platypush to set up a pipeline that:
- Runs a suite of tests. - Runs a suite of tests.
- If the tests succeed, then proceed with packaging the new version of the code - in my case, I run the automation to - If the tests succeed, then it proceeds with packaging the new version of the codebase - in my case, I run the
automatically create the new [`platypush-git`](https://aur.archlinux.org/packages/platypush-git) package for Arch automation to automatically create the new [`platypush-git`](https://aur.archlinux.org/packages/platypush-git) package
Linux on new pushes, and the new [`platypush`](https://aur.archlinux.org/packages/platypush) Arch package and for Arch Linux on new pushes, and the new [`platypush`](https://aur.archlinux.org/packages/platypush) Arch package and
the [`pip` package](https://pypi.org/project/platypush/) on new tags. the [`pip` package](https://pypi.org/project/platypush/) on new tags.
- If the tests fail, send a notification (over - If the tests fail, it sends a notification (over
[email](https://docs.platypush.tech/en/latest/platypush/plugins/mail.smtp.html), [email](https://docs.platypush.tech/en/latest/platypush/plugins/mail.smtp.html),
[Telegram](https://docs.platypush.tech/en/latest/platypush/plugins/chat.telegram.html), [Telegram](https://docs.platypush.tech/en/latest/platypush/plugins/chat.telegram.html),
[Pushbullet](https://docs.platypush.tech/en/latest/platypush/plugins/pushbullet.html) or [Pushbullet](https://docs.platypush.tech/en/latest/platypush/plugins/pushbullet.html) or
@ -228,7 +228,7 @@ event` line with a content like this on the standard output or log file of Platy
"project": { "project": {
"id": 1, "id": 1,
"name": "My project", "name": "My project",
"description": "Project escription", "description": "Project description",
"web_url": "https://git.platypush.tech/platypush/platypush", "web_url": "https://git.platypush.tech/platypush/platypush",
"avatar_url": "https://git.platypush.tech/uploads/-/system/project/avatar/3/icon-256.png", "avatar_url": "https://git.platypush.tech/uploads/-/system/project/avatar/3/icon-256.png",
"git_ssh_url": "git@git.platypush.tech:platypush/platypush.git", "git_ssh_url": "git@git.platypush.tech:platypush/platypush.git",