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

Remove the ID generator from AutoHCK #268

Merged
merged 1 commit into from
Apr 15, 2024
Merged

Remove the ID generator from AutoHCK #268

merged 1 commit into from
Apr 15, 2024

Conversation

kostyanf14
Copy link
Contributor

AutoHCK is a CI runner, not a manager, and should not control resources between different runs.

Add command line argument to have the ability to specify an ID that is received from external tools.

@YanVugenfirer
Copy link
Contributor

While I agree with the PR message. Who will allocate the IDs in the near future?

@kostyanf14
Copy link
Contributor Author

While I agree with the PR message. Who will allocate the IDs in the near future?

We don't need this in the near future. Currently, we run only one HCK-CI on the server. If we change this, Jenkins can assign an ID.

@kostyanf14 kostyanf14 marked this pull request as ready for review December 14, 2023 08:58
@kostyanf14 kostyanf14 marked this pull request as draft January 25, 2024 12:35
@kostyanf14 kostyanf14 marked this pull request as ready for review April 12, 2024 08:57
AutoHCK is a CI runner, not a manager, and should not
control resources between different runs.

Add command line argument to have the ability to specify
an ID that is received from external tools.

Signed-off-by: Kostiantyn Kostiuk <konstantin@daynix.com>
@kostyanf14
Copy link
Contributor Author

While I agree with the PR message. Who will allocate the IDs in the near future?

We can use Jenkins EXECUTOR_NUMBER env to assign id in case of multiple test runs.

@YanVugenfirer YanVugenfirer merged commit c2d6bdd into master Apr 15, 2024
6 checks passed
@YanVugenfirer YanVugenfirer deleted the no-id-gen branch April 15, 2024 08:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants