Lari,
Thank you for this work.
I have been following it very closely and I am happy that we are close
to be able to leverage it very soon.
What is the next step in order to apply these changes to the Pulsar repo ?
IIUC all of the changes that blocked you on building up this work have
been merged (
Thank you Yong for putting this together
+1 (non binding)
- Checked artifacts/checksums/signs
- Built from sources on JDK8/MacOs
- Run smoke tests on JDK8/MacOs
- Passed integration tests of DataStax Pulsar Cassandra Sink (using
Docker image)
- Passed internal system tests:
- including:
* Dock
This will be a great improvement. I read through the PIP, and overall, it
looks good to me.
I left a question on the doc about how concurrent runs affect the
repository's 5 GB cache limit.
I also think it could be helpful to explicitly document, or reference
github documentation, on how failure w
This is great news. Thanks Hari , Mateo and pulsar community
On Fri, Mar 12, 2021, 2:04 AM Lari Hotari wrote:
> Dear Pulsar community members,
>
> The work on "Changes to GitHub Actions based Pulsar CI" has gone forward
> based on your feedback. Here are some updates about the work.
>
> The draf
Dear Pulsar community members,
The work on "Changes to GitHub Actions based Pulsar CI" has gone forward
based on your feedback. Here are some updates about the work.
The draft PIP proposal document is here:
https://docs.google.com/document/d/1FNEWD3COdnNGMiryO9qBUW_83qtzAhqjDI5wwmPD-YE/edit#headi
Hi Yong, Yes, the files can be different in dev and releases directory, but
the artifact files prepared for releases should be signed using key exist
in both directories.
If PMC are vetting on release artifacts [1], including validating the
signature, it needs to use the same key to sign it.
Prefe
