When I create a new pipeline using the Blue Ocean plugin, even after I have properly configured the key pair and set up password-free login, as soon as I invoke the pipeline editor, it prompts me with the message "You need to register this public SSH key with your Git server to continue".
The problem may be due to the RSA SHA-1 public key that is generated by Blue Ocean. Many sites reject those public keys because they are no longer considered secure. It may be that gitlab.com rejects RSA SHA-1 public keys just as github.com does. Unfortunately, an RSA SHA-1 public key is the only type of public key that the Blue Ocean Pipeline editor will generate.
Blue Ocean is no longer being actively developed. Users should switch to Pipeline Graph View. Refer to the Blue Ocean status documentation where it says:
Blue Ocean will not receive further functionality updates. Blue Ocean will continue to provide easy-to-use Pipeline visualization, but it will not be enhanced further. It will only receive selective updates for significant security issues or functional defects.
Alternative options for Pipeline visualization, such as the Pipeline: Stage View and Pipeline Graph View plugins, are available and offer some of the same functionality. While not complete replacements for Blue Ocean, contributions are encouraged from the community for continued development of these plugins.
The Pipeline syntax snippet generator assists users as they define Pipeline steps with their arguments. It is the preferred tool for Jenkins Pipeline creation, as it provides online help for the Pipeline steps available in your Jenkins controller. It uses the plugins installed on your Jenkins controller to generate the Pipeline syntax. Refer to the Pipeline steps reference page for information on all available Pipeline steps.
Mark Waite
added a comment - The problem may be due to the RSA SHA-1 public key that is generated by Blue Ocean. Many sites reject those public keys because they are no longer considered secure. It may be that gitlab.com rejects RSA SHA-1 public keys just as github.com does. Unfortunately, an RSA SHA-1 public key is the only type of public key that the Blue Ocean Pipeline editor will generate.
Blue Ocean is no longer being actively developed. Users should switch to Pipeline Graph View. Refer to the Blue Ocean status documentation where it says:
Blue Ocean will not receive further functionality updates. Blue Ocean will continue to provide easy-to-use Pipeline visualization, but it will not be enhanced further. It will only receive selective updates for significant security issues or functional defects.
Alternative options for Pipeline visualization, such as the Pipeline: Stage View and Pipeline Graph View plugins, are available and offer some of the same functionality. While not complete replacements for Blue Ocean, contributions are encouraged from the community for continued development of these plugins.
The Pipeline syntax snippet generator assists users as they define Pipeline steps with their arguments. It is the preferred tool for Jenkins Pipeline creation, as it provides online help for the Pipeline steps available in your Jenkins controller. It uses the plugins installed on your Jenkins controller to generate the Pipeline syntax. Refer to the Pipeline steps reference page for information on all available Pipeline steps.
Unassigned
okkii
Votes:
0Vote for this issue
Watchers:
3Start watching this issue
Created:
Updated:
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
The problem may be due to the RSA SHA-1 public key that is generated by Blue Ocean. Many sites reject those public keys because they are no longer considered secure. It may be that gitlab.com rejects RSA SHA-1 public keys just as github.com does. Unfortunately, an RSA SHA-1 public key is the only type of public key that the Blue Ocean Pipeline editor will generate.
Blue Ocean is no longer being actively developed. Users should switch to Pipeline Graph View. Refer to the Blue Ocean status documentation where it says: