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

[Build] Define complete configuration of StartSmokeTests job via Job-DSL #2617

Merged

Conversation

HannesWell
Copy link
Member

This way the complete configuration of the 'Start-smoke-tests' job is under version control.
The only change is that this moves the 'Start-smoke-tests' job from the root of the Jenkins instance into the 'SmokeTests' folder, where all dedicated smoke-tests are located too.
This simplifies and cleans-up the structure of the Releng-Jenkins.

@HannesWell HannesWell force-pushed the define-smoke-test-parmeters branch from 3e853f6 to 82968a0 Compare December 1, 2024 14:09
This way the complete configuration of the 'Start-smoke-tests' job is
under version control.
The only change is that this moves the 'Start-smoke-tests' job from the
root of the Jenkins instance into the 'SmokeTests' folder, where all
dedicated smoke-tests are located too.
This simplifies and cleans-up the structure of the Releng-Jenkins.
@HannesWell HannesWell force-pushed the define-smoke-test-parmeters branch from 82968a0 to c965202 Compare December 1, 2024 14:17
and only use the latest Temurin JDK of the corresponding (feature)
release in all smoke tests.

Defining the URLs within the Jenkins file has the advantage that changes
are immediately visible upon the next execution without the need to run
the seed-job again and without the one-job-delay that happens if
parameters change.
@HannesWell HannesWell force-pushed the define-smoke-test-parmeters branch from c965202 to 3031928 Compare December 1, 2024 14:22
@HannesWell
Copy link
Member Author

HannesWell commented Dec 1, 2024

The cron trigger from the Start-smoke-tests job is now removed again since it's always triggered by I- and Y-builds and if I understood the specification 15 4 16 2 4 correctly, it runs only on the 16th of Feburary and only if it's the fourth day of the week. So round about every seven years?

Furthermore I added another commit to define JDK-URLs within the StartSmokeTests Jenkinsfile, which has the advantage that changes are immediately visible upon the next execution without the need to run the seed-job again and without the one-job-delay that happens if parameters change. The default values from the specific smoke test job definitions were removed.

Furthermore only the latest Temurin JDK builds of the corresponding (feature) release in all smoke tests. This reduces the maintenance effort respectively ensures that old JDK builds are automatically replaced.

Submitting this now as the verification build does not test this.

@HannesWell HannesWell merged commit c1478bf into eclipse-platform:master Dec 1, 2024
3 of 4 checks passed
@HannesWell HannesWell deleted the define-smoke-test-parmeters branch December 1, 2024 14:27
@HannesWell
Copy link
Member Author

For the record and for reference, since I'm no going to delete the old, manually maintained job configuration (i.e.https://ci.eclipse.org/releng/job/Start-smoke-tests/), this is the status overview of it's last executions:

grafik

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.

1 participant