That's a good idea. It could be helpful. Regards JB
On 05/10/2018 09:34 PM, Ankur Goenka wrote: > These actions are documented in groovy scripts > like > https://github.com/apache/beam/blob/b7bfca9b196699a096786506777a49237e0b3776/.test-infra/jenkins/job_beam_PostCommit_Python_ValidatesContainer_Dataflow.groovy#L36 > We can create a tool which can just go over these scripts and print the > comments > eliminating the need to keep the document upto date. > > > On Thu, May 10, 2018 at 12:33 PM Kenneth Knowles <[email protected] > <mailto:[email protected]>> wrote: > > It seems extremely useful to have a concise catalog of these commands in > the > contribution guide. I think new contributors will perhaps not be reading > the > testing guide but just want Jenkins to do the work for them. > > Kenn > > On Thu, May 10, 2018 at 12:27 PM Huygaa Batsaikhan <[email protected] > <mailto:[email protected]>> wrote: > > Hi devs, > > We can run various jenkins commands (precommit, postcommit, > performance > tests) directly from Github Pull Request UI by commenting phrases such > as "retest this please". Unfortunately, this tool is not documented. I > am adding a brief documentation in > https://beam.apache.org/contribute/testing/ and I need some help. > > 1. What are the most common phrases used? > 2. Can anyone run these commands? Are there any permission issues? > 3. Does it make sense to categorize the commands as Performance > tests, > Precommit, Postcommit, and Release Validation? > > Let me know what you think, > > Thanks, > Huygaa > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
