fabric8-devops
fabric8-devops copied to clipboard
fabric8io
Contains the pluggable apps that can be run as part of the fabric8 DevOps platform on any OpenShift v3 or Kubernetes environment
I have deployed to a local kubernete when I create a project the url for git repo for gogs be like this http://gogs/gogsadmin/repo_name.git and the build always faild. why it...
Version used : 2.2.43 
In fabric8-devops/gogs/src/main/fabric8/gogs-git-secret.yml ``` namespace: "user-secrets-source-admin" ``` when trying to install it through helm this error appear: ``` $ helm install fabric8/gogs Error: release dandy-garfish failed: namespaces "user-secrets-source-admin" not found ```...
[INFO] F8: Starting S2I Java Build ..... [INFO] F8: S2I binary build detected [INFO] F8: Copying binaries from /tmp/src/maven to /deployments ... [INFO] F8: ... done [INFO] F8: [ERROR] Exec...
moved issue from: https://github.com/fabric8io/gofabric8/issues/304 I installed Gerrit using the one click deploy. Out of the box, it does not work because it is missing the "gerrit-admin-ssh" and "gerrit-users-ssh-keys". So it...
Currently some of the modules have been migrated to fabric8-maven-plugin v3 already, but still quite some are stuck on v2. This can be detected by a marker file `uses.fmp2` within...
it is unclear what a pattern is and what type of expressions are supported. Please improve the documentation around it. ideally the patter should be a regexp. so mariadb-ha-[0-9] should...
Our settings is pointing 'mvn deploy' to 'snapshots' rather then 'staging' ``` local-nexus::default::http://nexus/content/repositories/snapshots/ local-nexus::default::http://nexus/content/repositories/staging/ local-nexus::default::http://nexus/content/repositories/snapshots/ ``` should be ``` local-nexus::default::http://nexus/content/repositories/staging/ local-nexus::default::http://nexus/content/repositories/staging/ local-nexus::default::http://nexus/content/repositories/snapshots/ ``` https://github.com/fabric8io/jenkins-pipeline-library/issues/177
as there's no BuildConfig and the jenkinshift doesn't yet support watching so you get this: ``` Exception in thread "main" org.jboss.weld.exceptions.DeploymentException: Exception List with 1 exceptions: Exception 0 : io.fabric8.kubernetes.client.KubernetesClientException:...
The existing Keycloak kube app only supports http scheme and not https. By consequence, it can't be used in combination with Apiman/apiman-gateway as HTTPS & TLS is required