-
Notifications
You must be signed in to change notification settings - Fork 930
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Openshift 4.2 and Gogs #133
Comments
Hi there, for me it worked to change the Deplyoment Config of the Gogs PostgreSQL Pod. I changed the name of the ImageStreamTag to: name: 'postgresql:9.6' . Then I started a new Rollout of the PostgreSQL DC and the GOGS DC. Maybe this workaround helps. cheeers, Daniel |
Thank you for the recommendation. I made the change and both Gogs pods are up and running. However, when I attempt a build, I get the following error (this ran OK in 4.1): Cloning the remote Git repository |
ok so it worked for me, but I had to add the route to gogs manually. Did you login to gogs? It might be that the user has not been created. I had to do this too. |
After some further debugging, I found the parameter DEPLOY_CHE was not being recognized by the oc new-app command in provision.sh. (see below). I created a backup of provision.sh and removed DEPLOY_CHE as a parameter from the oc new-app command. I re-ran provision.sh and it built all the components, fetched the code into gogs, and ran a successful build. Except now I don't have CHE as an IDE to edit the java code.
|
In OCP 4.2, Gogs is work for me but Project is not analyzed in SonarQube and show following message: |
Has anyone tried to deploy this on OCP 4.2? The Gogs pod will not stay running and fails. This works fine in 4.1.
--> Scaling gogs-1 to 1
error: update acceptor rejected gogs-1: pods for rc 'cicd-poc/gogs-1' took longer than 600 seconds to become available
Thanks,
John
The text was updated successfully, but these errors were encountered: