Thanks a lot, Luke, Gradle scans are now working with your changes.

On Thu, Oct 10, 2019 at 10:15 AM Luke Cwik <[email protected]> wrote:

> The Gradle forums[1] suggested that we will need to downgrade the build
> scan plugin to 2.3 to get the build scans working again.
> Tested it locally and it worked. Filed BEAM-8378 and opened pr/9762 with
> the downgrade.
>
> 1: https://discuss.gradle.org/t/your-build-scan
> -could-not-be-displayed-what-does-this-mean/33302
>
> On Thu, Sep 26, 2019 at 9:41 AM Lukasz Cwik <[email protected]> wrote:
>
>> The summary so far is that the spotless plugin is somehow interfering
>> with what is being published in a way where the build scan is broken.
>>
>> I tried an older version of the spotless plugin and also the latest
>> version and neither worked. I then tried to remove the spotless plugin[1]
>> and was able to successfully publish a build scan[2].
>>
>> Still waiting on an update in the forum about how to keep both spotless
>> and build scans working.
>>
>> 1:
>> https://github.com/lukecwik/incubator-beam/commit/1f026c9b94e3f8afc0cd472350b77c1eeef30a83
>> 2: https://gradle.com/s/665zarmdoixh6
>>
>>
>> On Wed, Sep 25, 2019 at 8:57 AM Lukasz Cwik <[email protected]> wrote:
>>
>>> I reached out on the Gradle forum
>>> https://discuss.gradle.org/t/your-build-scan-could-not-be-displayed-what-does-this-mean/33302
>>>
>>> On Wed, Sep 25, 2019 at 8:49 AM Łukasz Gajowy <[email protected]>
>>> wrote:
>>>
>>>> FWIW, I tried doing it locally and observed the same behavior. It works
>>>> in my other private projects. This is all I know for now.
>>>>
>>>> Łukasz
>>>>
>>>> wt., 24 wrz 2019 o 22:43 Lukasz Cwik <[email protected]> napisał(a):
>>>>
>>>>> Not to my knowledge. Maybe something is down.
>>>>>
>>>>> Have you tried running a gradle build locally with --scan?
>>>>>
>>>>> On Tue, Sep 24, 2019 at 1:03 PM Valentyn Tymofieiev <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> For example, https://gradle.com/s/mpfu3wpz2xfwe  says: Your build
>>>>>> scan could not be displayed.
>>>>>>
>>>>>

Reply via email to