During the release-promotion mini-work-week in Toronto 16-20 Nov we agreed that we need a python-package cli-tool to play against taskcluster API in order to perform several operations for the tasks: cancel/rerun/report-as-completed. Later on, the implementation needs to be extrapolated to Ship-it in order to be able to control the aforementioned ops on the tasks there, directly from the UI. For the moment the tool ought to live as a python package (pypi | our own index, etc) for testing.
Assignee: nobody → mtabara
Finished wrapping the cli tool in a presentable form. Pypi index: https://pypi.python.org/pypi/tctalker Github repo: https://github.com/MihaiTabara/tctalker I'll mark the bug as Resolved-WORKSFORME until feedback/more instructions from Rail.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
Am adding Rail back to have a look on this.
Great job! I commented in https://github.com/MihaiTabara/tctalker/commit/ae8b899f6083def7585d990b6a7bc6cc965c2825#diff-01ab12d9e955aa832a81df09c3399ce2R131 - really minor issues. Ship it!
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
@Rail: I've pushed a commit that addresses the refactoring you have suggested: https://github.com/MihaiTabara/tctalker/commit/9dc4663deca998b17761cfb224fd7533ec8d5343 Should you're okay with it - I'll push and bump another version here: https://pypi.python.org/pypi/tctalker Questions: 1. What now? Where is this supposed to be shipped? 2. Do you want the package in the Moz internal Pypi? 3. What are the next steps for this? I remember we were talking about integration with Ship-it. Do we track that work here or should we use another bug? Thanks!
(In reply to Mihai Tabara [:mtabara] from comment #4) > @Rail: I've pushed a commit that addresses the refactoring you have > suggested: > https://github.com/MihaiTabara/tctalker/commit/ > 9dc4663deca998b17761cfb224fd7533ec8d5343 > > Should you're okay with it - I'll push and bump another version here: > https://pypi.python.org/pypi/tctalker > > Questions: > 1. What now? Where is this supposed to be shipped? Maybe move under github.com/mozilla? > 2. Do you want the package in the Moz internal Pypi? Not right know. Probably we need to try using it first. > 3. What are the next steps for this? I remember we were talking about > integration with Ship-it. Do we track that work here or should we use > another bug? Maybe add some examples on how to use it? Ship-it integration would be the next phase. The idea is to add similar functionality using browser (JS), something similar to tools.taskcluster.net.
* improved README with examples: https://github.com/MihaiTabara/tctalker * bumped version for tctalker to cope with changes following review and discussing in this bug: https://pypi.python.org/pypi/tctalker * transferred the repo under @Mozilla Github Questions and follow-ups: * please move https://github.com/mozilla/tctalker under @mozilla/releng. Both me and Amy unsuccessfully struggled with it during this morning * since this package is fleeting till we deploy JS changes, should worry about adding python-related logistics (travis, tox and alike, etc)? * the JS part doesn't sound that complicated. with this package in the ship-it dependencies (after proper testing), we would need to add some Bootstrap buttons + JS functionality to glue them up. right? Let me know if you want to have a quick mtg over this to discuss the further steps. Thanks for the help.
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago → 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.