Opened 8 years ago

Last modified 22 months ago

#896 assigned project-idea

Replace try with a client for the force scheduler

Reported by: marcusl Owned by: verm
Priority: major Milestone: 0.9.+
Version: 0.8.0 Keywords: try, users, force
Cc: jachen, msorrenti@…, ffledgling@…, mikesorrenti@…

Description (last modified by dustin)

We have a "try" client defined which looks for a patch in a local repository on a developer's system, patches it up, and submits it to Buildbot. It's very ad-hoc, isn't very configurable, and hasn't gotten a lot of love.

Now that we have a force scheduler, the better solution is for the try client to talk to a force scheduler, preferably using HTTP. The client should also capture and send e-mail address of the submitter so that notifications can be sent.

This allows lots of flexibility on the master side: users can set up as many force schedulers as they like, with different builders, properties, permissions, and so on.

scope

To make this project a summer's worth, it should aim to implement:

  • a new try client
  • improved support for DVCS's, where patches aren't required, but where the client must send a repository
  • support in the master for sending force-build parameters to a force scheduler via an HTTP rest call
  • support for patches in the force scheduler
  • per-scheduler authentication/authorization
  • migration information for users of the existing try functionality

Change History (18)

comment:1 Changed 8 years ago by bhearsum

This is implementable through a MailNotifier? already, is there something beyond that that is desired?

comment:2 Changed 7 years ago by dustin

  • Keywords try added

bhearsum: the code change would be in sending an email address along with the try request (I think..)

comment:3 Changed 7 years ago by redheadphones

  • Keywords redheadphones added

comment:4 Changed 6 years ago by redheadphones

  • Keywords redheadphones removed

comment:5 Changed 6 years ago by dustin

  • Keywords users added

comment:6 Changed 5 years ago by tom.prince

  • Milestone changed from 0.8.+ to 0.8.8

comment:7 Changed 5 years ago by tom.prince

  • Keywords force added
  • Milestone changed from 0.8.8 to 0.8.+

The plan is to deprecate try, and replace it by an extended force scheduler.

comment:8 Changed 5 years ago by dustin

  • Description modified (diff)
  • Milestone changed from 0.8.+ to 0.9.+
  • Priority changed from minor to major
  • Summary changed from Try should capture and send e-mail address of the submitter so that notifications can be sent to Replace try with a client for the force scheduler
  • Type changed from enhancement to project-idea

comment:9 Changed 5 years ago by dustin

  • Description modified (diff)

comment:10 Changed 5 years ago by dustin

  • Description modified (diff)

comment:11 Changed 5 years ago by dustin

  • Cc jachen added

comment:12 Changed 5 years ago by mikesorrenti

  • Cc msorrenti@… added

comment:13 Changed 5 years ago by jachen

True. I wanted to use the try scheduler. But, seemed a lot of work for developers to set up, etc. Also not into setting up a bunch of user name/passwords to maintain this. Would prefer a loose general password for this type of stuff.

comment:13 Changed 5 years ago by jachen

True. I wanted to use the try scheduler. But, seemed a lot of work for developers to set up, etc. Also not into setting up a bunch of user name/passwords to maintain this. Would prefer a loose general password for this type of stuff.

comment:14 Changed 5 years ago by ffledgling

  • Cc ffledgling@… added

comment:15 Changed 5 years ago by mikesorrenti

  • Cc mikesorrenti@… added

comment:16 Changed 4 years ago by dustin

  • Description modified (diff)

comment:17 Changed 22 months ago by tardyp

  • Owner set to verm
  • Status changed from new to assigned

afaik, this project is worked on by verm

Note: See TracTickets for help on using tickets.