You could create multiple parameters as suggested above for the number of
jobs that you would like to run. ie ${projectToBeRun}, ${projectToBeRun1},
${projectToBeRun2}
mark
On Friday, December 20, 2013 6:57:47 AM UTC-7, Steven Deal wrote:
>
> I'm not sure. One thing I would keep in mind is not to loose sight of
> automation. Normally, jobs are kicked off based on code changing in a
> repository or a upstream dependency. Jenkins is incredibly flexible, to the
> point of abuse (I'm guilty). There is nothing you can't do; in this
> example, I think you could make each of these jobs a boolean choice and
> when you kick off the job you are trying to create, you uncheck or check
> what you want to run. But again, I'd have to ask is this really what you
> want to do?
> hth,
> steven
>
>
> On Fri, Dec 20, 2013 at 8:22 AM, ibrahim deek
> <[email protected]<javascript:>
> > wrote:
>
>> Thanks Steven and Robert. I tried the solution you have mentioned and it
>> works fine.
>> But here I can chose only one job, and I want to select several
>> jobs/projects to build not only one, could you help in that?
>>
>> I appreciate your help.
>>
>> Regards,
>> Ibrahim
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-users/bbKHpolUtUE/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
