1. 27 Nov, 2018 1 commit
  2. 14 Nov, 2018 2 commits
  3. 08 Nov, 2018 2 commits
  4. 05 Nov, 2018 2 commits
    • Leigh B Stoller's avatar
      Changes to how we handle/report mapping failures that also fail the · 11074445
      Leigh B Stoller authored
      empty testbed test.
      Prior to this commit, we were not invoking the empty testbed case
      consitently. Now we do, but that exposed another problem; reporting that
      to the error to the Portal in a meaningful way. Basically, we can report
      a different error code for an impossible to map error, but then we lose
      the info we store now about what the actual failure was (which we show
      to the user with additional helpful info). Since we cannot (easily)
      change the Geni API for CreateSliver(), I have elected to continue the
      practice of returning the specific error codes (which also go into the
      database for long term historical info), and add more helpful text that
      for the Portal user that explains clearly that the mapping is impossible
      on the target cluster. This extra text also go into the database in the
      attached message field, so we ccan come back later and post process if
      we decide to do something different.
    • Leigh B Stoller's avatar
  5. 30 Oct, 2018 1 commit
  6. 29 Oct, 2018 1 commit
  7. 26 Oct, 2018 2 commits
    • Leigh B Stoller's avatar
      Silence the email when the certificate does not verify, we tell the user · a249493d
      Leigh B Stoller authored
      that and point them to the Geni portal to fix it.
    • Leigh B Stoller's avatar
      Changes to repo based profiles: · c40bf355
      Leigh B Stoller authored
      * Respect default branch at the origin; gitlab/guthub allows you to set
        the default branch on repo, which we ignoring, always using master.
        Now, we ask the remote for the default branch when we clone/update the
        repo and set that locally.
        Like gitlab/guthub, mark the default branch in the branchlist with a
        "default" badge so the user knows.
      * Changes to the timer that is asking if the repohash has changed (via a
        push hook), this has a race in it, and I have solved part of it. It is
        not a serious problem, just a UI annoyance I am working on
        fixing. Added a cheesy mechanism to make sure the timer is not running
        at the same time the user clicks on Update().
  8. 24 Oct, 2018 1 commit
  9. 23 Oct, 2018 3 commits
  10. 11 Oct, 2018 1 commit
  11. 10 Oct, 2018 2 commits
  12. 08 Oct, 2018 1 commit
  13. 02 Oct, 2018 1 commit
  14. 01 Oct, 2018 2 commits
  15. 28 Sep, 2018 6 commits
  16. 27 Sep, 2018 1 commit
  17. 21 Sep, 2018 3 commits
  18. 19 Sep, 2018 3 commits
  19. 17 Sep, 2018 3 commits
  20. 14 Sep, 2018 2 commits