Flink benchmark Jenkins is broken due to missing 1.10 snapshots

[Yu Li]

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

[Chesnay Schepler-3]

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
>

[Chesnay Schepler-3]

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
>>
>
>

[Tzu-Li (Gordon) Tai]

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 <[hidden email]> 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
> >>
> >
> >
>
>

[Kurt Young]

Sorry about that and thanks Gordon for fixing this!

Best,
Kurt


On Mon, Jul 15, 2019 at 5:43 PM Tzu-Li (Gordon) Tai <[hidden email]>
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 <[hidden email]>
> 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
>> >>
>> >
>> >
>>
>>

[Yu Li]

Thanks for the follow up Chesnay, Gordon and Kurt. It seems the
flink-tests_2.11 snapshot [1] is not deployed yet thus flink-benchmark
build [2] hasn't recovered, will watch for the next round and report back
if fixed.

[1]
https://repository.apache.org/content/repositories/snapshots/org/apache/flink/flink-tests_2.11/
[2] http://codespeed.dak8s.net:8080/job/flink-master-benchmarks/

Best Regards,
Yu


On Mon, 15 Jul 2019 at 18:25, Kurt Young <[hidden email]> wrote:

> Sorry about that and thanks Gordon for fixing this!
>
> Best,
> Kurt
>
>
> On Mon, Jul 15, 2019 at 5:43 PM Tzu-Li (Gordon) Tai <[hidden email]>
> 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 <[hidden email]>
>> 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
>>> >>
>>> >
>>> >
>>>
>>>

[Chesnay Schepler-3]

It will likely take about a day for the 1.10 snapshots to be released.

On 15/07/2019 12:41, Yu Li wrote:

> Thanks for the follow up Chesnay, Gordon and Kurt. It seems the
> flink-tests_2.11 snapshot [1] is not deployed yet thus flink-benchmark
> build [2] hasn't recovered, will watch for the next round and report back
> if fixed.
>
> [1]
> https://repository.apache.org/content/repositories/snapshots/org/apache/flink/flink-tests_2.11/
> [2] http://codespeed.dak8s.net:8080/job/flink-master-benchmarks/
>
> Best Regards,
> Yu
>
>
> On Mon, 15 Jul 2019 at 18:25, Kurt Young <[hidden email]> wrote:
>
>> Sorry about that and thanks Gordon for fixing this!
>>
>> Best,
>> Kurt
>>
>>
>> On Mon, Jul 15, 2019 at 5:43 PM Tzu-Li (Gordon) Tai <[hidden email]>
>> 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 <[hidden email]>
>>> 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
>>>>>>
>>>>>
>>>>

[Yu Li]

Thanks for the note Chesnay, will wait and report back then.

Best Regards,
Yu


On Mon, 15 Jul 2019 at 18:51, Chesnay Schepler <[hidden email]> wrote:

> It will likely take about a day for the 1.10 snapshots to be released.
>
> On 15/07/2019 12:41, Yu Li wrote:
> > Thanks for the follow up Chesnay, Gordon and Kurt. It seems the
> > flink-tests_2.11 snapshot [1] is not deployed yet thus flink-benchmark
> > build [2] hasn't recovered, will watch for the next round and report back
> > if fixed.
> >
> > [1]
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/flink/flink-tests_2.11/
> > [2] http://codespeed.dak8s.net:8080/job/flink-master-benchmarks/
> >
> > Best Regards,
> > Yu
> >
> >
> > On Mon, 15 Jul 2019 at 18:25, Kurt Young <[hidden email]> wrote:
> >
> >> Sorry about that and thanks Gordon for fixing this!
> >>
> >> Best,
> >> Kurt
> >>
> >>
> >> On Mon, Jul 15, 2019 at 5:43 PM Tzu-Li (Gordon) Tai <
> [hidden email]>
> >> 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 <[hidden email]>
> >>> 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
> >>>>>>
> >>>>>
> >>>>
>
>

[Haibo Sun]

 `flink-tests_2.11:jar:tests:1.10-SNAPSHOT` was not deployed because the JIRA (https://issues.apache.org/jira/browse/FLINK-12602) changed the `artifactId` of `flink-tests` from `flink-tests_${scala.binary.version}` to `flink-tests`.


I have created a PR (https://github.com/dataArtisans/flink-benchmarks/pull/29) to revise pom.xml of `flink-benchmarks` accordingly, and need someone to help merge it.  @Chesnay Schepler


Best,
Haobo


At 2019-07-15 19:01:57, "Yu Li" <[hidden email]> wrote:

>Thanks for the note Chesnay, will wait and report back then.
>
>Best Regards,
>Yu
>
>
>On Mon, 15 Jul 2019 at 18:51, Chesnay Schepler <[hidden email]> wrote:
>
>> It will likely take about a day for the 1.10 snapshots to be released.
>>
>> On 15/07/2019 12:41, Yu Li wrote:
>> > Thanks for the follow up Chesnay, Gordon and Kurt. It seems the
>> > flink-tests_2.11 snapshot [1] is not deployed yet thus flink-benchmark
>> > build [2] hasn't recovered, will watch for the next round and report back
>> > if fixed.
>> >
>> > [1]
>> >
>> https://repository.apache.org/content/repositories/snapshots/org/apache/flink/flink-tests_2.11/
>> > [2] http://codespeed.dak8s.net:8080/job/flink-master-benchmarks/
>> >
>> > Best Regards,
>> > Yu
>> >
>> >
>> > On Mon, 15 Jul 2019 at 18:25, Kurt Young <[hidden email]> wrote:
>> >
>> >> Sorry about that and thanks Gordon for fixing this!
>> >>
>> >> Best,
>> >> Kurt
>> >>
>> >>
>> >> On Mon, Jul 15, 2019 at 5:43 PM Tzu-Li (Gordon) Tai <
>> [hidden email]>
>> >> 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 <[hidden email]>
>> >>> 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
>> >>>>>>
>> >>>>>
>> >>>>
>>
>>

[Chesnay Schepler-3]

Done.

On 16/07/2019 12:47, Haibo Sun wrote:

>
>  `flink-tests_2.11:jar:tests:1.10-SNAPSHOT` was not deployed because
> the JIRA (https://issues.apache.org/jira/browse/FLINK-12602) changed
> the `artifactId` of `flink-tests` from
> `flink-tests_${scala.binary.version}` to `flink-tests`.
>
> I have created a PR
> (https://github.com/dataArtisans/flink-benchmarks/pull/29) to revise
> pom.xml of `flink-benchmarks` accordingly, and need someone to help
> merge it. @Chesnay Schepler
>
> Best,
> Haobo
> At 2019-07-15 19:01:57, "Yu Li" <[hidden email]> wrote:
> >Thanks for the note Chesnay, will wait and report back then.
> >
> >Best Regards,
> >Yu
> >
> >
> >On Mon, 15 Jul 2019 at 18:51, Chesnay Schepler <[hidden email]> wrote:
> >
> >> It will likely take about a day for the 1.10 snapshots to be released.
> >>
> >> On 15/07/2019 12:41, Yu Li wrote:
> >> > Thanks for the follow up Chesnay, Gordon and Kurt. It seems the
> >> > flink-tests_2.11 snapshot [1] is not deployed yet thus flink-benchmark
> >> > build [2] hasn't recovered, will watch for the next round and report back
> >> > if fixed.
> >> >
> >> > [1]
> >> >
> >> https://repository.apache.org/content/repositories/snapshots/org/apache/flink/flink-tests_2.11/
> >> > [2] http://codespeed.dak8s.net:8080/job/flink-master-benchmarks/
> >> >
> >> > Best Regards,
> >> > Yu
> >> >
> >> >
> >> > On Mon, 15 Jul 2019 at 18:25, Kurt Young <[hidden email]> wrote:
> >> >
> >> >> Sorry about that and thanks Gordon for fixing this!
> >> >>
> >> >> Best,
> >> >> Kurt
> >> >>
> >> >>
> >> >> On Mon, Jul 15, 2019 at 5:43 PM Tzu-Li (Gordon) Tai <
> >> [hidden email]>
> >> >> 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 <[hidden email]>
> >> >>> 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
> >> >>>>>>
> >> >>>>>
> >> >>>>
> >>
> >>

[Yu Li]

Thanks Haibo for the nice catch and Chesnay for the quick fix! I just
confirmed that flink-benchmark Jenkins is recovered and benchmark result
updated in codespeed center.

Best Regards,
Yu


On Tue, 16 Jul 2019 at 18:53, Chesnay Schepler <[hidden email]> wrote:

> Done.
>
> On 16/07/2019 12:47, Haibo Sun wrote:
> >
> >  `flink-tests_2.11:jar:tests:1.10-SNAPSHOT` was not deployed because
> > the JIRA (https://issues.apache.org/jira/browse/FLINK-12602) changed
> > the `artifactId` of `flink-tests` from
> > `flink-tests_${scala.binary.version}` to `flink-tests`.
> >
> > I have created a PR
> > (https://github.com/dataArtisans/flink-benchmarks/pull/29) to revise
> > pom.xml of `flink-benchmarks` accordingly, and need someone to help
> > merge it. @Chesnay Schepler
> >
> > Best,
> > Haobo
> > At 2019-07-15 19:01:57, "Yu Li" <[hidden email]> wrote:
> > >Thanks for the note Chesnay, will wait and report back then.
> > >
> > >Best Regards,
> > >Yu
> > >
> > >
> > >On Mon, 15 Jul 2019 at 18:51, Chesnay Schepler <[hidden email]>
> wrote:
> > >
> > >> It will likely take about a day for the 1.10 snapshots to be released.
> > >>
> > >> On 15/07/2019 12:41, Yu Li wrote:
> > >> > Thanks for the follow up Chesnay, Gordon and Kurt. It seems the
> > >> > flink-tests_2.11 snapshot [1] is not deployed yet thus
> flink-benchmark
> > >> > build [2] hasn't recovered, will watch for the next round and
> report back
> > >> > if fixed.
> > >> >
> > >> > [1]
> > >> >
> > >>
> https://repository.apache.org/content/repositories/snapshots/org/apache/flink/flink-tests_2.11/
> > >> > [2] http://codespeed.dak8s.net:8080/job/flink-master-benchmarks/
> > >> >
> > >> > Best Regards,
> > >> > Yu
> > >> >
> > >> >
> > >> > On Mon, 15 Jul 2019 at 18:25, Kurt Young <[hidden email]> wrote:
> > >> >
> > >> >> Sorry about that and thanks Gordon for fixing this!
> > >> >>
> > >> >> Best,
> > >> >> Kurt
> > >> >>
> > >> >>
> > >> >> On Mon, Jul 15, 2019 at 5:43 PM Tzu-Li (Gordon) Tai <
> > >> [hidden email]>
> > >> >> 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 <
> [hidden email]>
> > >> >>> 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
> > >> >>>>>>
> > >> >>>>>
> > >> >>>>
> > >>
> > >>
>
>
>