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?
Continuous Integration for different languages [closed]
Closed 9 years ago.
Continuous Integration for different languages [closed]
Closed 9 years ago.
Continuous Integration for different languages [closed]
Closed 9 years ago.
Scheduling a Jenkins job to only run integration test [closed]
Closed 9 years ago.
Scheduling a Jenkins job to only run integration test [closed]
Closed 9 years ago.
Scheduling a Jenkins job to only run integration test [closed]
Closed 9 years ago.
Why does Jenkins warn you if you tell it to check for changes every minute?
In the past when I’ve set up Jenkins to look for version control changes every second by using the cron format of “* * * * *” (or something like that). When you do this, it gives you a warning and asks if you meant to say something like once a day.
Conventions for revision control with Maven/Jenkins
For a software project I am working on, we have a ‘dev => QA => production’ methodology. That is, we create a release candidate (deployed to Artifactory), give it to QA (deploy to QA systems and a QA backend/application server) who takes a week or so to look at it, and if they it’s ok, we make a production release.
Conventions for revision control with Maven/Jenkins
For a software project I am working on, we have a ‘dev => QA => production’ methodology. That is, we create a release candidate (deployed to Artifactory), give it to QA (deploy to QA systems and a QA backend/application server) who takes a week or so to look at it, and if they it’s ok, we make a production release.