On Tue, Mar 15, 2016 at 11:00 AM, Niels de Vos <ndevos at redhat.com> wrote: > On Tue, Mar 15, 2016 at 10:25:19AM +0200, Arie Bregman wrote: >> On Tue, Mar 15, 2016 at 10:06 AM, Niels de Vos <ndevos at redhat.com> wrote: >> > Hi, >> > >> > I would like to run a Jenkins job on a regular schedule, and this job >> > should run with different CentOS and Gluster versions. It is easy to >> > write the job and pass the different environment. This works fine for >> > manual execution with the Jenkins web interface >> > >> > Now, is there a trick or job-type in Jenkins that I can use to setup a >> > schedule *and* pass different environment parameters for different >> > times? >> > >> > The workaround would be to create multiple Jenkins jobs with different >> > default parameters... But I do not think that is a very elegant >> > solution. >> >> You may want to look into Dynamic Parameter plugin[1] >> >> Anther workaround (or solution?) would be to check the time by >> yourself in 'virtualenv builder'/shell and set the parameters >> accordingly. > > Oh, thanks for the idea. Doing something time based would be an option, Isn't time based is what you wanted? "pass different environment parameters for different times?" > but jobs may get delayed if the slave is busy. Maybe it is not exactly a > reliable solution? Jobs may get delayed in any case, whether it's one job scheduled for different hours or multiple jobs that call one job. This is probably the easier solution to maintain. > > I might take this approach if there are no other suggestions. > > Niels > >> >> [1] https://wiki.jenkins-ci.org/display/JENKINS/Dynamic+Parameter+Plug-in >> >> > >> > Thanks, >> > Niels >> > _______________________________________________ >> > Ci-users mailing list >> > Ci-users at centos.org >> > https://lists.centos.org/mailman/listinfo/ci-users