sprucedev/dockci

CI, but with that all important Docker twist

dockci's Issues

User logins and access

https://trello.com/c/PxM88nW7/58-feature-request-user-logins-and-access

For the enterprise

As a mega corp
I would like to have user logins job access
So that user can only see and access there allowed jobs

Provision stage link to job that built the service image

https://trello.com/c/LnmvKlcR/97-provision-stage-link-to-build-that-built-the-service

As a developer
I want to see the job for a provisioned container's image
So that I can trace back and see how my services were built

Share build cache

https://trello.com/c/qEsXSzdH/81-share-build-cache

As a user
I want to pull the latest built image of a repository from the registry when I build
So that I share the cache across servers

From #71

Hook to trigger DockCI build

https://trello.com/c/oM8cJ3A8/56-feature-request-hook-to-trigger-dockci-build

As a DockCi job owner
I would like to tigger a DockCi job automatically via a git commit or tigger from builder server
Build would run with out any user intervention

Adding new project pre-existing slug does not result in error...

Adding new project with pre-existing slug does not result in error, instead it results in the pre-existing project's details being updated.
I reckon this is unexpected behaviour for most people.

Path security

https://trello.com/c/BgGEm8a9/28-bug-path-security

Issue with opening files from a filename given by the user: https://github.com/RickyCook/DockCI/blob/f9277a128ebb6247381a2256116eb12f50608d6c/dockci/views/job.py#L132

Refresh job status/info live

https://trello.com/c/QPGCOgGN/61-refresh-build-status-info-live

As a developer
I want job status and info to refresh live
So that I don't have to keep refreshing the page

Depends:

• UI overhaul #182

BUG: ANSI coloring not working

https://trello.com/c/FgAPLrdp/54-bug-ansi-coloring-not-working

Move pylint/pep8 to test-requirements.txt

https://trello.com/c/i588Ts9U/49-move-pylint-pep8-to-test-requirements-txt

Documentation framework

https://trello.com/c/81DSyZdy/15-documentation-framework

Tests: add tests to exercise the versioning/caching/cleanup behaviour

https://trello.com/c/tuxVCP8z/55-tests-add-tests-to-exercise-the-versioning-caching-cleanup-behaviour

Log time taken per job step

https://trello.com/c/7XqhzP8y/59-feature-request-log-time-taken-per-build-step

As a developer
I want to see how long docker job steps take
So that I know where to optimise build times

Dogestry support

https://trello.com/c/y9NjRToY/62-dogestry-support

Semanticly version tagged commits aren't being detected as versioned

Testing c627975 today, I noticed that the semantic version detection is broken.

I'm investigating.

Git changes in failure email

https://trello.com/c/rTaPae21/32-git-changes-in-failure-email

Implement pallet dep check UI

https://trello.com/c/4dSKllRq/99-implement-pallet-dep-check-ui

infoxchange/pallet#1

Incompatible client/server versions

https://trello.com/c/bhXtWoWu/39-bug-incompatible-client-server-versions

Docker-py uses a static Docker version as the client version. DockCI shouldn't care, and just match the version of the server

Line numbers on console

https://trello.com/c/QTzOyNqn/89-line-numbers-on-console

Record DockCI, and Docker version of job

https://trello.com/c/Jx0JlnG5/94-record-dockci-and-docker-version-of-build

Tests

https://trello.com/c/GhzjOel4/7-tests

Fix DockCI demo email

https://trello.com/c/mMAq5HRv/82-task-fix-dockci-demo-email

Email in on http://demo.dockci.io is broken because I moved thatpanda.com from my old provider. Need to get maybe mailgun or some such

Github hook registration UI

https://trello.com/c/7z38Zi5N/18-github-hook-registration-ui

As a developer
I want to choose my Github repo and have DockCI setup a push hook
So that I can quickly, and effortlessly setup DockCI for my project

Assumptions

• Github push hooks #17 is complete

Generic push hooks

https://trello.com/c/pHXWt9zU/12-generic-push-hooks

As a developer
I want to trigger builds from an external tool
So that my build flow is automated

Gitlab integration

Tasks linked in references

Debian as host OS rather than Ubuntu

As discussed - it would be advisable to use Debian as the host OS rather than Ubuntu

Git submodules

https://trello.com/c/utfsinFx/84-git-submodules

Link to github repo

https://trello.com/c/uWu8vAiv/88-link-to-github-repo

Sensitive data such as users credentials and other form input fields should be encrypted

https://trello.com/c/QjScl298/51-todo-sensitive-data-such-as-users-credentials-and-other-form-input-fields-should-be-encrypted

Re-run errored job button

https://trello.com/c/pfzgNTkY/35-re-run-errored-build-button

As a user
I want a re-run button
So that I don't have to copy & paste the git commit ID again and again

Assumptions

• Button on both project page, and job page
• Only for broken builds; not failed, or success

If github email, link to user

https://trello.com/c/u7jIY7jE/86-if-github-email-link-to-user

Dependencies for dependencies

https://trello.com/c/BALqAJyX/50-deps-dependencies-for-dependencies

As a developer
I want to specify a dependency hierarchy
So that my dependent services can be more complex

Example:
Search microservice dependency that requires a database/elasticsearch to function

Delete projects

https://trello.com/c/OgpmWE3i/78-delete-jobs

As a developer
I want to delete projects
So that my UI is uncluttered

Can't set email password to blank string

https://trello.com/c/nBOAuWNE/29-bug-can-t-set-email-password-to-blank-string

Setup.py

https://trello.com/c/FiW5mTIM/3-setup-py

As a tools admin
I want to install DockCI via pip
So that I don't have to go through a complex setup process

Stages with no output should not be added

https://trello.com/c/iuG8TRyV/75-stages-with-no-output-should-not-be-added

Git changes use job start time, not commit time

https://trello.com/c/o1MOyWL3/76-bug-git-changes-use-build-time-not-commit-time

As a developer
I want the git change log to show a diff since my most recent git ancestor, not most recent job that is a git ancestor
So that the history is not long (and more relevant) when started out of order

CLI: Build working directory

https://trello.com/c/sNWaRypo/66-cli-build-working-directory

As a developer
I want to start an "ad-hoc" job of my current working directory
So that I can test without needing to commit
So that I can integrate DockCI with an external build tool

Example

$ dockci build
--- git_prepare ---
Cloning into '/tmp/tmp6zbq69qr'...
Note: checking out '2d718539a461b3af3d34883d72d06162c23f29a8'.
...

--- git_info ---
...

$ dockci build ~/code/dockci
...

Assumptions
Requires a single log stream resource, separate from the current AJAX format of multiple requests

Questions

• Better name than build for CLI command (since we don't have a build model any more)

Slack group notifications

https://trello.com/c/RPFCVBPz/20-slack-group-notifications

As a developer
I want to be notified via Slack (https://slack.com) group chat when my job fails
So that I don't have to keep checking the CI server

Assumptions

• Not the first notifications story

CLI: List all built versions

https://trello.com/c/GmoZ8klM/67-cli-list-all-built-versions

As a developer
I want to list all available versions of a project
So that I can get information about my project to script with/etc

Assumptions

• #57 has been completed for the AJAX UI

data/configs.yaml not auto-created

My steps:

• rm -rf data
• ./dockci_server -p 8000
• navigate to http://127.0.0.1:8000/config

Github CI status push

https://trello.com/c/gM4bqPzE/60-github-ci-status-push

As a developer
I want to see CI build status on github commits
So that it's easy to see which commits passed in pull requests

Assumptions

• GitHub UI is complete #18

Favicon for progress, pass, fail

https://trello.com/c/TzBFWaQ6/93-favicon-for-progress-pass-fail

CLI: Show project info

https://trello.com/c/ZSal5Fik/65-cli-show-project-info

As a developer
I want to list project info from my working directory
So that integrate DockCI with my processes easily

Example

$ dockci show
URL: http://demo.dockci.io/projects/dockci
Last build: Passed
Last version: v0.0.2

$ dockci show ~/code/dockci
...

$ dockci show dockci
...

Notes
Can use remotes info to link the git working dir with the DockCI project, if the remotes match. What happens for HTTPS vs SSH clones though? GitHub we can pick up on; others maybe not?

Implement a clean-up "queue"

https://trello.com/c/DOQlaX9k/52-implement-a-clean-up-queue

Idea: have a queue where clean up tasks are sent that:

• don't impact job result
• might need to be retried (image deletion?)

Gitter group notifications

https://trello.com/c/k5qdFWP9/41-gitter-group-notifications

As a developer
I want to be notified via Slack (https://slack.com) group chat when my build fails
So that I don't have to keep checking the CI server

Assumptions

• Not the first notifications story

Link commits to github

https://trello.com/c/ZNdqmNoW/85-link-commits-to-github

ANSII sequences split over multiple stream structures are not displayed correctly

https://trello.com/c/EIT75VQC/68-bug-ansii-sequences-split-over-multiple-stream-structures-are-not-displayed-correctly

When the UI calls dockerBuildLine, on some {'stream':} content, it will ansi_to_html that content. This works until an ANSII sequence is started, and spans multiple stream objects, because the formatting is "reset" after each.

Use github avatar

https://trello.com/c/QdO7gNJJ/87-use-github-avatar

Project change in state notification

https://trello.com/c/DM3jVTva/77-build-change-in-state-notification

As a developer
I want to be notified only when a project branch changes state
So that I can be notified, without total spam for every job

Dependencies: #207
Assumptions:

• Restricted to branch. eg master, dev-cookr-my-feature, etc

Builds never cached after a Dockerfile ADD directive because of modification time

https://trello.com/c/v3PXSBCj/33-bug-builds-are-never-cached-after-a-dockerfile-add-directive-because-of-modification-time

Create a new job, wait for job to complete and don't commit anything, run another job with the same commit hash, wait for end of build stage

Expected: Build stage is entirely cached
Actual: Nothing is cached

Create a new job, wait for job to complete, create a commit and change 1 file in an ADD directive in the Dockerfile, run another job with the new commit, wait for end of build stage

Expected: Build stage is cached up until the ADD directive
Actual: Nothing is cached

Cause: Docker invalidates cache by multiple methods. The first check is on the file mtime. Git (unfortunately in this case) checks out files, but does not set the file mtime to the last commit time of files (the mtime is the time that git wrote the file to disk) which causes Docker to invalidate the cache every time