jenkins-controller: Changes to support hw-testing #185
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
henrirosten
force-pushed
the
jenkins-plugins-for-hw-testing
branch
from
0eef1dd to
d76a6c2
Compare
henrirosten
force-pushed
the
jenkins-plugins-for-hw-testing
branch
from
5754045 to
3a83512
Compare
Signed-off-by: Henri Rosten <[email protected]>
Signed-off-by: Henri Rosten <[email protected]>
henrirosten
force-pushed
the
jenkins-plugins-for-hw-testing
branch
from
3a83512 to
44e78a4
Compare
henrirosten
changed the title
Signed-off-by: Henri Rosten <[email protected]>
mkaapu
approved these changes
Jun 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements the jenkins-controller VM changes required to support jenkins HW-testing pipelines.
This change depends on the pipeline changes from: tiiuae/ghaf-jenkins-pipeline#34.
Note: running the HW-tests requires setting-up a testagent as described in: https://ssrc.atlassian.net/wiki/x/IoAXRQ - currently, such testagent setup will be done on the 'dev' instance. Other instances are still able to run the pipelines, but the HW-tests will obviously not be run unless testagent is connected.
For the overall HW-test status after merging this PR, see: https://ssrc.atlassian.net/wiki/spaces/SP/pages/1184759816/Ghaf-infra+HW+test+status