![]() ![]() I cant find any information about how to configure jenkins to checkoutīecause inverted order of actions used in CI. Jenkins - if you can use any repository URL with Jenkins (I know nothing about it), you can use tag URL, same way as any other URL of repository, but.For every branch/tag you always create "cheap copy" of source on conditional location (/branches and /tags are just most commonly used and accepted agreement) Taggins/branching in Subversion always path-based, you can not just add meta-information.You want to work with independent, unrelated to old, new, repo: just checkout new URL, don't reinvent the wheel.Nothing changed in tree, just for some reasons changed URL for the same point of code (svn://host/path repo changed to or changed hostname.): svn help relocate - svn relocate svn:///repo/project.You want to use another URL inside the same repo (branched /trunk to /branch/name server-side, want mirror this change in WC in order to work with your branch): svn help switch, 1-st form - svn switch ^/branches/1.x-release.When you speak about changing repository URL, you really mention 3 different cases:.In Subversion, unlike CVS, there's no difference in checking out a tag, a branch, or from the trunk: It's all just a URL of some sort. If you already have a Jenkins project under Subversion, you can copy the Jenkins job to a new job, and modify the URL that Jenkins uses to the tag's URL. ![]() However, this can be solved with a pre-commit trigger. The only issue is that tags cannot be locked, so people can checkout tags and modify them. You can even see if that tag has been modified and by who.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |