This is in contrast to the **development** stages, where you are constantly changing the code, breaking it and fixing it, stopping and restarting the development server, etc.

## Deployment Strategies { #deployment-strategies }

// Generates a Build Scan custom value "PartOf=X,Y,Z"
// where X, Y, Z are all the stages including current stage
// For example, for the stage PullRequestFeedback, the custom value will be "PartOf=PullRequestFeedback,ReadyForNightly,ReadyForRelease"
private fun Stage.getBuildScanCustomValues(): List<String> =
    StageName
        .values()

#!groovy

pipeline {
  agent none
  // save some io during the build
  options {
    skipDefaultCheckout()
    durabilityHint('PERFORMANCE_OPTIMIZED')
    disableRestartFromStage()
  }
  stages {
    stage("Build / Test - JDK17") {
      agent { node { label 'ubuntu' } }
      steps {
        timeout(time: 210, unit: 'MINUTES') {
          checkout scm
          mavenBuild("jdk_17_latest", "")
          script {

        TaskProvider<Sync> userguide = tasks.register("userguide", Sync.class, task -> {
            task.setGroup("documentation");
            task.setDescription("Stages rendered user manual documentation.");

            task.from(userguideSinglePageHtml);
            task.from(userguideMultiPage);
            task.into(extension.getUserManual().getStagingRoot().dir("final"));

    },
    BuildLogicTest {
        override fun create(
            model: CIBuildModel,
            stage: Stage,
            flakyTestStrategy: FlakyTestStrategy,
        ): OsAwareBaseGradleBuildType = BuildLogicTest(model, stage)
    },
    BuildDistributions {
        override fun create(
            model: CIBuildModel,
            stage: Stage,
            flakyTestStrategy: FlakyTestStrategy,

* the system authenticates the user

* the CLI
* the command line interface

* the server
* the client

* the cloud provider
* the cloud service

* the development
* the development stages

* the dict
* the dictionary
* the enumeration
* the enum
* the enum member

* the encoder
* the decoder
* to encode
* to decode

* the exception
* to raise

            model.stages[1].getBuildScanCustomValueParam(),
        )
        assertEquals(
            "-DbuildScan.PartOf=ReadyforRelease",
            model.stages[4].getBuildScanCustomValueParam(),
        )
    }

    @Test
    fun `test functional test project tags`() {
        assertEquals(
            "QuickJava25AdoptiumLinuxAmd64",

                stage.specificBuilds.size + stage.functionalTests.size + stage.performanceTests.size + stage.docsTests.size +
                    (if (prevStage != null) 1 else 0) +
                    // flakyTestQuarantineTriggers
                    if (stage.stageName == StageName.READY_FOR_RELEASE) 3 else 0,
                it.dependencies.items.size,
                stage.stageName.stageName,
            )
        }
    }

            .forEach {
                buildType(FlakyTestQuarantine(model, stage, it))
            }

        model.stages
            .filter { it.stageName <= StageName.READY_FOR_RELEASE }
            .flatMap { stage -> stage.specificBuilds.map { it.create(model, stage, FlakyTestStrategy.ONLY) } }
            .filter { it.os == os }
            .filter { it is SmokeTests || it is SmokeIdeTests }

Although in FastAPI it's optional, and is used mainly to set headers, cookies, and alternative status codes.

///

### [Molten](https://moltenframework.com/) { #molten }

I discovered Molten in the first stages of building **FastAPI**. And it has quite similar ideas:

* Based on Python type hints.
* Validation and documentation from these types.