Switch branches/tags
Nothing to show
Commits on Feb 13, 2018
  1. Fix a running investigated build being shown above uninvestigated one…

    zlamma committed Feb 13, 2018
    …s - not the best choice if we want things attended to quickly
    Fixed by making the horrible ternary expression abominable. One day should rewrite this into a nice ordered list of all combinations that anyone can easily change... one day...
  2. Fix: failed build that was still running was showing in grey

    zlamma committed Feb 13, 2018
    Fix by showing the appropriate red (uninvestigated) or orageish (investigated)
Commits on Feb 10, 2018
  1. Use latest REST API - 2017.2

    zlamma committed Jan 24, 2018
    There seem to be no breaking changes to our usage:
  2. Fix not showing assignee when he hasn't got name defined - fix by sho…

    zlamma committed Feb 9, 2018
    …wing 'username' in that case
  3. Show 'failed to start' builds too - they're actually very important

    zlamma committed Jan 29, 2018
    (BTW, strangely enough, TeamCity doesn't allow investigation on these)
    Use a queryString filter as per [doc](
  4. Give the tab a title that is probably a bit more helpful and also mea…

    zlamma committed Jan 28, 2018
    …ningful, even to laypeople
  5. Filter out situations when a configuration used to use a branch speci…

    zlamma committed Jan 24, 2018
    …fication, but then changed into a 'no branch' (e.g. changed into one that only has dependencies on other configurations)
  6. Terser readme, just link to where the images/sounds can be customized…

    zlamma committed Feb 9, 2018
    … in the features list, and remove the related section
Commits on Feb 9, 2018
  1. Change project title in readme - just "Radiator for TeamCity" to keep…

    zlamma committed Feb 9, 2018
    … the base organization-agnostic
Commits on Feb 25, 2016
Commits on Feb 9, 2016
Commits on Feb 6, 2016
  1. Update screenshot

    zlamma committed Feb 6, 2016
  2. Fixed: When a build had no investigator but an investigation comment …

    zlamma committed Feb 6, 2016
    …it would put it in the list under non-investigated ones
    Similar thing to how we started to support this situation in 74474a4
  3. Add links to build and job

    zlamma committed Feb 6, 2016
  4. Make the shadow in text that appears over image slightly thicker, as …

    zlamma committed Feb 6, 2016
    …it was very thin on smaller fonts
  5. Only apply TravCorp's branch filters when the TeamCity we are connect…

    zlamma committed Feb 6, 2016
    …ing to is that of TravCorp (otherwise public users just checking how our radiator works with their TC would see no builds)
    Fix by grouping TTC's settings into 'organizationSettings' and put them in front, because they're pretty much the most frequently updated part of the file.
  6. Don't cause everything to reload when adding/removing browser instanc…

    zlamma committed Feb 6, 2016
    …e specific filter (by right click)
    Fixed by moving `branchFromApi.builds = getBuildsForBranchObservable()` before the filters get applied, so that they don't rerun on filters collection change, and extracting a mainBuildUrl computed to only fire mainBuild when it changed.
Commits on Feb 5, 2016
  1. When someone gives up investigation, don't show him as investigator a…

    zlamma authored and slawomir-brzezinski-at-travcorp committed Feb 4, 2016
    …nymore. Still show a comment.
    (turns out that TC returns him as still assigned, just the status is 'GIVEN_UP')
Commits on Feb 4, 2016
  1. Add refreshing of investigations on the main picture (before they onl…

    zlamma committed Feb 4, 2016
    …y refreshed on whole page reload; the refresh of investigation indicators on the list did work)
  2. Fixes #7 - the big picture showing success sometimes, when there is o…

    zlamma committed Feb 4, 2016
    …ne failed build on the list
     - the problem was that the mainBuild computed fired the ajax request twice, due to reliance on two computed observables - self.builds() and self.isFirstLoad() - when the isFirstLoad() triggered the update, the builds() list was not updated yet with the failed build, so it was actually making the ajax request for the second build. Only after that, the proper request for the failure would come, but, depending on luck, the success response would come first.
       Fixed this one by making the build rely on allBuildsOfAllProjectsOrPlaceholders intead of self.builds(), because that one is also the basis of self.isFirstLoad(), so when mainBuild fires, it already has the right build info.
     - By the way cleanup - remove old code that prevented refreshing the big picture, which stopped making sense when we started to present changes and investigations - these should be refreshed always.
    (I realize this complexity should be unravelled one day, but the codebase was already in quite a bad state when we forked it. Perhaps one day, time permitting I'll make it much more understandable).
Commits on Jan 27, 2016
  1. Ignoring the Nightly integration tests

    matthew.sleeman matthew.sleeman
    matthew.sleeman authored and matthew.sleeman committed Jan 27, 2016
  2. Ignoring iTropics Dev deploy and nightly integration tests until thes…

    matthew.sleeman matthew.sleeman
    matthew.sleeman authored and matthew.sleeman committed Jan 27, 2016
    …e environments have been rebuilt
Commits on Jan 24, 2016
Commits on Jan 21, 2016
  1. When a build is running, don't triumph yet. Look for the previous one…

    zlamma committed Jan 21, 2016
    …, it could be red. (Fixes #4)
  2. Don't break the whole refreshing when encountered an error with a sin…

    zlamma committed Jan 21, 2016
    …gle request (Fixes #3)
     - BTW, instead of showing instructions on how to set up the app, introduced a simple 'connection down' error, with a live 'last checked' information
Commits on Jan 20, 2016