+1 to writing a Beam Jenkins spellbook.
I have observed that Jenkins commands sometimes don't work for the first
time, why could this be? Do end of lines at the end of command matter?
On Thu, May 10, 2018 at 1:24 PM, Andrew Pilloud <apill...@google.com> wrote:
> It would be great to have the set of "Run {Java,Python,Go} PreCommit"
> documented in the contributors guide as well. Those match up to the jobs auto
> run on every PR and are the ones I use most. There is no security, anyone
> can run them including 'Run Seed Job'. That one seems like a good one to
> document in testing, because it is the one that loads changes to the rest.
>
> Andrew
>
> On Thu, May 10, 2018 at 12:27 PM Huygaa Batsaikhan <bat...@google.com>
> 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
>>
>
