James Strachan
James Strachan
So that we can know when a fix goes into production & can then comment on issues etc
Would be nice to periodically query the Elasticsearch logs for exceptions & report them to a SaaS endpoint so that they can be turned into issues & increase feedback &...
When folks run fabric8 on custom clusters we would benefit from feedback on how users are using it such as which quickstarts are used, number of releases etc Needs to...
e.g. a typical on premise install will be to have a jenkins master per team but a shared nexus
so kinda like fabric8-init-tenant but for the core saas services
add the following: * nexus * logging + metrics (elasticsearch + prometheus + grafana etc) * sonarqube * hubot mattermost * mattermost * gitcollector * gitea/gogs * hubot-notifier * chaos...
that has a blank Dockerfile, Jenkinsfile and a pom.xml to make the fabric8 YAML stuff; so that folks can quickly spin up new apps
which we can then use to help demo service discovery, high availability, readiness checks etc like the @davsclaus demo he's done lately with 2 microservices
it'd be great to be able to generate a list of all the issues that have been fixed by an individual fabric8-platform release (based on all the issues from kube...