Remove batch-job cleanup from jenkins_generic_job #1812
Merged
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
This was another potential conflict point between simultaneous runs of jenkins. Also, there's really no need for it because the directory cleanup (case, run, bld dirs) will surely cause any stale jobs from older runs to die, so there's little risk of unlimited build-up of batch jobs unless the jobs are not even being started. New CIME updates are needed for analyzing job info per-case. [BFB]
jgfouca
added a commit
that referenced
this pull request
Sep 27, 2017
) Remove batch-job cleanup from jenkins_generic_job This was another potential conflict point between simultaneous runs of jenkins. Also, there's really no need for it because the directory cleanup (case, run, bld dirs) will surely cause any stale jobs from older runs to die, so there's little risk of unlimited build-up of batch jobs unless the jobs are not even being started. New CIME updates are needed for analyzing job info per-case. [BFB] * jgfouca/cime/jenkins_no_batch_cleanup: Remove batch-job cleanup from jenkins_generic_job
jgfouca
added a commit
that referenced
this pull request
Sep 27, 2017
…1812) Remove batch-job cleanup from jenkins_generic_job This was another potential conflict point between simultaneous runs of jenkins. Also, there's really no need for it because the directory cleanup (case, run, bld dirs) will surely cause any stale jobs from older runs to die, so there's little risk of unlimited build-up of batch jobs unless the jobs are not even being started. New CIME updates are needed for analyzing job info per-case. [BFB] * jgfouca/cime/jenkins_no_batch_cleanup: Remove batch-job cleanup from jenkins_generic_job
jgfouca
pushed a commit
that referenced
this pull request
Oct 3, 2017
…nges Merge configuration changes from ACME to CIME This just copies the latest configuration files from ACME to CIME to fix Skybridge configuration changes and meet the new xmllint requirements Test suite: scripts_regression_tests Test baseline: Test namelist changes: Test status: BFB User interface changes?: N Update gh-pages html (Y/N)?: N Code review: @jedwards4b
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 was another potential conflict point between simultaneous
runs of jenkins. Also, there's really no need for it because the
directory cleanup (case, run, bld dirs) will surely cause any
stale jobs from older runs to die, so there's little risk of unlimited
build-up of batch jobs unless the jobs are not even being started.
New CIME updates are needed for analyzing job info per-case.
[BFB]