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

Turn off application tests CI #16

Closed
wants to merge 3 commits into from
Closed

Turn off application tests CI #16

wants to merge 3 commits into from

Conversation

nshyrei
Copy link
Contributor

@nshyrei nshyrei commented Oct 2, 2024

This PR turns off application tests CI until we move test images into a public repository. Additionally the PR contains the following small additions:

  1. Reverted back policy to run CI only on successful review as it blocks the iterative process to test changes for CI itself. Now with application tests turned off there is no danger in anyone running a small package of project build + unit tests
  2. docker-credential-ecr-login is now downloaded from a public place instead of a private one

@nshyrei nshyrei added the bug Something isn't working label Oct 2, 2024
@nshyrei nshyrei self-assigned this Oct 2, 2024
@aditijannu
Copy link
Collaborator

Why is the branch named SALM-213? Can we rename the branch to the relevant ticket?

@nshyrei
Copy link
Contributor Author

nshyrei commented Oct 3, 2024

Why is the branch named SALM-213? Can we rename the branch to the relevant ticket?

This is the correct ticket number - "Turn off Application tests in Salmiac"

@nshyrei nshyrei requested a review from aditijannu October 3, 2024 08:30
@aditijannu
Copy link
Collaborator

Why is the branch named SALM-213? Can we rename the branch to the relevant ticket?

This is the correct ticket number - "Turn off Application tests in Salmiac"

It's RTE-213 and not SALM-213

@nshyrei nshyrei closed this Oct 4, 2024
@nshyrei nshyrei deleted the ns/SALM-213 branch October 4, 2024 08:59
- name: Run application tests container
env:
FORTANIX_API_KEY: ${{ secrets.FORTANIX_API_KEY }}
OVERLAYFS_UNIT_TEST_API_KEY: ${{ secrets.OVERLAYFS_UNIT_TEST_API_KEY }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now these keys are no longer required, right? Can you also remove them from the secrets section above?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are still used in

- name: Run Rust unit tests

push:
branches: [ "master" ]
pull_request:
branches: [ "master" ]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpick: Personally I'm in strong favor of a one-goal-one-PR rule. It makes it much more clear why these changes are there. I agree to what you're trying to do, but doesn't that mean we can also disable the other keys here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't fully understand what keys are you talking about here, do you want to remove the push/pull rules? I believe in that case CI won't start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants