Re: Jenkins CI currently unavailable

Additionally to what Kenn said, we have some documentation here: https://cwiki.apache.org/confluence/display/BEAM/Jenkins+Tips Though, not sure how up-to-date it is. — Alexey > On 14 Jun 2022, at 16:42, Kenneth Knowles wrote: >

Re: Jenkins CI currently unavailable

The UI is https://ci-beam.apache.org/ and it is integrated with ASF's LDAP. I don't know if this URL is documented anywhere. Usage of the UI is standard Jenkins. You can select any job and click "build with parameters" and put in a git ref to build from. Kenn On Mon, Jun 13, 2022 at 5:54 PM

Re: Jenkins CI currently unavailable

I just also want to say that you can run the tests locally and have people believe you when you say they passed. It isn't as good as CI but it is better than nothing. I am referring to the case where you want to manually add a postcommit status to your PR. If you orchestrate with gradle then you

Re: Jenkins CI currently unavailable

Logged in as a Committer, You need to open the configuration menu for the task, add in a string parameter for 'ghprPullId'. Save. Then you can go to Build With Parameters, populate the new field with the PR number And the sha1 with origin/pr//merge The you can kick off the job. It doesn't

Re: Jenkins CI currently unavailable

You know, I do forget that committers can manually trigger Jenkins runs. And after fiddling with the Jenkins options and filling in the expected, but missing PR number parameter i think I've managed it. Thanks for the reminder! On Mon, Jun 13, 2022, 3:38 PM Kiley Sok wrote: > Can you run the

Re: Jenkins CI currently unavailable

There are a couple of Go SDK PRs that are basically blocked on final manual runs of the post commits, that we'd like to get in for the 2.40 cut. Are we intending on delaying the 2.40 cut a little bit so PRs like those can make it in? On Mon, Jun 13, 2022, 1:32 PM Ahmet Altay wrote: > Thank

Re: Jenkins CI currently unavailable

Yes, the ghprb plugin was disabled. That was the entire action. I believe my PR will reduce the load caused by the ghprb plugin; we are currently restarting Jenkins to re-enable it. So we can unfreeze master as soon as Jenkins reboots. Basically, if your PR has a precommit status great, otherwise

Re: Jenkins CI currently unavailable

I definitely think we should freeze until we have precommits re-enabled. We have a hypothesis that https://github.com/apache/beam/pull/21821 may reduce the impact on the Jenkins master. We would lose phrase triggering on postcommits, but we would still have it on precommits for retriggering after