Description of problem: we don't have a good section that explains more in depth different considerations in Job design. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: No plae where we can discuss the attributes and elements of jobs and why you would/would not include them. Expected results: Some place where we can. Additional info:
Does http://gerrit.beaker-project.org/#/c/1917/ cover this bug, or is the intention to add more stuff to that section?
This BZ definitely depends on that patch, but no, it only covers a very small part of it.
We need a concrete list of what information is missing. What other job features do we need to cover in this doc? Otherwise this bug is just a piece of string that will get ignored forever.
I think the intent of this was to effectively make a what looks like an 'Advanced users guide'. I'm sure there are various hacks and other customisations that people to do beaker jobs/tasks to get them to work just the way they need them, these even sometimes come up on the dev list. Capturing some of this information may be useful to others, if the tricks that are used may not otherwise be obvious. You're right though, that it is a piece of string, and is probably not that important.
What I'm looking for here is a concrete list of what those hacks and customisations are, that we want to document. Did you have any in mind when you filed the bug? Can you think of any now? If not, let's just close this bug. I agree that a section like what you are describing would be useful, but unless we have a concrete list of what it should include, there's not much point leaving this bug open.
(In reply to Dan Callaghan from comment #5) > What I'm looking for here is a concrete list of what those hacks and > customisations are, that we want to document. > Yes, a concrete list would be great. I think it would be fine if we just started with one or two things though. > Did you have any in mind when you filed the bug? Can you think of any now? > I can't remember the examples I had at the time. Here are a couple of things which I think could be good candidates though: See the the thread, "Is it possible to continue if 'rhts-sync-block' timeout", and "How to disable avc check for single result" Also, how about writing up how to try new versions of task packages without actually installing them in beaker (Although I guess we want to move towards git tasks anyway...). > If not, let's just close this bug. I agree that a section like what you are > describing would be useful, but unless we have a concrete list of what it > should include, there's not much point leaving this bug open. I think we have a couple of suitable examples that are concrete, are suitable, and we can think of a good way to design such a guide than I think it could be a good thing to create it. If you don't think any of these examples are worthwhile, then yes, let's close this bug and we can open another one if we do find better candidates.
Isn't this the kind of thing we decided made better sense to push people to Stack Overflow for?
Closing this one, since a) we still don't have a list b) Raymond isn't part of our team any more.