louischatriot / braindead-ci Goto Github PK

Cannot change the name of a job cleanly, as well as the SSH url.

Correct ssh url -> random one -> correct again
Then it can't build the job anymore

Spaces should be escaped in the 'cd' command.

Not ultra-urgent, but it would be nice to have evergreen urls as soon as a build is launched.

Too tangled

Config params values should be (in this order)
given by the command line or
through a config file or
default config

currentName badly passed.

So that you don't wait for it for a long time

Works perfectly with external script, not so much with internal scripts. Problems linked to one-lining scripts.

Strange error popping up from time to time:

events.js:66
throw arguments[1]; // Unhandled 'error' event
^
Error: EBADF, close

fs.exists sometimes creates the directory it's supposed to test ... Maybe use node-fs module.

It would really save a lot of time if one could see at one glance which job are enabled and which aren't.
I have something like this in mind:

And add a setting for it

Extend advertiseBuildResult so that people can plug in their own result advertisers like email (which should really be built-in, btw)

At least for the Job CRUD actions.

Especially for the users/password encryption and job mgmt parts.

Stop having a new build destroy the one that is currently running on the same repo

So that we get real time feedback

Is there a reason for the job name limitation to 16 characters? If not, increase or lift.

Small detail but that would be good :)

Either a standalone page or in the column, on the left.

might as well put all job data in memory, except build status maybe