Note: There is a [known issue](https://github.com/mixonic/ember-cli-deprecation-workflow/issues/30) with a deprecation warning coming from
...wait for it... ember-cli-deprecation-workflow.
Otherwise, this simply bumps the necessary dependencies (suggested by
the new generators) and makes the project conform to the minimal changes
in import syntax.
An [issue](https://github.com/travis-ci/travis-ci/issues/5181) was reported in
which the repository sidebar links were not functioning properly. I've
tracked it down to the fact that a click handler was registered and
automatically performing a redirect to the repo route.
This breaks CMD+Click behavior (as the click handler was still
called and navigating when the user did not expect it, as well as
navigated to a link that the user did not intend to visit.
This commit simply removes that click handler. I checked the previous
coffee version of the file to gain more context on why it was initially
added, but unfortunately, it was simply added when the original
component was created, so I'm not sure what its use was.
When a user restarts a job, we should not try fetching the log again. In
order to do this I added a guard in job-log component, which checks if
attributes changed in didReceiveAttrs callback. If the old job value is
the same as the new value, we don't need to do anything.
The use of `resource` within the router is deprecated as of 2.0.0.
See notice [here](https://github.com/emberjs/ember.js/pull/11517).
This uses ember-watson to do the manual conversion, with small
aesthetic tweaks.
Upgading ember-cli-autoprefixer to 0.5.0 removes the deprecation
messages from the build output (these were targeted for removal
in 0.4.0).
There are no noticable side effects, but this version does package
the most recent version of postcss/autoprefixer. The release notes
for that version can be found
[here](https://github.com/postcss/autoprefixer/releases/tag/6.0.0).
Sample of using the `time` element instead of `abbr` for displaying timestamps.
The `time` element can also represent durations. So the sample used here is suboptimal. Rather than the duration time lising the `lastBuildStartedAt` time in the `datetime` attribute, it ought to be a [valid `duration` value](https://www.w3.org/html/wg/drafts/html/master/infrastructure.html#valid-duration-string). However, I didn't see any existing helpers for formatting according to a machine-readable duration value.
