error seen while trying to test connection
I am getting an error "Invalid input length 849" when I tried to test the connection with the Jira site in Jenkins. I tried to add the site in the Jenkins->configure system section using OAuth.But I can save it.
This is a known issue: https://issues.jenkins.io/browse/JENKINS-68495
Hope they will fix it a day or another...
Related
With Eclipse Che, I've recently been able to deploy the docker container without any issue as provided in the instructions.
I'm at the point where am trying to learn a bit more about extension development for Che, and I'm going through the small introduction on "developing your first plugin" located on the following page:
https://www.eclipse.org/che/docs/che-in-che-quickstart.html
I'm stuck at the point where I can successfully build and deploy the sample project by executing the Traefik Start, Tomcat8-IDE Start, Deploy IDE and Deploy Workspace Agent commands.
But when it comes time to navigate to the newly created 2nd workspace by clicking on the link provided in the IDE to go to the newly created 2nd workplace instance...:
... I end up getting redirected to the following error page:
I suspect that there may be some kind of configuration problem with the sample plugin project, or configuration problem with keycloak, but I'm at the point where I don't really know how to proceed in terms of troubleshooting.
(Update: 2018/07/31)
At request of #kalrsson for more information, below is a screenshot of the che-public client configuration in my Keycloak instance.
(SOLUTION Update: 2018/08/01)
Thanks to #kalrsson for pointing me in the right direction.
At first I tried only adding the needed URL to the "Valid Redirect URIs" list. Doing so allowed me to get past the issue were I was receiving the error "Invalid parameter: redirect_uri". However, this only presented me with a blank page. On this blank page, when I inspect the web browser console, I noticed the following error:
From there, I also tried to add the needed URL to WebOrigins in KeyCloak as seen below.
Doing this finally allowed me to fully load and render the secondary workspace
Can you go to keycloak_ip:5050/auth, login as admin/admin, clients, che-public, and the IP you use to redirect urls and webOrigins?
So, you need to previewURL:port both to redirectURIs and webOrigins
I used this link (create an Automated Build) from this guide.
The browser error console shows:
https://hub.docker.com/v2/repositories/github//autobuild/
Failed to load resource: the server responded with a status of 403 (FORBIDDEN)
I got this hint from https://github.com/docker/hub-feedback/issues/411#issuecomment-149878749
I replaced the following URL with my values.
https://hub.docker.com/add/automated-build/github/form/<GITHUB USER ID>/<GITHUB REPO NAME>/?namespace=<DOCKERHUB NAMESPACE>
This workaround has been outdated.
The url returns a 404.
Imho, this has to do with dockerhub changing some policies, concerning 'classic' autobuilds & company/user setup.
In my company we already use JIRA and plan to use Zephyr for JIRA for our Testmanagement.
In order to test the AddOn I created a JIRA-Cloud test-account.
Now I want to import some test-cases using the zfj-importer
When trying to connect with the tool, I get this error message:
I followed the steps in the Wiki, so I don't know why I get this error? Maybe somebody has had this before.
Thank you!
The issue was that I was trying to connect behind my company proxy.
Switching to a "normal" network worked for me.
I am trying to integrate the power bi report with our asp.net mvc application. So I found this https://azure.microsoft.com/en-us/documentation/articles/power-bi-embedded-get-started-sample/ article and followed the steps. I have successfully created the workspace collection and generated the access keys. And I downloaded this https://github.com/Azure-Samples/power-bi-embedded-integrate-report-into-web-app/ sample application as specified in the article and ran the ProvisionSample contsole application. I selected the 5th step and provided the appropriate values for workspace collection name and access key and it throws the following error "Operation returned an invalid status code 'Forbidden'". I looked at the audit logs and there is no error. Anyone have idea what causes for this issue?
There is an issue going on right now that is effecting some parts of the world. We are actively working on a fix.
I am trying to create a bot using OSX Server 4.0 and Xcode 6.4.
My project encompasses multiple repositories and uses additional libraries as submodules. When I go to "Product > Create Bot," A dialog appears, saying "Provide repository credentials for this bot."
The dialog shows all of the repositories which I use as submodules. If I attempt to authenticate them by either SSH or https, xcode rejects my credentials.
When I click "Ignore" and finish the setup process, it says "Bot creation failed with error: Internal Error Creating Bot" and gives me no other information.
As a test, I have successfully created a sample project in github which I can create a bot for without a problem. I have tried to add submodules to the sample project and it still can create bots fine.
Can anyone help fix this?
I figured out the answer.
The problem ended up being GitSlave (http://gitslave.sourceforge.net/) which my team was using to keep our repositories updated. Something about the way GitSlave set up the repositories causes Xcode bots to fail with an internal error.
My issues accessing the repositories were unrelated to the internal error and were fixed by creating a new set of SSH keys for the bot instead of using my personal SSH keys, which had different permissions.
Hope this helps anyone else having this problem!
I managed to get past the "provide credentials" dialog, but Xcode Bots would fail with the same "Internal Error Creating Bot" error once I had stepped all the way through the wizard and clicked "Create".
The solution in my case was to change the remote.origin.url setting for my repository from a git#github.com SSH URL to a https://github.com HTTPS URL, and suddenly it just worked.
(This is kind of maddening because I checked every log file and every place where there might be an error report and found nothing. Figured it out through trial and error)