Re: Jenkins question
Luis Gomez <luis.gomez@...>
Thanks Andy for your quick answer.toggle quoted message Show quoted text
The question comes because we have different stuff in our git repo :
/distributions: this is what Ed created to build the controller release vehicles
/packaging: this was created to build linux packages such as rpm
/testcode: this will be created to store test code
Very soon we would like to trigger at least the following jobs:
Change in /distributions -> verify and merge jobs to build distributions, run system test, review code, merge to master and upload release artifacts to Nexus
Change in /packaging -> Not sure if this should trigger anything...
Change in /testcode -> verify and merge jobs to run system test with new code, review code and merge to master (no upload to Nexus needed for now, maybe later if we want to package the testcode for distribution)
Change (merge) in other OpenDaylight project -> csit job to build distributions, run system test and upload release artifacts to Nexus (we do not upload to Nexus if system test fails)
Does this make sense?
From: Andrew Grimberg [mailto:agrimberg@...]
Sent: Tuesday, November 05, 2013 12:01 PM
To: Luis Gomez
Cc: 'integration-dev@...'; 'infrastructure@...'
Subject: Re: [integration-dev] Jenkins question
On Tue, 2013-11-05 at 19:19 +0000, Luis Gomez wrote:
I have a question regarding Jenkins setup: if I create a branch in ourWhat jenkins builds is completely dependent up where it's pointing from
the git branch options as well as the gerrit path triggers.
So, yes, it's feasible to have different jobs for different branches or
even portions of branches.
Andrew J Grimberg
The Linux Foundation