I'm trying to integrate Telerik's NuGet repo on my local nexus repository (v. 3.2.0.01).
I've found this on the web, http://docs.telerik.com/aspnet-mvc/getting-started/nuget-install but so far no libraries are shown.
I created a new proxy type NuGet repo with the following:
url: https://nuget.telerik.com/nuget
checked the HTTP Authentication
type: username
and provided a valid username and password.
Don't see any errors. but don't see any assets either.
has anyone successfully integrated Telerik's NuGet with Nexus OSS?
thanks,
Related
I have posted my libre software GitLab project on Packagist, and this succeeded but Packagist indicates next to its name that it "Does not auto-update". It does not say how to make it so it automatically updates.
GitLab added official integration with Packagist so you just need to go to Integrations and enable it (or go directly to gitlab.com/[your-org]/[your-project]/services/packagist/edit) and enter your username and API token from your Packagist profile and everything is all set.
When I log into packagist.org I get this message on my packages:
This package is using the legacy GitHub service and will stop being auto-updated in early 2019. Please set up the new GitHub Hook for Packagist so that it keeps working in the future.
When I visit https://packagist.org/about#how-to-update-packages the instructions seem to be more talking about how to set it up from scratch then anything.
I'm already logged in and my GitHub account is already linked (do I need to unlink it and relink it?)
When I click on https://github.com/settings/connections/applications/a059f127e1c09c04aa5a I see the "Access public information (read-only)" has a green checkbox next to it.
When I check https://packagist.org/profile/ it doesn't say that they're not automatically sync'd. What it does say is "Legacy Auto-Update, Needs Attention".
The URL suggests you trigger a manual account sync "to have Packagist try to set up hooks on your account again". I'm assuming the way you make Packagist do a manual sync is by clicking the "Update" button. I tried that to no avail.
Any ideas?
You should take a look at this issue: https://github.com/composer/packagist/issues/907 - GitHub deprecated GitHub Services, which was previously used for integration with Packagist. Packagist should switch to GitHub app when you first login to Packagist using GitHub OAuth.
If you already have connected GitHub account to Packagist account, try to logout and login using GitHub - you will be asked about permissions, which allows to automatically setup webhooks for repositories. After this everything should update automatically.
In other case you can connect GitHub account to existing Packagist account on settings page.
We are testing out the new project badge URL's in version 7.1
As described in the release notes
The thought was to, e.g., include this in README's on github.
However, as our Sonarqube instance requires login, these URL's do not work.
Is there a workaround for this?
Or a feature planned to allow unauthorized access to badge URL's?
We've created a MMF to allow usage of badges on project that requires authentication : https://jira.sonarsource.com/browse/MMF-1178
Unfortunately there's no workaround nor ETA.
I use gerrit with Google Play Android Publisher Plugin the way it described in plugin tutorial on the plugin page.
.apk is signed and if I upload it via google play gui it uploads well.
When I try to upload it using gerrit i get en error. Log below:
Upload failed: The Google Service Account credential 'GooglePlayAPICredentials' has not been configured correctly.
Update the credential, ensuring that the required data have been entered, then try again
- No changes have been applied to the Google Play account
Build step 'Upload Android APK to Google Play' marked build as failure
Finished: FAILURE
For google play credentials i use p12 key with email that looks like
serviceaccountforgerrit#api-64****-*****8.iam.gserviceaccount.com
and the keyfile i got while generating the key on a page that looks like:
https://console.developers.google.com/permissions/serviceaccounts?project=api-64****-*****8
I have created a new service account with "Furnish a new private key" checkbox checked and P12 radiobutton selected.
I have also granted access to this key in google play developer console api settings
https://play.google.com/apps/publish/?dev_acc=*******#ApiAccessPlace
Service account have every permission possible.
What could be the problem?
I have a same issue, but I solve with change the Google oAuth plugin (dependency for Google Play publish plugin) from v0.4 to v0.3.
You can downgrade by install manualy.
Download here:
https://updates.jenkins-ci.org/download/plugins/google-oauth-plugin/
(this is a *.hpi file)
Manage Jenkins > Manage Plugins > Advanced > Upload plugin
It works for me.
As per János answer, Downgrade Google OAuth Credentials plugin to v0.3
Download here
Manage Jenkins > Manage Plugins > Advanced > Upload plugin
Downgrade Token Macro Plugin to 1.10
Download here
Manage Jenkins > Manage Plugins > Advanced > Upload plugin
Re-import your JSON into the credential store
Credentials > (select credential domain) > (find your google credential) > Click Update (toolbox icon) > Choose File > Select the JSON file you downloaded previously > Save
It's 2018 and unfortunately the issue still exists. The solutions from János answer and Andy Answer are correct.
Let me write down the working solution step by step in case if someone
already have the latest Google Play publish plugin installed.
Uninstall the Google OAuth Credentials plugin
Uninstall the Google Play publish plugin
Download and manually install the Google OAuth Credentials plugin Version v0.3 from here
Restart Jenkins to complete this installation
Download and manually install the Google Play publish plugin Version v1.5 from here
Download and manually install the token-macro plugin Version v1.10 from here
Now the error from Google Play publish plugin should have gone.
Update:
By following the mentioned procedure of downgrading the version numbers of certain plugins, you would loose the GIT section from you Jenkins Jobs. i.e: You would not be able to select the Git Branch for your Jenkins Job and the Polling to your Git Branch would stop.
I'm using SonarQube 4.5.4. The SonarQube's API documentation says that the POST api/projects/destroy method requires Administer System permission.
However, users having the Administer Project role can delete their projects via the web interface selecting the Deletion option in the Project Configuration menu.
Why can't "project administrators" use the API to delete the projects they administer? Or is there a way? I've tried and I got this error:
$ curl -u user:password -X POST "https://sonar.cpqd.com.br/api/projects/destroy?id=123456789"
{"err_code":401,"err_msg":"Unauthorized"}%
The link to the documentation you provide points to http://nemo.sonarqube.org/ which is running SonarQube 5.1, not the version you are using.
Fortunately, there is no change regarding permissions checks on the WS /api/projects/destroy between 4.5 and 5.1 and what you request is not implemented: Administer System permission is required, project administer permission is not enough.
In 5.2, this WS is replaced by WS /api/project/delete which requires 'Administer System' permission or 'Administer' permission on the project.