How to get jenkins to build my code even if there are no changes -


i using jenkins matrix plugin testing project. have upstream, kick-off build fired of every night @ fixed time. build performs checkout , part 1 of tests. passes subversion url (svn_url) , revision (svn_revision) downstream build. downstream build uses passed in subversion url , revision checkout source (this way, know both upstream , downstream builds targeting same revision), , performs part 2 of tests.

the problem have downstream job doesn't run saying there no changes in checked out source since last build (no change since previous build). downstream build build every single time invoked, if there no changes. pointers on how that?

thanks

(edited in reponse question) detailed jobs description: 1. kickoff job. run periodically. captures svn_url , svn_revision. fires of part1-job , part2-job. not else. 2. part1-job , part2-job matrix jobs not have triggers on them. merely run kickoff job.

part2-job have problem. curiosly, problem mentioned above not happen part1-job.

you may find storing build output initial build , running downstream job based on artifact solution problem. i'm making assumptions here you're doing in initial , subsequent jobs, our experience might helpful.

for tests perform longer test after initial build & test successful, use artifact system store build results first build , retrieve @ beginning of next test execution. works particularly lengthy build processes may need more 1 test run in parallel.

for example, our system looked this:

  1. build task
  2. gui test on os x 10.6
  3. gui test on os x 10.7
  4. gui test on os x 10.8

initially, ran these serially (all in 1 big build task), changed our testing systems run gui tests in parallel , needed efficient way take build output specific job , run on each of test environments in parallel.

our new system runs this:

  1. build task post build action archive artifacts
  2. 3 different tasks each run gui tests in 1 environment, each of begins copying artifacts first build stage (using upstream build triggered job) , using artifacts execution targets test.

now our tests run in parallel , guaranteed use identical build. has added bonus each build run once.

as added bonus, reduced 3 tasks doing gui test single matrix task, that's not relevant purposes (however, it's sure saved lot of work us).


Comments

Popular posts from this blog

java - Jmockit String final length method mocking Issue -

asp.net - Razor Page Hosted on IIS 6 Fails Every Morning -

c++ - wxwidget compiling on windows command prompt -