-
Notifications
You must be signed in to change notification settings - Fork 19
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
Test build - this may get deleted, or include fixes to the github/workflows/bazel.yaml file eventually? #216
Conversation
Add some clarification that SSL Profiles maybe used for: * client services (services on a system which initiate connections) * server services (services on a system which receive connections) * both (clients and servers)
Cleanup a bit of the README content, mostly language fixes seen upon re-reading the readings.
Make this BUILD target look like a working BUILD target (credentialz)
A change may be necessary to the BUILD or githubactions/workflows to accomodate new ubuntu images.
This fails to build, with just a comment change in the certz/BUILD.bazel:
This is also failing in the previous PR(#215), so perhaps this this here, merge back and go forward. |
'internet advice' seems to say that blowing away the cache and re-building makes this problem go away. It LOOKS like the problem is 'bazel isn't telling gcc where the std lib headers are" |
Oh, with the cache enabled the build fails still. |
and ideally @marcushines to either ack or point at proper process to fix this :) |
argh, also some linter failures :( grumble. |
Use a supported (from lemming's use as well) version of workflow.
Ok, converted the workflow (bazel.yaml) to use the bazelisk pre-built/offered workflow instead of some multi-line yaml thing that linter got mad about. Linter passes now. |
…kflows/bazel.yaml file eventually? (#216) * Issue202: Add clarification on usage of ssl profiles. Add some clarification that SSL Profiles maybe used for: * client services (services on a system which initiate connections) * server services (services on a system which receive connections) * both (clients and servers) * Documentation Cleanup. Cleanup a bit of the README content, mostly language fixes seen upon re-reading the readings. * Address comment. * Attempting to fix a broken bazel build in github-actions. Make this BUILD target look like a working BUILD target (credentialz) * Add to the BUILD fixing? * Testing github-actions BUILD. A change may be necessary to the BUILD or githubactions/workflows to accomodate new ubuntu images. * Remove the bazel cache, clearing it MAY resolve build errors. * Remove comment from BUILD. * Remove BUILD changes. * Remove commented section. * Attempt to use an already available bazel/bazelisk. Use a supported (from lemming's use as well) version of workflow.
Making a PR in order to trigger an actions run.