Jaypore CI

> Jaypore CI: Minimal, Offline, Local CI system.
Log | Files | Refs | README

commit 17ed400b89972a6d3c980f9dcf8eee175a9067ee
parent 6461ad8386093de2391365ed712b4593126813d6
Author: arjoonn <arjoonn@noreply.localhost>
Date:   Tue, 14 Mar 2023 03:15:28 +0000

Multiple remote idea voting (!60)

Branch auto created by JayporeCI

```jayporeci
╔ 🔴 : JayporeCI       [sha 3c8cedba5f]
┏━ build-and-test
┃
┃ 🟢 : JciEnv          [00b61467]   0: 9
┃ 🟢 : Jci             [f316cc98]   0:16            ❮-- ['JciEnv']
┃ 🟢 : black           [5b1dfe31]   0: 0            ❮-- ['JciEnv']
┃ 🟢 : install-test    [934487f6]   0: 0            ❮-- ['JciEnv']
┃ 🟢 : pylint          [250a7285]   0: 8            ❮-- ['JciEnv']
┃ 🟢 : pytest          [982bd1db]   0:24 Cov: 91%   ❮-- ['JciEnv']
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
┏━ Publish
┃
┃ 🟢 : DockerHubJci    [cf01f24e]   0:46
┃ 🟢 : DockerHubJcienv [b2007316]   0:45
┃ 🟢 : PublishDocs     [964dd30a]   0:33
┃ 🔴 : PublishPypi     [6e158a9e]   0: 5 v0.2.23
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
```

Co-authored-by: demo <demo@example.com>
Reviewed-on: https://gitea.midpathsoftware.com/midpath/jaypore_ci/pulls/60

Diffstat:
MREADME.md | 3+--
Mdocs/source/index.rst | 22++++++++++++++++++++++
2 files changed, 23 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md @@ -1,9 +1,8 @@ # ![JayporeCI](docs/source/_static/logo80.png) Jaypore CI - Documentation is at : https://www.jayporeci.in -## If you are reading this on github +## If you are reading this on GitHub - Github is only the mirror for this codebase. - Actual development is on a personal gitea instance. diff --git a/docs/source/index.rst b/docs/source/index.rst @@ -393,6 +393,28 @@ commit message contains **jci:release** as one of it's lines. if p.repo.commit_message.contains("jci:release"): p.job("release", "bash cicd/release.sh", depends_on=["build"]) +[WIP: `Vote for it <https://github.com/theSage21/jaypore_ci/issues/14>`_ ] Select remote based on job status / branch / authors +------------------------------------------------------------- + +At times it's necessary to inform multiple people about CI failues / passing. + +For example + +- Stakeholders might need notifications when releases happen. +- People who wrote code might need notifications when their code breaks on a more intensite test suite / fuzzying run. +- Perhaps you have downstream codebases that need to get patched when you do bugfixes. +- Or perhaps a failure in the build section of the pipeline needs one set of + people to be informed and a failure in the user documentation building needs + another set of people. + + +While all of this is already possible with JayporeCI, if this is a common +workflow you can vote on it and we can implement an easier way to declare this +configuration. + + + + Contributing ============