First time I m facing this issue. When I try committing my project. I face issue like beloow
svn: Working copy '/Users/administrator/Documents/Checkout/Mar 26 6.23 pm/XXX.xcodeproj' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
My project is as noted as locked. What would be the issue? Tried in internet noting works out.
How can I remove locked state?
if I try clean SVN it shows error like
$svn cleanup
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: Working copy '/Users/administrator/Documents/Checkout/Mar 26 6.23 pm' is too old (format 10, created by Subversion 1.6)
sometimes when svn found the files inn working copy are not intended for committing to svn tool will lock such files and user have to release the lock before committing it.
Related
I am building with TFS 2017. I am currently receiving this in my log:
[error]Core\Install\CSharp.nuget\NuGet.targets(87,9): Error : Unable to find version '9.0.1' of package 'Newtonsoft.Json'.
as well as some other packages. Immediately following, I have this:
[error]Core\Install\CSharp.nuget\NuGet.targets(87,9): Error MSB3073: The command ""E:\agent01\31\s\Core\Install\CSharp.nuget\nuget.exe" install "E:\agent01\31\s\Core\Source\Core.PackageReference\packages.config" -source "" -RequireConsent -solutionDir "E:\agent01\31\s\Core\Install\CSharp\ "" exited with code 1.
I am only switching builds from 2013 to 2017 and know that they should work without going inside of config files and changing anything. The only changes I should have to worry about are with the build machine or in the tasks I've created for this build. I was wondering what potential solutions someone may have.
I have a nuget restore task and all of the correct solutions are being built.
Looking in to my nuget restore task, I see near the bottom:
Adding package 'Newtonsoft.Json.9.0.1' to folder 'E:\agent02\12\s\Core\Source\packages'
The issue I found was with the build task. I had sent it to an output directory and that had caused the error.
I am having issues using Maven's: mvn dependency:purge-local-repository command.
I have several versions of a project and would like to remove certain versions.
I am running the command:
mvn dependency:purge-local-repository -DactTransitively=false -DreResolve=false -DresolutionFuzziness=version
The command runs with success but nothing is purged(deleted) from my local .m2 repository.
I have closely watched the windows explorer while the command runs, and I see items being deleted, repopulated, and deleted again, but in the end nothing has changed and the same files I wanted gone remain.
Can anyone explain what I am missing, or not fully understanding of how to use the tool?
thanks,
Cameron
i've setup my own jenkins buildserver today on my windows PC to build commits to my bitbucket.org-repository automatically.
Sadly i'm deep in trouble with the conenction between jenkins and git.
This is my Jenkis-Git configuration:
This is the Jobconfiguration:
If i now run "Build now" i'm getting the following output in console:
I hope somebody here is abled to help me with this problem. The Job is building... and building... and building... no result.
Kind regards,
Daniel
I get these Git-related warnings as well, but Jenkins is working just fine for me. I believe that they can be ignored. There is an open issue about this.
confirm you do indeed have Git installed on your system. try again.
If still having issue, you may need to also add the path of the Git executable to your Node configuration. By going to your Node configuration page, 'Node Properties' section, 'Tools Locations' setting. There you will find an option to explicitly add the path to Git.
I'm trying to 'release' my project using the gradle release-plugin
The plugin starts by checking if my working copy is clean, so that only properly versioned stuff gets released.
This works just fine on my local machine. But when I try the same thing in a Jenkins job, the build fails complaining various stuff is changed in the workplace. I decided that a lot of stuff was just internally used by jenkins and added it to gitignore:
caches/
native/
wrapper/
But it also considers gradlew as changed:
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':checkCommitNeeded'.
> You have uncommitted files:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
M gradlew
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Why does Jenkins change that file how do I prevent that?
I think the following settings on the Jenkins job might be relevant:
Checkout/merge to local branch (optional) is set to master. Without this setting the release plugin complains about not being on a branch
Clean after checkout is currently checked, but checking/unchecking it didn't make a difference
Make gradlew executable is checked, and at least to me sounds like a likely cause, but unchecking it makes the build faile because gradlew is not executable
Pretty old question, but for the record to anyone coming over here, jenkins isn't at fault here, you should commit gradlew with executable bit set:
# git update-index --chmod=+x gradlew
# git commit
Then you will no longer need the jenkins setting to set it executable, which is the workaround causing your issue.
I'm developing an iOS app with XCode 4.2 and latest SDK.
I have added to my project a folder with several files. This folder is a real folder in Finder.
When I try to commit those files I get the following message:
svn: Commit failed (details follow):
svn: '/Users/User1/Fuentes/iPhone/Desarrollos/TurismoCR2/TurismoCR2/Descripciones' is not under version control and is not part of the commit, yet its child '/Users/User1/Fuentes/iPhone/Desarrollos/TurismoCR2/TurismoCR2/Descripciones/021es.html' is part of the commit
How can I fix this error?
Probably I could add these files and folder manually but I don't know how (and I don't want to make a mistake).
You need to do:
cd /Users/User1/Fuentes/iPhone/Desarrollos/TurismoCR2/TurismoCR2
then:
svn add Descripciones/
Try this:
step 1:
svn ci
step 2:
Then vim or vi will be automatically offered by the svn (with svn diff file name) then type the required string or massage and save it.
Done.