how to prevent the Spring cloud config server from cloning remote repo if the local repo already exists? - spring

I have a scenario where i wish the Spring cloud config server not the clone the git repo every time, if the repo already exists locally. i wish to clone only when there is a change in remote git repo. How do i configure the config-server in this case ?

Related

How can I get Xcode to remember my Git credentials?

Does anyone know how to get Xcode to remember Git credentials for a Git repository that is not hosted on Github or Bitbucket or Gitlab? My company uses Beanstalk.

How to deploy local maven repo to remote repo

I've a valid local maven repo which is generated by a closed-source tool. I'd like to deploy the full repo to a remote maven repo.
Any clues how to do this ?
If you can't scp or transfer up the repo another way, then I assume you'd have to write a script that would walk your local repo and put them all up using the deploy plugin.
https://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
If you're moving the whole repo up, I'd suggest to put it to an isolated repo so that it doesn't mix with other upstream repos like central.

Setup artifactory so that it's used for both caching an upstream Hadoop/HBase project & also provide build artifacts to our CI?

I'm getting started with Artifactory and am getting confused by all the terminology. What I'm trying to accomplish is the following:
$ git clone https://github.com/apache/hbase.git
$ cd hbase
$ git checkout branch-1.2
$ mvn clean install -DskipTests assembly:single
I'd like the git clone of this upstream project to live in Artifactory along with the components that Maven is pulling down. Additionally the final product zip file that mvn builds, hbase-assembly/target/hbase-1.1.6-bin.tar.gz, I want to store that in Artifactory too so that we can use it downstream in several CI jobs.
Questions
Is this approach correct?
How do I accomplish this?
Artifactory provides you with the Remote Repository functionality which you can also use to proxy various VCS services although I fail to see the point in just storing a clone of a git repo in Artifactory -
The VCS remotes are mainly used for cases where you directly include source code that you don't need to influence in your own code (i.e you can't git push changes back into Artifactory - they will not be persisted in the upstream git repo).
If you're aiming to have your CI job clone a certain branch, run tests, build it and then deploy build artifacts back to artifactory, I would suggest configuring your job to clone the git repo (using git not Artifactory) and then deploying the build artifacts back to Artifactory for downstream jobs to use.
Artifactory provides very extensive integration with popular build servers through which you can achive what's discussed here, your build artifacts should go into a Maven repository and the downstream jobs should reference it with their own pom files - you can quickly setup any Maven client to work with Artifactory using the Set Me Up dialog.

Nexus (proxy)Repository Connection pending on remote storage And 404 on repository acces

I have set up a sonatype Nexus 3.0.0-03. And trying to configure proxy repositories.
Problems:
the created repositories are not accessible. 404 If I just open repository URL.
The status in the repositories overview is on Online - Remote Connection Pending...
Type and Format of repository I have setup:
proxy, npm
proxy, nuget
proxy, maven
The goal is proxy the remote Nexus npm repository and use it as a npm registry.
Additional information:
I have no access to the settings of the remote Nexus, but as far as I understood this is not even necessary.
Accessing the remote repository with npm is possible.
I have already tried using npm install on created repository and it does not work. My Nexus is not fetching from remote Nexus' repository.
Solved by correcting the proxy settings.
Host was not reachable, because the companies Nexus is not reachable from outside of companies network, but inside of companies network.
I had to change no_proxy and NO_PROXY environment variables from *.company.com to .company.com
*.company.com won't work for nexus.company.com

Directly transferring a .pom file from local maven repo to remote repo

I have a maven "pom-only" artifact in my local repository (which is not built by me or my company , It was an very old one ). I want to transfer this to remote repository (our companies snapshot repository) . How do i do that .
I have following in my local repo under the version folder
****-1.8-SNAPSHOT.pom
****-1.8-SNAPSHOT.pom.sha1
How can i push both to remote repo. One of our project is dependent on this parent/Pom only artefact ?
The Web UI of your remote repository manager should provide functionality to upload/deploy artifacts manually. For Artifactory and Nexus I know for sure that they provide such.

Resources