Hey everyone, I wanted to let you know that as part of the migration from
Jenkins to GitHub Actions we are going to start disabling Jenkins jobs if
they have a corresponding GitHub Actions job that has been running
successfully for a while. We are starting with Yi's PR here -
https://githu
at 11:14 AM Danny McCormick via dev <
dev@beam.apache.org> wrote:
> Hey everyone, I wanted to let you know that as part of the migration from
> Jenkins to GitHub Actions we are going to start disabling Jenkins jobs if
> they have a corresponding GitHub Actions job that h
gt;
>>>>>>>> To run a job that has been migrated manually, you can navigate to that
>>>>>>>> job in the Actions tab and click "run workflow". So for the website
>>>>>>>> publish job you would navigate to
>>>>>
abled on Jenkins:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> To run a job that has been migrated manually, you can navigate to
>>>>>>>> that job in the Actions tab and click "
Hi all,
We have shut down most tests in the Jenkins Load Tests and Performance
Tests categories [1, 2], as they have been migrated to GitHub Actions for a
while and are continuously publishing the metrics as expected. Please refer
to https://github.com/apache/beam/pull/29092 for these tests. Note
Not sure if it’s related but I see that, seems, all Jenkins jobs are stuck and
there is a big Build Queue on https://ci-beam.apache.org/
Random clicks on jobs show that “"All nodes of label ‘beam’ are offline”
message.
Is it known problem?
—
Alexey
> On 24 Oct 2023, at 21:50, Yi Hu via dev w
I don't think it's related. I noticed the problem half an hour ago; it
seems there's an expired cert on the Jenkins machines. I'm hoping
https://github.com/apache/beam/actions/runs/6786537134/job/18447281366 will
fix this since the IO-Datastores cert is the problematic piece I think (and
that has f
Hi Alexey,
> all Jenkins jobs are stuck and there is a big Build Queue on
https://ci-beam.apache.org/
This is not intentional. This is likely due to INFRA's routine Jenkins
upgrade on Nov 5 and caused this outage. Have created
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-25147?filte
Danny, Yi,
Thank you for taking care of this!
—
Alexey
> On 7 Nov 2023, at 17:10, Yi Hu via dev wrote:
>
> Hi Alexey,
>
> > all Jenkins jobs are stuck and there is a big Build Queue on
> > https://ci-beam.apache.org/
>
> This is not intentional. This is likely due to INFRA's routine Jenkins
Hi all,
Just another update that we have shutdown all precommit tests on Jenkins.
For now, the remaining tests running on Jenkins are PostCommit suites. They
are also exercised on GitHub Action, but cannot be triggered from a pull
request due to [1]. That said, once the blocker [1] is resolved, w
Hi,
I’ve just noticed that some workflows stopped sending metrics to Grafana with
an error “org.apache.beam.sdk.testutils.publishing.InfluxDBPublisher: Unable to
publish metrics due to error: Response code: 401. Reason: "unable to parse
authentication credentials”” (e.g. Nexmark, Tpcds).
Is i
Nevermind, it was an issue with InfluxDB credentials that perhaps appeared
during a transfer the workflows from Jenkins to GitHub actions.
I fixed this.
—
Alexey
> On 11 Dec 2023, at 17:56, Alexey Romanenko wrote:
>
> Hi,
>
> I’ve just noticed that some workflows stopped sending metrics to G
12 matches
Mail list logo
