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

Integration with CI jobs: test trigger without need to delete existing custom resource #312

Closed
DAT-Amundi opened this issue Oct 16, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@DAT-Amundi
Copy link

Feature Description

Recreate test jobs and resources without need to delete the existing Custom resource, only synchronize should be able to relaunch tests , in order to automatize load tests

Suggested Solution (optional)

Run with : kubectl apply -f ..
without need to : kubectl delete -f
I tried applying custom annotation and didn't work :
spec:
runner:
metadata:
annotations:
deploymentTime:

Already existing or connected issues / PRs (optional)

No response

@DAT-Amundi DAT-Amundi added the enhancement New feature or request label Oct 16, 2023
@yorugac
Copy link
Collaborator

yorugac commented Oct 18, 2023

Hi @DAT-Amundi, thanks for the issue! It sounds to be very similar to edits of custom resource? This one: #305
Could you please clarify the difference?

@DAT-Amundi
Copy link
Author

DAT-Amundi commented Oct 23, 2023

Hi @yorugac thanks for your comment, the purpose of this issue is so precise, not sure it is covered by #305 , the main difference that here I want to relaunch the test even without any modification in the TestRun CRD, whenever I want to rerun tests it should be possible just by synchronizing. That's why I tried deployment time annotation, to make ArgoCD detect change and relaunch tests but it doesn't work, the CRD is not taking that into account I think.

@yorugac
Copy link
Collaborator

yorugac commented Oct 24, 2023

@DAT-Amundi, in that case, I'm confused what do you mean by "synchronizing"? You mention ArgoCD: do you mean sync operation there? Then yes, changing annotation won't work as a "relaunch": from perspective of the k6-operator by adding annotation you edited TestRun CRD (with the help of ArgoCD) but as mentioned in #305, edits are not supported at the moment at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants