[Build] Unify definition of all smoke tests into StartSmokeTests job #2637
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
Define the different smoke-test Jenkins agents in a scripted sub-part of the StartSmokeTests job and unify the multiple definitions of the executed shell-script into one.
HannesWell
force-pushed
the
smoke-tests-in-one-job
branch
from
1fe7eea to
5911ac7
Compare
|
Submitting this immediately since the verification build does not test this. |
|
Now that all smoke test configurations are defined and launched from one job, the following separated jobs can be deleted:
But I'll keep them for a little bit, for reference. |
HannesWell
added a commit
to HannesWell/eclipse.platform.releng.aggregator
that referenced
this pull request
Dec 12, 2024
Defining them only in the pipeline has the effect that the jobs forgets it's parameter each time the job-configuration is recreated by the seed-job and thus the subsequent first execution of the smoke-test fails because it has 'forgotten' it's parameters and has to re-discover them on the first pipeline execution again. eclipse-platform#2637
HannesWell
added a commit
to HannesWell/eclipse.platform.releng.aggregator
that referenced
this pull request
Dec 12, 2024
Defining them only in the pipeline has the effect that the jobs forgets it's parameter each time the job-configuration is recreated by the seed-job and thus the subsequent first execution of the smoke-test fails because it has 'forgotten' it's parameters and has to re-discover them on the first pipeline execution again. Follow-up on eclipse-platform#2637
HannesWell
added a commit
that referenced
this pull request
Dec 12, 2024
Defining them only in the pipeline has the effect that the jobs forgets it's parameter each time the job-configuration is recreated by the seed-job and thus the subsequent first execution of the smoke-test fails because it has 'forgotten' it's parameters and has to re-discover them on the first pipeline execution again. Follow-up on #2637
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.
Define the different smoke-test Jenkins agents in a scripted sub-part of the
StartSmokeTestsjob and unify the multiple definitions of the executed shell-script into one.