I'm working at a very small startup. A previous employee set up our SVN system. The SVN system is accessed through a URL of the type:
http://dxxx2:1080/subversion (works in a web browser)
This works fine for Tortoise. No problems there. I'm trying to write a batch file to to pull down a single trunk file into a Unit Test folder for testing. All of my attempts at accessing by using the above URL results in errors saying that the URL cannot be found. For example:
When I use the form:
svn checkout file:///subversion/Firmware/2-branches//02_Initializations.c
I receive the following:
C:\>checkout_target.bat
C:\>svn checkout file:///subversion/Firmware/2-branches//02_Initializations.c
svn: E180001: Unable to connect to a repository at URL 'file:///subversion/Firmware/2-branches/02_Initializations.c'
svn: E180001: Unable to open an ra_local session to URL
svn: E180001: Unable to open repository 'file:///subversion/Firmware/2-branches/02_Initializations.c'
When I use the form:
svn checkout http://dxxx2:1080/subversion/Firmware/2-branches/02_Initializations.c
I receive the following:
C:\>checkout_target.bat
C:\>svn checkout http://dxxx2:1080/subversion/Firmware/2-branches//02_Initializations.c
svn: E170000: URL 'http://dxxx2:1080/subversion/Firmware/2-branches/02_Initializations.c' doesn't exist
How do I access our SVN through a command-line command that doesn't balk at the URL or port number?
Or how do I find the local network address of our SVN server so that I can access through a script?
You must read SVN Book
You must understand SVN Book basics
After 1-2 you'll never use svn co with file-URL, only with directory-URL
svn checkout http://dxxx2:1080/subversion/Firmware/2-branches/02_Initializations.c will not work and must not work
svn checkout http://dxxx2:1080/subversion/Firmware/2-branches/ will work and must work
Related
I have created choice parameted using Extended Choice Parameter property files. When used locally jenkins sees file's path correctly and choices are visible, but when I use deployed version and try to get the property file from git repository it does not recognize the path.
I use pipeline script from SCM, pass credentials and connect with no problems. Jenkins file is read from git repository correctly.
Can the Extended Choice Paramters use git files? What is it's working directory? I don't know where the extension is looking for for this files.
I installed lfs plugin on gerrit server, but there are many error message on server.
ERROR com.googlesource.gerrit.plugins.lfs.locks.LfsLocksContext : Not authorized to perform operation verify lock on repository
Does anybody know what this error means, and how to fix it? I attempted to google this error, but didn't find any results.
By default, the Gerrit LFS plugin stores the Git LFS file lock information at the following directory:
$GERRIT_SITE/data/lfs/lfs_locks
Have you changed this directory using the "locks.directory" option in the "$GERRIT_SITE/etc/lfs.config" file? Verify if everything is OK with this option and with this directory.
For more info, see the "Global Plugin Settings" section here.
I have a local instance of Jenkins. I have previously tried storing the jenkins.yml in my system and giving its path on http://localhost:8080/configuration-as-code. This worked but I want to use a Gitlab repository to store the jenkins.yml file.
I have already tried giving the gitlab link of my jenkins.yml in the path or URL textbox. Some weird things happened, like
1. jenkins broke or huge error console
2. It reapplies the previous configuration(from system path)
jenkins:
systemMessage: "Hello, world"
Your problem as described: you want the job configuration to be saved in GIT and, when a build is triggered, the job should get the current stand of its configuration from there and then, run the build.
Maybe there is a kind of plug-in that does it for you, but I am not aware of any. Maybe anyone?
My suggestion is to define a pipeline job and use a declarative pipeline. It is a file, normally named Jenkinsfile that can be stored in GIT. In the Job, you define the GIT address and when you trigger a build, the file is got from GIT and executed.
There are several flaws in this: pipelines learning curve is not small, you are confronted with groovy (not XML!) and your current XML file is barelly useful.
Maybe someone shows up and tells us about new (for me) plugin that solves your problem using the configuration XML file. In the other hand, pipelines are such a beautyful feature that I encourage you to give it a try
I want to update Jenkins plugin via Artifactory.
Create a remote repo named Jenkins-update
Create a local repo named jenkins-update-center
Get the update-center.json from repo Jenkins-update to local and modify the URL from 'http://updates.jenkins-ci.org/' to my own URL 'https://artifacts.xxx.com/artifactory/Jenkins-update/' in update-center.json, then put update-center.json into local repo.
#!/bin/sh
curl -L -o /tmp/update-center.json http://localhost:8081/artifactory/Jenkins-update-cache/update-center.json
sed -i 's#http://updates.jenkins-ci.org/#https://artifacts.xxx.com/artifactory/Jenkins-update/#g' /tmp/update-center.json
curl -L -uuser:pass -T /tmp/update-center.json "http://localhost:8081/artifactory/jenkins-update-center/update-center.json"
Change the default update site from 'http://updates.jenkins-ci.org/' to 'https://artifacts.xxx.com/artifactory/jenkins-update-center/update-center.json' in Jenkins
There is an error 'SHA-512 digest mismatch: expected=49a22dc23f739a76623d10128b6803f79e0489de3ded0f1d01f3dfba4557136c7f318baaf4749a7713ec4b3f56633f2ac3afc4703e87d423ede029d68f84c74d in 'update site 'default''' when I click 'check now' button.
What should I do to make Jenkins update plugins from Artifactory?
Tkx
As soon as the content of update-center.json changed you need to re-generate "signature" section of this file.
For that you need to generate your key pair (see more details in How to create a local mirror of public Jenkins update site?)
Also you may use the following proposed approach :
there is probably a better way, by having a sandbox Jenkins on a system that has access to the internet. You update the server using the UI and then you can test that updated Jenkins thoroughly. When done, you just need to copy the war and hpi files over to your 'production' Jenkins. now you have even a nice process and QA in place.
Another way is to setup a transparent https proxy between your Jenkins and Artifactory server - in that case update-center.json will not change and signature verification should work fine.
With best regards,
Dmytro Gorbunov
As of 2023-01-10 there is a problem with making a mirror of the jenkins plugins on artifactory.
Artifactory documentation decribes only how to create a mirror: https://jfrog.com/knowledge-base/how-to-configure-artifactory-as-a-mirror-for-jenkins-plugins/
But this is not a complete solution. Because this leads to the situation when every plugin shall be manually updated. Having plugins with bunch of dependencies it is huge effort.
There is a need to generate a file: update-center.json
There is an internal jenkins tool to do this: https://github.com/jenkins-infra/update-center2, but documentation is poor and contains vague statements like:
With a few modifications it could easily be used to generate your corporate update center as well.
Without clear description, what shall be done.
I tried to follow steps and completely failed. Tool require some special environment variables, which are also not documented and so on.
So as of my experience mirroring jenkins plugins on artifactory is practically not possible. And honestly spoken, I would like to be wrong here.
i'm quite new in Jenkins. I would like to use the log parser plugin to parse the console output of jenkins.
Like the documentation explains I have to add a file, which is containing my parsing rules.
So there is my question:
How do i upload files to jenkins? Do they need to be located in the projects workspace? My workspace is connected with a git repository. So i have to commit that file?
For example the file /tmp/rules.txt how do i get the rules.txt in the /tmp/ folder (and which folder is it, the workspace/tmp or the /tmp/ of the server itself)?
Do I have to transfer it via ssh?
Thanks for help!
This file dont have to be in the projects workspace. You don't have to uploat it on Git. Just create file somewhere on the computer, where jenkins runs.
You must change Global Configuration (/jenkins/configure). There is a section "Console Output Parsing". In description you can put, for example, : "Rules1" and in "Parsing Rules File" - path. Then in each job you want to use this rules configure Post-build Actions -> Console output (build log) parsing.