Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the simplest CI with make #10982

Draft
wants to merge 64 commits into
base: main
Choose a base branch
from
Draft

Add the simplest CI with make #10982

wants to merge 64 commits into from

Conversation

HoloRin
Copy link
Contributor

@HoloRin HoloRin commented Apr 12, 2024

To check total run time

@HoloRin HoloRin force-pushed the make-ci branch 5 times, most recently from d137b1a to d0686ff Compare April 16, 2024 16:04
@mergify mergify bot added the make label Apr 17, 2024
@HoloRin HoloRin force-pushed the make-ci branch 8 times, most recently from 9e90669 to b3255af Compare April 24, 2024 13:36
@HoloRin HoloRin force-pushed the make-ci branch 8 times, most recently from 471191b to 358757c Compare April 29, 2024 16:40
@mergify mergify bot added the bazel label Apr 29, 2024
@HoloRin HoloRin force-pushed the make-ci branch 4 times, most recently from b9ef746 to ee5a60f Compare May 2, 2024 13:35
HoloRin added 24 commits May 6, 2024 13:28
So that github actions does not report it as an errored workflow, when
it is only a template
since the test suite in rabbitmq_prometheus invokes test-build, it
ends up wiping out any copies of the module. Links seem to be the most
natural workaround, as the module depends on the federation header and
therefore can't be easily moved to rabbit_ct_helpers
It turns out that actions workflow artifacts are visible to everyone,
so injected credentials would be leaked via the test logs. Therefore
we just skip them (they still run in the bazel workflows where the
logs are protected).
therefore all dimensions of the matrix must be included in the key,
otherwise the first to finish within the matrix, wins
Technically this is a workaround - dialyzer should not be checking the
khepri source in this case
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant