gocept / cihub Goto Github PK

Original report by me.

The cc.xml specification (https://web.archive.org/web/20090830044629/http://confluence.public.thoughtworks.org/display/CI/Multiple+Project+Summary+Reporting+Standard) allows to communicate the current activity of the ci job.

We are currently using sleeping as hard coded activity. It would be nice to also notify cihub at the beginning of running a job, to store this activity in the database and export it via cc.xml/cc.json.

Original report by me.

The cc.xml specification (https://web.archive.org/web/20090830044629/http://confluence.public.thoughtworks.org/display/CI/Multiple+Project+Summary+Reporting+Standard) allows to communicate the current activity of the ci job.

We are currently using sleeping as hard coded activity. It would be nice to also notify cihub at the beginning of running a job, to store this activity in the database and export it via cc.xml/cc.json.

Original report by [email protected] (Bitbucket: jeremykolbe, ).

Remove old entries to get rid of jobs wich are possibly no longer running.

Currently the messages from branches are written to the database as well as the ones from master.

Failed branches are okay as long as master stays green.

We have to fix the following integrations:

• jenkins does not know about branches
• bitbucket no longer in use
• travis #18
• github actions
• gitlab

Original report by [email protected] (Bitbucket: jeremykolbe, ).

Currently no tests are running on check-ins and PRs.

The readme says to call npm run test. But calling this command leads to:

$ npm run test

> [email protected] test /.../cihub/cihub-vue
> echo 'Error: no test specified'

Error: no test specified

Is this a documentation issue or are the tests actually missing?

Original report by me.

The cc.xml specification (https://web.archive.org/web/20090830044629/http://confluence.public.thoughtworks.org/display/CI/Multiple+Project+Summary+Reporting+Standard) allows to communicate the current activity of the ci job.

We are currently using sleeping as hard coded activity. It would be nice to also notify cihub at the beginning of running a job, to store this activity in the database and export it via cc.xml/cc.json.

Original report by me.

Breaking tests on pull requests should no break the status of the job.