action #33892

action #10316: [epic] Better command line options extending "client"

Allow the client to trigger a build for a jobgroup

Added by szarate almost 2 years ago. Updated almost 2 years ago.

Status:ResolvedStart date:27/03/2018
Priority:NormalDue date:
Assignee:mkittler% Done:

0%

Category:Feature requests
Target version:Done
Difficulty:
Duration:

Description

User story

As a test developer, I want to trigger or retrigger a build from a jobgroup, to ease posting jobs into openQA

Acceptance criteria

  • AC1: openQA::Client is able to trigger a build only for the specified jobgroup
  • AC2: Builds that were triggered in the normal way, are not obsoleted or canceled
  • AC3: Builds for a jobgroup that were previously scheduled can be handled in a similar fashion as other builds (Parameters, et al)

History

#1 Updated by okurz almost 2 years ago

  • Description updated (diff)

#2 Updated by okurz almost 2 years ago

I guess one can also describe it as restricted to a job group because the job group is merely a filtered part of a complete build spanning none to many job groups.

#3 Updated by szarate almost 2 years ago

  • Assignee deleted (szarate)

I haven't had too much chance to work on this.

Part #1: is to add simple re/trigger:
1. Query the Job Group and find the last job ids
2. Use TESTS parameter in isos post added here to trigger tests only for that jobgroup.

MM jobs need to be tested aswell.

Having a proper table for isos would be desirable, as this could help to better trace events, and simplify the needs of passing more and more parameters.

#4 Updated by mkittler almost 2 years ago

  • Assignee set to mkittler

#5 Updated by mkittler almost 2 years ago

The idea would be:

  1. Create an API route to get relevant job ideas. It would return a JSON array like this: [{id: 1}, {id: 2}, ...]. This route would be similar to the test results overview and should preferably share the code.
  2. Allow the client to restart all jobs returned by the new route.

@szarate Not sure why you always use the word 'trigger' and want to use the POST isos route. I talked with @coolo and this seems to be simply about restarting some jobs filtered by some criteria like on the test results overview page.

#6 Updated by szarate almost 2 years ago

@mkittler: Because that's how I was seeing it, specially if you take MM jobs into account.

Triggering jobs (isos posts) and retriggering/restarting which might be the part that coolo pointed you to.

Update de AC if you see it fit :)

#7 Updated by mkittler almost 2 years ago

  • Description updated (diff)

#8 Updated by mkittler almost 2 years ago

  • Status changed from New to In Progress

#9 Updated by coolo almost 2 years ago

hmm, now reading the user story - looks like we talked about a different problem. Oops :-)

#10 Updated by szarate almost 2 years ago

@coolo Happens :P but it's not entirely bad

#12 Updated by szarate almost 2 years ago

  • Status changed from In Progress to Resolved
  • Target version changed from Current Sprint to Done

Implemented feature complies with the AC. :)

Also available in: Atom PDF