kminehart/jules

A pretty basic build system for repositories with multiple projects.

jules's Issues

`diffs` will have to be rethinked or better documented.

Test coverage is low!

ok  	_/home/kminehart/Work/jules/cmd/jules	0.002s	coverage: 18.8% of statements

what a disaster!

Code cleanup initiative!

We should probably move some stuff over to pkg and stop being bad at programming.

Clean up the output.

[Lint] Warn users when using an absolute path.

I kind of suck at writing Go so I need to rebuild this to accept interfaces and return structs like a real man.

Clean up that ugly main.go

Use docker containers to run tests

The problem

I'm having to ship a giant docker container to run Jules on monorepos with many different classes of projects.

Example:
We have a monorepo which pretty heavily uses Go. It also has a project for the front-end, which uses node / yarn. There's also a small Ruby project for some one-off thing that Ruby fanboy in the office built. Someone else decided to use Django for a small administrative piece.

Suddenly, Jules needs python, go, node, yarn, dep... It's not exactly a configurable solution.'

The solution

Allow projects to specify docker containers. For running the go commands, specify the golang docker image; or for the ruby project, specify the ruby image.

Implementing the `-diffs` flag.

-diffs is supposed to only run tests on projects that have been changed in this commit.

The original plan said that "if a file was changed in this commit, then run the stage(s) for the project it is in."

However, there's an issue with that. If the test fails, and the developer goes on to modify another project, then the tests won't run for that project until it is modified again, leading to false positives.

One proposed solution would be to make the diffs based on branches.

jules test -diff origin/master

Run a stage on every project concurrently.