{"push_id":741623915,"size":1,"distinct_size":1,"ref":"refs/heads/jobparams","head":"243755ce09e616810c1950163e4f286552f5b6c6","before":"7356a6b11fcb929a9a7a782880828ef508d17d79","commits":[{"sha":"243755ce09e616810c1950163e4f286552f5b6c6","author":{"email":"60c6d277a8bd81de7fdde19201bf9c58a3df08f4@bandpage.com","name":"Alex Doronin"},"message":"[chronos] FE-7715. Update Chronos to allow to start a job with custom arguments\n\nSummary:\nThis is a follow-up work on https://github.com/mesos/chronos/pull/337. There was a commit (https://github.com/mesos/chronos/pull/360/files) that removed the ability to pass arguments to a force run (https://mesos.github.io/chronos/docs/api.html#manually-starting-a-job) while fixing the issue with `null` arguments (https://github.com/mesos/chronos/issues/355)\n\nCurrent commit re-introduces the \"custom arguments\" functionality in slightly different way: instead of passing optional query parameter one can pass extra arguments in JSON request body\n\nTest Plan: I tested the case with empty JSON payload to ensure there's no regression introduced similar to https://github.com/mesos/chronos/issues/355\n\nReviewers: adam, boris, josh, oscar, Reimertz, krishna, steve, chris\n\nDifferential Revision: https://phabricator.bandpagehq.com/D14515","distinct":true,"url":"https://api.github.com/repos/doronin/chronos/commits/243755ce09e616810c1950163e4f286552f5b6c6"}]}