Funtoo JIRA

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options (Alt+g)
  • Structure Access more options (Alt+h)
Funtoo Linux
  • Funtoo Linux
  • FL-316 adding whenjobs
  • FL-338

Whenjobs userfeedback

  • Agile Board
  • Open Structure
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Sub-task Sub-task
  • Status: Closed Closed
  • Priority: Normal Normal
  • Resolution: Incomplete
  • Affects Version/s: None
  • Fix Version/s: None
  • Labels:
    None

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Commits
Hide
Permalink
Daniel Robbins added a comment - 18/Jan/13 11:05 PM

Whenjobs is a very interesting project and I am interested in having people test it out and evaluate it and tell Martin and me what you think about it.

Show
Daniel Robbins added a comment - 18/Jan/13 11:05 PM Whenjobs is a very interesting project and I am interested in having people test it out and evaluate it and tell Martin and me what you think about it.
Hide
Permalink
Jamie Learmonth added a comment - 19/Jan/13 9:34 AM

I've only had a quick read of the man page but it seems to be lacking a few features like "every day at 14:00" or "every monday at 3pm", or am I missing something?

Show
Jamie Learmonth added a comment - 19/Jan/13 9:34 AM I've only had a quick read of the man page but it seems to be lacking a few features like "every day at 14:00" or "every monday at 3pm", or am I missing something?
Hide
Permalink
Martin 'golodhrim' Scholz added a comment - 20/Jan/13 12:49 AM - edited

Jamie Learmonth that's what we want to figure out in testings, and why we asked for stuff like that, but a try of it should bring in clearing... The problem is that whenjobs is atm a very young project and perhaps we can improve it ourself or do it with help of Richard Jones from Red Hat, to get better support for us and him with whenjobs. as already added we have improved it with two own works in it... and we see what he says about them upstream later...

Show
Martin 'golodhrim' Scholz added a comment - 20/Jan/13 12:49 AM - edited Jamie Learmonth that's what we want to figure out in testings, and why we asked for stuff like that, but a try of it should bring in clearing... The problem is that whenjobs is atm a very young project and perhaps we can improve it ourself or do it with help of Richard Jones from Red Hat, to get better support for us and him with whenjobs. as already added we have improved it with two own works in it... and we see what he says about them upstream later...
Hide
Permalink
Martin 'golodhrim' Scholz added a comment - 20/Jan/13 11:26 PM - edited

Jamie Learmonth the solution for that is pretty simple if you play a bit with whenjobs and console scripts:

so here is how to get it work.

  1. Add a minute running script:
      every 1 minute :
          <<
          testtime=`date +%H%M`
          whenjobs --set --type int test=${testtime}
          >>
      
  2. Add a when clause:
      when test == 0017 :
          <<
          echo `date` >\> ~/test.log 
          >>
      

so the first job generates every minute a variable called testtime in the form of HHMM (HH=Hour(24h mode),MM=Minute) and sets this testime to a whenjobs-variable called test, finally our when clause checks for that test-whenjobs-variable and calles the code for it if test equals 0017 in the above case. so it runs every day at 00:17... playing with it brings the solution for it if you want a special one for a month job etc just add the needed output format to date and you are ready to run...

Hope that for first solves your question

Show
Martin 'golodhrim' Scholz added a comment - 20/Jan/13 11:26 PM - edited Jamie Learmonth the solution for that is pretty simple if you play a bit with whenjobs and console scripts: so here is how to get it work. Add a minute running script: every 1 minute : << testtime=`date +%H%M` whenjobs --set --type int test=${testtime} >> Add a when clause: when test == 0017 : << echo `date` >\> ~/test.log >> so the first job generates every minute a variable called testtime in the form of HHMM (HH=Hour(24h mode),MM=Minute) and sets this testime to a whenjobs-variable called test , finally our when clause checks for that test -whenjobs-variable and calles the code for it if test equals 0017 in the above case. so it runs every day at 00:17... playing with it brings the solution for it if you want a special one for a month job etc just add the needed output format to date and you are ready to run... Hope that for first solves your question
Hide
Permalink
Martin 'golodhrim' Scholz added a comment - 15/Feb/13 7:24 AM

as there is no big need for discussion of users as I saw, I close that bug too, cause the guide is online and I don't want to let the bug stay to long open...

Show
Martin 'golodhrim' Scholz added a comment - 15/Feb/13 7:24 AM as there is no big need for discussion of users as I saw, I close that bug too, cause the guide is online and I don't want to let the bug stay to long open...

People

  • Assignee:
    Martin 'golodhrim' Scholz
    Reporter:
    Martin 'golodhrim' Scholz
Vote (0)
Watch (3)

Dates

  • Created:
    18/Jan/13 10:55 PM
    Updated:
    15/Feb/13 7:24 AM
    Resolved:
    15/Feb/13 7:24 AM

Agile

  • View on Board
  • Atlassian JIRA (v5.2.5#847-sha1:7fd7dd6)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Funtoo Technologies. Try JIRA - bug tracking software for your team.