Jenkins Job Naming

We strive for consistency in our Jenkins job naming, so all names are validated using the following regex:

^(
    ( # regular executable builds
        (?!lib)([^_]+)_build_(windows|linux|osx|android|illumos)_(x86_64|x86|arm|arm64)_(release|debug)
    )
    |
    ( # library builds
        lib([^_]+)_build_(windows|linux|osx|android|illumos)_(x86_64|x86|arm|arm64)_(shared|static|mixed)_(release|debug)
    )
    |
    ( # syncing source code of a project from git or something else
        ([^_]+)_src
    )
    |
    ( # static code analizer
        ([^_]+)_analyze_(cppcheck|scan-build)
    )
    |
    ( # package builds
        ([^_]+)_pkg_(windows|debian|ubuntu|centos|fedora|osx|android|illumos)_(x86_64|x86|arm|arm64)_(stable|nightly)_(release|debug)
    )
)$

([^_]+), which is a regular expression for “anything without _ in it”, is your project name.

You can test your job name against the regex using this regex101 save.

Some of valid job names:

• libtoxcore_build_linux_x86_64_mixed_debug
• libtoxcore_build_windows_x86_shared_release
• libtoxcore_src
• qTox_analyze_cppcheck
• qTox_build_osx_x86_64_debug
• uTox_build_windows_x86_64_release
• uTox_src

If you want to add more rules to the regex or change existing ones, please bring it up for discussion in #tox-dev.