RE: Any way to schedule a one time build?

[William Soula]

See this thread:

http://jenkins.361315.n4.nabble.com/Build-on-a-specific-date-time-trigger-td2542845.html

From the thread:

For example, the setting "30 9 21 11 *", should trigger the build on November 21st, at 9.30 am. 

Will

---

From: jenkins...@googlegroups.com [jenkins...@googlegroups.com] on behalf of Nathan Overbey [over...@gmail.com]
Sent: Friday, March 22, 2013 12:02 PM
To: jenkins...@googlegroups.com
Subject: Any way to schedule a one time build?

I know there's a cron type schedule with the option of "Build periodically".  However, I am hoping there is a way to schedule a build to run only one time at a specified date/time.  There is a button on the main page that is labeled "Schedule Build" however that seems to just kick off a immediate build.  Anyone know of a existing plugin or a way to do this with Jenkins?

--
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-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Ng, Jeff]

Here’s one way:  In the “Build Triggers” section, select “Trigger builds remotely”.  You can name the Authentication Token something like “ONE_TIME_BUILD”.  Jenkins will display a URL that you can call to trigger the build.  Then, you can trigger the build in many different ways (cron job, script, SCM hook, etc.).  If on unix, you should have the “wget” command. If on linux, try the “curl” command.

 

I have been using this method with a ClearCase UCM postop deliver_complete trigger that kicks off a dev build whenever someone completes a delivery.  Works great.

 

-Jeff Ng

[Hendy Irawan]

Actually there is a way:

https://myjenkins.ci.cloudbees.com/job/myjob/build?delay=2100sec

That means build 35 minutes from now.

It works on CloudBees. I'm not sure if it's working on vanilla Jenkins or if
it requires a plugin.

I also never see it on CloudBees interface. I just noticed that the "Build
Now" link has a ?delay=0sec parameter and I thought "hey, this is useful!"
so I put ?delay=Xsec in there and voila! It works.

SUPER USEFUL HIDDEN FEATURE if you feel me.

I definitely have no idea why it doesn't have a proper UI, i.e. a simple
text box inputting seconds or minutes would be sufficient.

I feel your pain.

Hendy



--
View this message in context: http://jenkins-ci.361315.n4.nabble.com/Any-way-to-schedule-a-one-time-build-tp4660205p4708068.html
Sent from the Jenkins users mailing list archive at Nabble.com.

[Hendy Irawan]

Actually there is a way: 

https://myjenkins.ci.cloudbees.com/job/myjob/build?delay=2100sec

That means build 35 minutes from now. 

It works on CloudBees. I'm not sure if it's working on vanilla Jenkins or if it requires a plugin. 

I also never see it on CloudBees interface. I just noticed that the "Build Now" link has a ?delay=0sec parameter and I thought "hey, this is useful!" so I put ?delay=Xsec in there and voila! It works. 

SUPER USEFUL HIDDEN FEATURE if you feel me. 

I definitely have no idea why it doesn't have a proper UI, i.e. a simple text box inputting seconds or minutes would be sufficient. 

I feel your pain. 

Hendy

On Tuesday, March 26, 2013 9:27:01 AM UTC+7, Nathan Overbey wrote:

Then nothing for a year and a half.

On Mar 25, 2013 10:22 PM, "Nathan Overbey" <over...@gmail.com> wrote:

When you have to do it again in two days then again 4 days from then and again 2 days later then again one day after that and then 5 days later then nothing for a week and then again 3 days after that its repetitive.  You feel me?

On Mar 25, 2013 10:15 PM, "Les Mikesell" <lesmi...@gmail.com> wrote:

On Mon, Mar 25, 2013 at 9:01 PM, Nathan Overbey <over...@gmail.com> wrote:
> Think 2:00am deployments.  I guess it could be manually disabled the next
> day (if one remembers).  Doing stuff manually is not what jenkins is all
> about though.  Its like asking why use jenkins and do all the repetitive
> tasks manually.

So you poll the scm at 2 am.    And don't commit a change to the
branch it polls until you want it to do the job again.   If it is
really a repetitive task.   Scheduling something to happen once isn't
what I'd call repetitive.

--
   Les Mikesell
     lesmi...@gmail.com

--
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/LPXPx_ftQZ0/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.