Commit Graph

13 Commits

Author SHA1 Message Date
Thomas Gummerer 7a7f4b916e
avoid new issues being created when dispatched acceptance tests fail ()
Name the CI test appropriately to make use of the skipping functionality
introduced in https://github.com/pulumi/home/pull/3457.

Fixes: https://github.com/pulumi/pulumi/issues/14026
2024-06-05 08:12:30 +00:00
Justin Van Patten f762c5f7c7
ci: Use latest version of peter-evans/create-or-update-comment ()
Upgrade all workflows to the latest version of
peter-evans/create-or-update-comment (which uses node 20 runtime).
2024-03-30 15:52:42 +00:00
Thomas Gummerer 6fbf28c54c
pass in AZURE_STORAGE_SAS_TOKEN when dispatching tests ()
Similar to https://github.com/pulumi/pulumi/pull/15175, we need to set
these secrets up so the dispatched acceptance tests can run correctly.

Noticed this in https://github.com/pulumi/pulumi/pull/15596
2024-03-06 19:27:50 +00:00
Thomas Gummerer 37969fdc77
set up secrets in acceptance test job ()
These secrets are required for the acceptance tests to run correctly, as
we're getting false failures otherwise. This is safe, since we're also
using these secrets in other CI jobs, and always review code before
running the acceptance tests.

I noticed in https://github.com/pulumi/pulumi/pull/15173 that the tests
introduced in https://github.com/pulumi/pulumi/pull/14649 are failing.
2024-01-18 14:40:31 +00:00
Justin Van Patten 7b639e30a5 ci: Don't upload coverage artifacts on PRs
We currently upload coverage artifacts to codecov every 12 hours via the periodic-coverage cron workflow, which runs the full suite of tests against master, as well as during PRs, which runs a subset of tests for the PR.

We currently see some discrepancies in the data in codecov. One theory is the difference in tests between PRs and master.

This change makes it so we no longer upload coverage artifacts during PRs, to helpfully keep the data in codecov clean for trends over time.
2023-08-09 09:56:08 -07:00
Robbie McKinstry a96a69db28
Rename "Smoke" test to "Acceptance" tests
After internal discussion, we determined "smoke" is a misleading
adjective for this category of tests. What we called "smoke tests"
are short integration tests for basic cross-platform functionality.
As a result, these are better named "acceptance" tests, since smoke
tests are intended to be a low water mark at the unit level to sniff
out bigger issues with the build as a whole.
2023-01-30 15:38:37 -05:00
Engin Diri 7d9fb008a0 feat: sign pulumi binaries with cosign
Co-authored-by: Aaron Friel <mayreply@aaronfriel.com>
2022-12-16 09:32:51 -08:00
Aaron Friel 5a7c36110e ci: fix community contributor workflows
Tightens secret permissions on the CI workflow to a set of two required
tokens, and fixes changelog comment behavior.
2022-09-21 17:39:15 -07:00
Aaron Friel 2af74b6469 ci: Use reduced smoke testing on Windows & macOS targets 2022-09-21 09:55:06 -07:00
Aaron Friel 6ef7ef64d6 ci: Enable testing of language version sets 2022-09-21 09:48:38 -07:00
Aaron Friel 87366fafeb ci: Fix CI lint 2022-09-15 18:40:19 -07:00
Aaron Friel 4e539af81d ci: Clean up excess permissions, fix acceptance tests job 2022-09-15 17:48:16 -07:00
Aaron Friel 272b987791 ci: ensure trunk is always green 2022-09-13 13:38:14 -07:00