Sorry about that and thanks Gordon for fixing this!

Best,
Kurt


On Mon, Jul 15, 2019 at 5:43 PM Tzu-Li (Gordon) Tai <tzuli...@apache.org>
wrote:

> Done.
>
> Thanks for the reminder and help with the Jenkins deployment setup!
>
> Cheers,
> Gordon
>
> On Mon, Jul 15, 2019 at 3:54 PM Chesnay Schepler <ches...@apache.org>
> wrote:
>
>> Please also setup the 1.9 travis cron branch.
>>
>> On 15/07/2019 09:46, Chesnay Schepler wrote:
>> > It is documented in the release guide that a new jenkins deployment
>> > must be setup when creating a new release branch, and even contains
>> > step-by-step instructions for doing so.
>> >
>> > @Kurt @Gordon please fix this
>> >
>> > On 12/07/2019 20:10, Yu Li wrote:
>> >> Hi All,
>> >>
>> >> I just found our flink benchmark Jenkins build [1] is broken with below
>> >> error:
>> >>
>> >> *[ERROR] Failed to execute goal on project flink-hackathon-benchmarks:
>> >> Could not resolve dependencies for project
>> >> org.apache.flink.benchmark:flink-hackathon-benchmarks:jar:0.1:
>> >> Failure to
>> >> find org.apache.flink:flink-tests_2.11:jar:tests:1.10-SNAPSHOT in
>> >> https://repository.apache.org/content/repositories/snapshots/
>> >> <https://repository.apache.org/content/repositories/snapshots/>*
>> >>
>> >> Which is due to the branching of 1.9 has updated our flink project
>> >> version
>> >> to 1.10 while still no 1.10 snapshot deployed yet. I tried to help
>> >> deploy
>> >> but it turned out with no access. Could anyone with the privilege help
>> >> deploy the snapshot for the new version? Thanks.
>> >>
>> >> What's more, no blame but to prevent such issue happen again, should we
>> >> document it somewhere that a deploy of snapshot is necessary when
>> >> branching
>> >> new releases and update the snapshot version?
>> >>
>> >> I've also opened an issue in our flink-benchmarks project [2].
>> >>
>> >> Thanks.
>> >>
>> >> [1] http://codespeed.dak8s.net:8080/job/flink-master-benchmarks/
>> >> [2] https://github.com/dataArtisans/flink-benchmarks/issues/28
>> >>
>> >> Best Regards,
>> >> Yu
>> >>
>> >
>> >
>>
>>

Reply via email to