Skip to content

Conversation

wo0dyn
Copy link
Contributor

@wo0dyn wo0dyn commented Feb 24, 2017

Rationale

I've split CircleCI jobs into:

  • tox -e $(tox -l | grep django18 | tr '\n' ',')
  • tox -e $(tox -l | grep django19 | tr '\n' ',')
  • tox -e flake8
  • tox -e isort-check

This way, we can spot more quickly which jobs have failed, without reading the full log of the previous job.

@wo0dyn wo0dyn force-pushed the split-tox-jobs-in-circleci branch from bc34925 to 30f0260 Compare February 24, 2017 13:28
@wo0dyn wo0dyn requested review from brunobord and mgu February 24, 2017 13:29
@wo0dyn wo0dyn self-assigned this Feb 24, 2017
@wo0dyn wo0dyn force-pushed the split-tox-jobs-in-circleci branch 2 times, most recently from 1e34603 to 5c826ed Compare February 24, 2017 13:46
@wo0dyn
Copy link
Contributor Author

wo0dyn commented Feb 24, 2017

screenshot from 2017-02-24 15 00 50

@wo0dyn wo0dyn force-pushed the split-tox-jobs-in-circleci branch from 5c826ed to 987102a Compare February 24, 2017 13:54
I've split CircleCI jobs into:
  * tox -e $(tox -l | grep django18 | tr '\n' ',')
  * tox -e $(tox -l | grep django19 | tr '\n' ',')
  * tox -e flake8
  * tox -e isort-check

This way, we can spot more quickly which jobs have failed, without
reading the full log of the previous job.
@wo0dyn wo0dyn force-pushed the split-tox-jobs-in-circleci branch from 987102a to 8aa2cec Compare February 24, 2017 13:56
@wo0dyn wo0dyn requested a review from moumoutte February 24, 2017 14:00
@mgu
Copy link
Contributor

mgu commented Feb 24, 2017

do we really want to separate django 1.8 and django 1.9 ?
same question for flake8/isort

@wo0dyn
Copy link
Contributor Author

wo0dyn commented Feb 24, 2017

do we really want to separate django 1.8 and django 1.9 ?
same question for flake8/isort

Yeah, that was intend to quickly spot which check failed. Since some features are deprecated in Django version, I think it's useful to detect which version of Django raises an potential issue, without digging the whole log.

Besides, I feel:

  • tox -e $(tox -l | grep django18 | tr '\n' ',')
  • tox -e $(tox -l | grep django19 | tr '\n' ',')
  • tox -e flake8
  • tox -e isort-check

more readable than

  • tox -e $(tox -l | grep django | tr '\n' ',')
  • tox -e $(tox -l | grep -v django | tr '\n' ',')

Overall, it doesn't take much time anyway. Still not convinced? 😉

Copy link
Contributor

@mgu mgu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM !
good job, It should help me to spot my flake8 at a glance ;)

@wo0dyn wo0dyn merged commit 90854f5 into master Feb 24, 2017
@wo0dyn wo0dyn deleted the split-tox-jobs-in-circleci branch February 24, 2017 15:37
@wo0dyn wo0dyn added 4 - Done and removed 3 - Review labels Mar 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants