Pass child data in views up to higher-level scopes (e.g. top nav)

To bubble up low-level info to higher level views in the app, the global templates (nav, dashboard, etc) need access to things like build status, job status, and durations from resources like the BuildController and JobController

When @adamreese was running the ui locally, it was throwing the following angular error:

foundation.js:10511 Uncaught Error: [$injector:unpr] Unknown provider: $$forceReflowProvider <- $$forceReflow <- $$animateQueue <- $animate <- $compile <- $$animateQueue
http://errors.angularjs.org/1.4.2/$injector/unpr?p0=%24%24forceReflowProvider%20%3C-%20%24%24forceReflow%20%3C-%20%24%24animateQueue%20%3C-%20%24animate%20%3C-%20%24compile%20%3C-%20%24%24animateQueue
    at foundation.js:6163
    at foundation.js:10359
    at Object.getService [as get] (foundation.js:10506)
    at foundation.js:10364
    at getService (foundation.js:10506)
    at Object.invoke (foundation.js:10538)
    at foundation.js:10365
    at getService (foundation.js:10506)
    at Object.invoke (foundation.js:10538)
    at foundation.js:10365

Specifying angular 1.4.14 avoids this error, but this should be looked into to avoid causing potential headaches for people down the line.

Likely the app.js needs to be reorganized to call angular.module and app.config elements in the correct order.

Common triggers are:

• github
• dockerhub
• acr
• containerregistry
• brig

Introduced in #77, pretty sure it's a path issue. Only happens in Chrome, doesn't seem to affect font rendering, though.

Access and display log output from Jobs.

/job/id/logs
/task/id/logs

We don't have a concept of teams right now

update the brigade.sh site at https://github.com/deis/brigade-www to add new sections to show Kashti as a part of the Brigade story

Make sure that UI can be served via SSL

To encourage community participation on the project (and make development easier for us), we should structure the project inline with the Angular style guide: https://angular.io/guide/styleguide#overall-structural-guidelines

This is refactoring work to move folders and files to a simple component based structure, but not to refactor components/code in general.

This probably requires adding the build state to the /project/:id/builds endpoint

• remove current links
• replace with event/author filters

And if an error, expand the log block

Use a neater format or moment.js to clean up the listings:

Running npm install -g bower or bower install returns:

npm WARN deprecated [email protected]: ...psst! Your project can stop working at any moment because its dependencies can change. Prevent this by migrating to Yarn: https://bower.io/blog/2017/how-to-migrate-away-from-bower/

We should replace bower with yarn. Yarn is pretty much a drop in replacement.

Should keep:

• Activity
• Configuration

The build view spills over to the right hand side as job data loads. See this example (from brian redmond's build):

When I browse the UI, i'm getting a bunch of 404s for API endpoints in the console:

e.g.
http://acid-api.technosophos.me:7745/v1/project/01bz3j29xmz4dhs99xahm1q9bh
http://acid-api.technosophos.me:7745/v1/project/01bzzn07g488przds1x7n21p2v
http://acid-api.technosophos.me:7745/v1/project/01bzzmz498aqh18hc7j5erjxmm/builds

I think these are endpoints that did exist, but have expired?

Is there a way the UI / API can know the difference between a build which still has data, and one that has expired? Not for MVC, but important UX for launch, to have better error states.

"Add a Project" button should either (a) open docs or (b) go away until we can do it inline.

@adamreese says we should just remove the branch dropdown

Dumps blob of data. Drop-down item doesn't always go away

This is definitely not critical, but I get this on my JS console.

When I click on the chart, scroll me to the job

We need a way to specify the base URL for:

• the UI itself
• the API server we attach to

Add a chart to run this as a deployment
Depends on #8

Dockerfile should serve static assets via nginx or suitable alternative.

This message can be confused for 'active building' state seen in similar CI UI. let's drop it for now.

The list order needs to be reversed, to show the latest at the top:

Needs updating to unsquish:

Should do this after the Oauth work has been addressed.

When there are no projects/builds/jobs, the different views within Kashti should reflect that by showing empty state messages

• state that there are no contents (instead of blank page)
• advise how to add contents (link to the docs on configuring brigade)

Right now, user icon does not represent a real user.

If we add OAuth support, flesh this out.

If not, delete this button

On a build listing page, add the date to the columns

Might also show something in the build list to point that out (e.g. grey out items that don't have logs)

instead of completing #34 for MVP, let's simplify and reduce the cotent in the left nav to reflect active providers

• update left nav icon
• change title
• change favicon

Things like URLs might be links, keywords like FAIL are highlighted red, etc.

• IP
• Docker image registry address
• Slack-like output

Right now, the cards on the main page have state (green check) hard-coded. Should switch to use latest build

Access and display info from active jobs in the UI.
Using the ?stream=true API query.

/job/id/logs
/task/id/logs

Replace brigade.js content with project configuration data

Make sure we can talk to an API server that is SSL-protected

So that it's easy to say "this project is currently in state..."

• placeholders as $http GET fetches content
• optimize UI assets for quicker pageload (use UnCSS)

See angular-loading-bar.