Branch: refs/heads/production
  Home:   https://github.com/jenkins-infra/jenkins-infra
  Commit: 62b41c757dfe883bccff345f4b90cdcd49d4a3c6
      
https://github.com/jenkins-infra/jenkins-infra/commit/62b41c757dfe883bccff345f4b90cdcd49d4a3c6
  Author: R. Tyler Croy <[email protected]>
  Date:   2017-04-01 (Sat, 01 Apr 2017)

  Changed paths:
    M hieradata/common.yaml

  Log Message:
  -----------
  Use a proper 5.10.8 Confluence container


  Commit: 14e1ed4c03e46150feb0c8c78096fb9e805cfe33
      
https://github.com/jenkins-infra/jenkins-infra/commit/14e1ed4c03e46150feb0c8c78096fb9e805cfe33
  Author: R. Tyler Croy <[email protected]>
  Date:   2017-04-01 (Sat, 01 Apr 2017)

  Changed paths:
    M hieradata/common.yaml

  Log Message:
  -----------
  Use a 5.10.8 Confluence container with a newer mysql connector


  Commit: 8ab27dfc203927f54053bf5ed0eb020aca4295bf
      
https://github.com/jenkins-infra/jenkins-infra/commit/8ab27dfc203927f54053bf5ed0eb020aca4295bf
  Author: R. Tyler Croy <[email protected]>
  Date:   2017-04-01 (Sat, 01 Apr 2017)

  Changed paths:
    M hieradata/common.yaml

  Log Message:
  -----------
  Pin to 5.0.3 until we can figure out a suitable upgrade path to 6.1.0

The 5.10.8 upgrade wasn't as "drop-in" as I had hoped with our older DBs


  Commit: 744a5c090d7748f306c67b14b76fd9ef210a35c3
      
https://github.com/jenkins-infra/jenkins-infra/commit/744a5c090d7748f306c67b14b76fd9ef210a35c3
  Author: R. Tyler Croy <[email protected]>
  Date:   2017-04-01 (Sat, 01 Apr 2017)

  Changed paths:
    M hieradata/common.yaml

  Log Message:
  -----------
  Merge pull request #718 from jenkins-infra/staging

Pin to confluence 5.0.3 for now


Compare: 
https://github.com/jenkins-infra/jenkins-infra/compare/7a8c5be3c584...744a5c090d77

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to