Bamboo supports shared credentials.
I would like to use these shared credentials to commit tags to git using the artifactory maven addon.
According to this ticket: https://www.jfrog.com/jira/browse/BAP-189 it should work.
I do however not know where to configure it.
We are using bamboo 5.14.3.1
Artifactory plugin 2.1.0
Was this feature removed?
Related
We want to mirror PowerShell module repository in to our Artifactory instance as a Virtual repo, to have the ability to obtain needed modules from our Azure VM
Has any one done that before? Is there any documentation on how to mirror PowerShell modules into Artifactory?
I'm pulling my hair out. I've got an On Prem installation of Azure DevOps, and a pair of build agents. We're trying to move to .net core, but we have never been able to get it to work to push the nuget packages into DevOps feed. This should be straight forward.
The whole environment is hidden behind corporate firewall and proxy, and while the proxy config is good for nuget pull, and any other activity you care to name, we cannot invoke nuget push (or dotnet push) to our internal package repository. The only error I get is a 502 (bad gateway) from tunnel.js, but I've explicitly set the address of the DevOps server in NO_PROXY (environment variables, .proxy & .proxybypass for the devops agent, netsh winhttp proxy, build agent user internet connection settings, and %AppData%\Nuget\Nuget.Config file). Git works, nuget restore works, build works, packaging works, but the dotnet push (or nuget push) fail with this error.
Can anyone suggest any other places I might need to set a proxy bypass or no_proxy setting?
There can be many reasons why you are getting this problem, which may be related to your organization network, users roles and permissions or even task may be restricted by any policy.
But if above mentioned things are not true in your case then you should configure NuGet tools to authenticate with Azure Artifacts and other NuGet repositories. If all of the Azure Artifacts feeds you use are in the same organization as your pipeline, you can use the NuGetAuthenticate task without specifying any inputs. Check this Restore and push NuGet packages within your organization document for more information.
This task must run before you use a NuGet tool to restore or push packages to an authenticated package source such as Azure Artifacts. This task installs the Azure Artifacts Credential Provider into the NuGet plugins directory if it is not already installed.
If your agent is behind a web proxy, the NuGetAuthenticate will not set up nuget.exe, dotnet, and MSBuild to use the proxy. Then set the environment variable http_proxy and optionally no_proxy to your proxy settings as shown below.
nuget.exe config -set http_proxy=http://my.proxy.address:port
nuget.exe config -set http_proxy.user=mydomain\myUserName
Check this NuGet CLI environment variables for more information.
I am using on-prem JFrog Artifactory to hold maven artifacts. I have a need to use this artifactory to hold my app's docker images. So I tried creating a new docker repository but it showed me docker type as disabled. When I am looking around people are suggesting to use JFrog Container Registry.
My question is, can't I create a docker repository in my existing artifactory, does it require any plugin etc. to be downloaded to add this functionality in existing artifactory ? And how to enable that docker repository option while trying to create a new repository ?
Seems like you are using the Artifactory OSS version and not the Artifactory pro version, Artifactory OSS is limited as this an open-source version for the Maven-based projects. As everyone recommends you can make use of the JFrog container registry which is free to use application to handle the Docker registries.
Otherwise you can utilize the FREE Cloud Artifactory to handle all the different repositories in a single Artifactory instance.
I'm pretty new to jfrog artifactory. Is there a way to tell jfrog artifactory to POST to a custom endpoint/webhook whenever a new artifactory version of a repo is published? I'm trying to create a slack notification to my team whenever a new artifactory version is published. I've seen some examples with Artifactory pipelines but nothing very specific. Thanks!
Following the comment by Ortsigat, the support for webhooks was released as part of Artifactory 7.6. Webhooks can be managed via the web UI or the REST API.
You can read more about it in the Artifactory documentation.
https://docs.wso2.com/display/AM210/Upgrading+from+the+Previous+Release
I am following this to upgrade WSO2 API-M 2.0.0 to 2.1.0.
My 2.0.0 API-M has custom url configured and https certificates configured to map the url.
If i follow the migration as in the document , Will these things gets automatically migrated? Or will i have to manaully change the url in all the configuration files and also do the changes for https ?
I believe you are referring to [1] which is configuring custom URLs per tenant. If so you do not have to redo these configuration in the registry since the new deployment will be pointing to the same registry database as given in the migration documentation.
The changes done to configuration files in the file system, has to be re done in the APIM 2.1.0 pack. You can do a diff of the file system and do those changes.
The SSL certificates also have to be imported again. As an alternative, you can copy the keystores and truststores to the APIM 2.1.0 from the older version instead.
[]https://docs.wso2.com/display/AM200/Customize+the+API+Store+and+Gateway+URLs