On Thu, Dec 5, 2013 at 11:59 AM, JR Cary <c...@txcorp.com> wrote:
>
>>
>> One option would be to use the build flow plugin where one job polls
>> the repository and starts the flow job, then the build flow job starts
>> all of the child jobs, passing parameters for the revision numbers.
>> Not sure even this will work for the svn externals unless they are
>> pointing to tags or peg revisions.
>>
> I see. Thanks for the suggestions!
For anything other than CI builds that just test 'works or not' and
revisions aren't all that critical, I'd recommend separately tagging
the components you are pulling in separately. That is, use tags or
peg revisions in your svn externals and whatever you use to check out
from git. That way each component can have its own
development/release scheduling without breaking your main programs
that use them.
--
Les Mikesell
lesmikes...@gmail.com
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
