Adding more helpful information about Cloud Build. With it's additional
features, we can:
1. Define GitHub triggers on certain branches and optionally multiple
wildcarded includes and exclude paths.
2. Flag whether to trigger on pull requests or specific branch commits
3. Version control the terr
I wonder if some integration tests could be offloaded to their respective
cloud provider. For example, the Google cloud related integration tests
could be executed on Cloud build. Cloud Build's service account, or
custom, could have the minimally necessary IAM roles to access Google Cloud
resource
Kenn, thank you for the summary. SGTM. Looking forward to GitHub Actions.
On Mon, Nov 7, 2022 at 12:58 PM Kenneth Knowles wrote:
> OK, it seems like there is general consensus. Not too much action on the
> document. I will summarize the gaps that don't have an answer in the doc,
> and my new opi
OK, it seems like there is general consensus. Not too much action on the
document. I will summarize the gaps that don't have an answer in the doc,
and my new opinion of how important they are:
- [required] Run specific non-default workflow on PR
- [required] View history of a workflow
- [requir
+1
Also would help address a good amount of what concerns me that was [sorta]
raised by https://lists.apache.org/thread/7jr99nc5xsb3ft1d75kb0ml32bzw89rv
Once we think this is something we want to do, but might be
blocked/concerned because of lack of definitively comparable features, I'd
be happy
+1 Github Actions are more intuitive and easy to modify and test for everyone.
Also Beam wins because that makes one less system to maintain.
Regards,
Ismaël
On Wed, Oct 19, 2022 at 5:50 PM Danny McCormick via dev
wrote:
>
> Thanks for kicking this conversation off. I'm +1 on migrating, but only
Thanks for kicking this conversation off. I'm +1 on migrating, but only
once we've found a specific replacement for easy observability (which
workflows have been failing lately, and how often) and trigger phrases (for
retries and workflows that aren't automatically kicked off but should be
run for
Hi all,
As you probably noticed, there's a lot of work going on around adding more
GitHub Actions workflows.
Can we fully migrate to GitHub Actions? Similar to our GitHub Issues
migration (but less user-facing) it would bring us on to "default"
infrastructure that more people understand and is ma
