Re: Email about build runs on my fork.

[Alex Amato]

Thanks, havent seen any emails since rebasing to master.

On Sun, Aug 2, 2020 at 5:09 AM Tobiasz Kędzierski <
tobiasz.kedzier...@polidea.com> wrote:

> Hi Alex,
>
> After rebase on the latest master scheduled workflow should not run,
> condition for scheduled job was extended to prevent situations like this.
> As mentioned by Robert, you can disable gh action in case you don't need
> it.
>
> BR
> Tobiasz
>
> On Thu, Jul 30, 2020 at 9:18 PM Robert Burke  wrote:
>
>> You can disable GitHub actions on your own repos via the UI or via a code
>> change
>>
>> https://github.community/t/how-can-i-disable-a-github-action/17049
>>
>> On Thu, Jul 30, 2020, 12:15 PM Ahmet Altay  wrote:
>>
>>> /cc +tobiasz.kedzier...@polidea.com  +Emily
>>> Ye  -- this question is related to one of the
>>> recent github action prs.
>>>
>>> On Thu, Jul 30, 2020 at 10:23 AM Alex Amato  wrote:
>>>
 Hi,

 I received this email indicating some build was running on my fork,
 though I had not been doing any work on that fork for the last few weeks.

 I don't really need to run these builds on my fork and don't think we
 need to waste resources on this. Is there some way to prevent forks from
 doing this?

 I just rebased my own fork from apache beam master now. I am not sure
 if that will stop it or not, but it should now be up to date.

 -- Forwarded message -
 From: Alex Amato 
 Date: Wed, Jul 29, 2020 at 7:47 PM
 Subject: [ajamato/beam] Run failed: Build python wheels - master
 (9ca80ae)
 To: ajamato/beam 
 Cc: Ci activity 


 Run failed for master (9ca80ae)

 Repository: ajamato/beam
 Workflow: Build python wheels
 Duration: 29 minutes and 27.0 seconds
 Finished: 2020-07-30 02:47:17 UTC

 View results 
 Jobs:

- build_source 
succeeded (0 annotations)
- Build wheels on ubuntu-latest
 succeeded (0
annotations)
- Build wheels on macos-latest
 succeeded (0
annotations)
- Prepare GCS 
succeeded (0 annotations)
- Upload source to GCS bucket
 failed (1
annotation)
- Tag repo nightly 
succeeded (0 annotations)
- Upload wheels to GCS bucket (ubuntu-latest)
 cancelled (2
annotations)
- Upload wheels to GCS bucket (macos-latest)
 failed (1
annotation)
- List files on Google Cloud Storage Bucket
 skipped (0
annotations)

 —
 You are receiving this because this workflow ran on your branch.
 Manage your GitHub Actions notifications here
 .

>>>

Re: Email about build runs on my fork.

[Tobiasz Kędzierski]

Hi Alex,

After rebase on the latest master scheduled workflow should not run,
condition for scheduled job was extended to prevent situations like this.
As mentioned by Robert, you can disable gh action in case you don't need it.

BR
Tobiasz

On Thu, Jul 30, 2020 at 9:18 PM Robert Burke  wrote:

> You can disable GitHub actions on your own repos via the UI or via a code
> change
>
> https://github.community/t/how-can-i-disable-a-github-action/17049
>
> On Thu, Jul 30, 2020, 12:15 PM Ahmet Altay  wrote:
>
>> /cc +tobiasz.kedzier...@polidea.com  +Emily
>> Ye  -- this question is related to one of the recent
>> github action prs.
>>
>> On Thu, Jul 30, 2020 at 10:23 AM Alex Amato  wrote:
>>
>>> Hi,
>>>
>>> I received this email indicating some build was running on my fork,
>>> though I had not been doing any work on that fork for the last few weeks.
>>>
>>> I don't really need to run these builds on my fork and don't think we
>>> need to waste resources on this. Is there some way to prevent forks from
>>> doing this?
>>>
>>> I just rebased my own fork from apache beam master now. I am not sure if
>>> that will stop it or not, but it should now be up to date.
>>>
>>> -- Forwarded message -
>>> From: Alex Amato 
>>> Date: Wed, Jul 29, 2020 at 7:47 PM
>>> Subject: [ajamato/beam] Run failed: Build python wheels - master
>>> (9ca80ae)
>>> To: ajamato/beam 
>>> Cc: Ci activity 
>>>
>>>
>>> Run failed for master (9ca80ae)
>>>
>>> Repository: ajamato/beam
>>> Workflow: Build python wheels
>>> Duration: 29 minutes and 27.0 seconds
>>> Finished: 2020-07-30 02:47:17 UTC
>>>
>>> View results 
>>> Jobs:
>>>
>>>- build_source 
>>>succeeded (0 annotations)
>>>- Build wheels on ubuntu-latest
>>> succeeded (0
>>>annotations)
>>>- Build wheels on macos-latest
>>> succeeded (0
>>>annotations)
>>>- Prepare GCS 
>>>succeeded (0 annotations)
>>>- Upload source to GCS bucket
>>> failed (1
>>>annotation)
>>>- Tag repo nightly 
>>>succeeded (0 annotations)
>>>- Upload wheels to GCS bucket (ubuntu-latest)
>>> cancelled (2
>>>annotations)
>>>- Upload wheels to GCS bucket (macos-latest)
>>> failed (1
>>>annotation)
>>>- List files on Google Cloud Storage Bucket
>>> skipped (0
>>>annotations)
>>>
>>> —
>>> You are receiving this because this workflow ran on your branch.
>>> Manage your GitHub Actions notifications here
>>> .
>>>
>>

Re: Email about build runs on my fork.

[Robert Burke]

You can disable GitHub actions on your own repos via the UI or via a code
change

https://github.community/t/how-can-i-disable-a-github-action/17049

On Thu, Jul 30, 2020, 12:15 PM Ahmet Altay  wrote:

> /cc +tobiasz.kedzier...@polidea.com  +Emily
> Ye  -- this question is related to one of the recent
> github action prs.
>
> On Thu, Jul 30, 2020 at 10:23 AM Alex Amato  wrote:
>
>> Hi,
>>
>> I received this email indicating some build was running on my fork,
>> though I had not been doing any work on that fork for the last few weeks.
>>
>> I don't really need to run these builds on my fork and don't think we
>> need to waste resources on this. Is there some way to prevent forks from
>> doing this?
>>
>> I just rebased my own fork from apache beam master now. I am not sure if
>> that will stop it or not, but it should now be up to date.
>>
>> -- Forwarded message -
>> From: Alex Amato 
>> Date: Wed, Jul 29, 2020 at 7:47 PM
>> Subject: [ajamato/beam] Run failed: Build python wheels - master (9ca80ae)
>> To: ajamato/beam 
>> Cc: Ci activity 
>>
>>
>> Run failed for master (9ca80ae)
>>
>> Repository: ajamato/beam
>> Workflow: Build python wheels
>> Duration: 29 minutes and 27.0 seconds
>> Finished: 2020-07-30 02:47:17 UTC
>>
>> View results 
>> Jobs:
>>
>>- build_source 
>>succeeded (0 annotations)
>>- Build wheels on ubuntu-latest
>> succeeded (0
>>annotations)
>>- Build wheels on macos-latest
>> succeeded (0
>>annotations)
>>- Prepare GCS 
>>succeeded (0 annotations)
>>- Upload source to GCS bucket
>> failed (1 annotation)
>>- Tag repo nightly 
>>succeeded (0 annotations)
>>- Upload wheels to GCS bucket (ubuntu-latest)
>> cancelled (2
>>annotations)
>>- Upload wheels to GCS bucket (macos-latest)
>> failed (1 annotation)
>>- List files on Google Cloud Storage Bucket
>> skipped (0
>>annotations)
>>
>> —
>> You are receiving this because this workflow ran on your branch.
>> Manage your GitHub Actions notifications here
>> .
>>
>

Re: Email about build runs on my fork.

[Ahmet Altay]

/cc +tobiasz.kedzier...@polidea.com  +Emily
Ye  -- this question is related to one of the recent
github action prs.

On Thu, Jul 30, 2020 at 10:23 AM Alex Amato  wrote:

> Hi,
>
> I received this email indicating some build was running on my fork, though
> I had not been doing any work on that fork for the last few weeks.
>
> I don't really need to run these builds on my fork and don't think we need
> to waste resources on this. Is there some way to prevent forks from doing
> this?
>
> I just rebased my own fork from apache beam master now. I am not sure if
> that will stop it or not, but it should now be up to date.
>
> -- Forwarded message -
> From: Alex Amato 
> Date: Wed, Jul 29, 2020 at 7:47 PM
> Subject: [ajamato/beam] Run failed: Build python wheels - master (9ca80ae)
> To: ajamato/beam 
> Cc: Ci activity 
>
>
> Run failed for master (9ca80ae)
>
> Repository: ajamato/beam
> Workflow: Build python wheels
> Duration: 29 minutes and 27.0 seconds
> Finished: 2020-07-30 02:47:17 UTC
>
> View results 
> Jobs:
>
>- build_source 
>succeeded (0 annotations)
>- Build wheels on ubuntu-latest
> succeeded (0
>annotations)
>- Build wheels on macos-latest
> succeeded (0
>annotations)
>- Prepare GCS 
>succeeded (0 annotations)
>- Upload source to GCS bucket
> failed (1 annotation)
>- Tag repo nightly 
>succeeded (0 annotations)
>- Upload wheels to GCS bucket (ubuntu-latest)
> cancelled (2
>annotations)
>- Upload wheels to GCS bucket (macos-latest)
> failed (1 annotation)
>- List files on Google Cloud Storage Bucket
> skipped (0
>annotations)
>
> —
> You are receiving this because this workflow ran on your branch.
> Manage your GitHub Actions notifications here
> .
>

Email about build runs on my fork.

[Alex Amato]

Hi,

I received this email indicating some build was running on my fork, though
I had not been doing any work on that fork for the last few weeks.

I don't really need to run these builds on my fork and don't think we need
to waste resources on this. Is there some way to prevent forks from doing
this?

I just rebased my own fork from apache beam master now. I am not sure if
that will stop it or not, but it should now be up to date.

-- Forwarded message -
From: Alex Amato 
Date: Wed, Jul 29, 2020 at 7:47 PM
Subject: [ajamato/beam] Run failed: Build python wheels - master (9ca80ae)
To: ajamato/beam 
Cc: Ci activity 


Run failed for master (9ca80ae)

Repository: ajamato/beam
Workflow: Build python wheels
Duration: 29 minutes and 27.0 seconds
Finished: 2020-07-30 02:47:17 UTC

View results 
Jobs:

   - build_source 
   succeeded (0 annotations)
   - Build wheels on ubuntu-latest
    succeeded (0
   annotations)
   - Build wheels on macos-latest
    succeeded (0
   annotations)
   - Prepare GCS  succeeded
   (0 annotations)
   - Upload source to GCS bucket
    failed (1 annotation)
   - Tag repo nightly 
   succeeded (0 annotations)
   - Upload wheels to GCS bucket (ubuntu-latest)
    cancelled (2
   annotations)
   - Upload wheels to GCS bucket (macos-latest)
    failed (1 annotation)
   - List files on Google Cloud Storage Bucket
    skipped (0 annotations)

—
You are receiving this because this workflow ran on your branch.
Manage your GitHub Actions notifications here
.