Skip to content

Conda Windows CI migration: execution plan #1247

@j-rivero

Description

@j-rivero

Related to #373

As context: the buildfarm expects to run the nightly generation at 10:00am Spain time and the DSL regenerate for libraries run at 10:39am. Should be fine to disable the job until the migration is done to have the morning clean.

Migration plan

Full testing

Launching all the new jobs:

def jenkins = Jenkins.instance

jenkins.items.each { job ->
    // Check if the job name ends with -cwin or -clowin, does not include -pr-, and has no builds yet
    if ((job.name.endsWith("-clwin") || job.name.endsWith("-clowin")) && 
        !job.name.contains("-pr-") && 
        job.builds.isEmpty()) {
        
        println "Triggering job: ${job.name}"
        job.scheduleBuild(0)
    }
}

Post migration

Revert to current state

If things do not work well, the migration can be reverted. What would happen following the next steps:

  • CI: previous -ci-*-win jobs will be enabled again.
  • CI: new -ci-*-clwin or -ci-*-clowinjobs will be disabled.
  • PR: the -ci-pr-win jobs will changed again to use
  • PR: new -pr-*-clwin or -pr-*-clowinjobs will be disabled.

Executing the rescue

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions