Dynamic git URL for Jenkins builds
We internally use GitHub Enterprise and Jenkins. If I push on the main repository it is automatically build without and the Commit is marked as correct (just as Travis does this).
Dynamic git URL for Jenkins builds
We internally use GitHub Enterprise and Jenkins. If I push on the main repository it is automatically build without and the Commit is marked as correct (just as Travis does this).
Tomcat + Spring + CI workflow [closed]
Closed 9 years ago.
Where to audit a codebase for dangerous code use [closed]
Closed 9 years ago.
Where to audit a codebase for dangerous code use [closed]
Closed 9 years ago.
Where to audit a codebase for dangerous code use [closed]
Closed 9 years ago.
Where to audit a codebase for dangerous code use [closed]
Closed 9 years ago.
Where to audit a codebase for dangerous code use [closed]
Closed 9 years ago.
Where to audit a codebase for dangerous code use [closed]
Closed 9 years ago.
Is there some way to mark which branch is the latest in subversion?
We’re reworking our process with subversion at the moment, and one of the things we’re doing is making branches for each release target in our demo environment so that you can test a release that has been delayed independent of code that will be released separately. I am also experimenting with Jenkins in order to automatically run and report out on our unit tests in our demo environment. Is there some way in subversion to say “This branch is the release we’re testing at the moment” such that Jenkins will check out that branch to test it? If not, how should I be approaching this issue?