Jenkins versions and LTS - Step-by-Step Execution

Process Flow - Jenkins versions and LTS

Start: Jenkins Release Cycle

↓

Develop New Features

↓

Release Weekly Versions

↓

Select Stable Weekly for LTS

↓

Release LTS Version

↓

Users Choose Version

↓

Update & Maintain

Jenkins releases weekly versions with new features and fixes. Some weekly versions are chosen as stable and become Long-Term Support (LTS) releases for users needing stability.

Execution Sample

Jenkins

Week 1: Release 2.400 (weekly)
Week 2: Release 2.401 (weekly)
Week 3: Release 2.402 (weekly)
Week 4: Release 2.400.3 (LTS)
User installs 2.400.3 for stability

Shows Jenkins releasing weekly versions and then an LTS version based on a stable weekly release.

Process Table

Step	Action	Version Released	Type	User Choice
1	Release weekly version	2.400	Weekly	No
2	Release weekly version	2.401	Weekly	No
3	Release weekly version	2.402	Weekly	No
4	Select stable weekly for LTS	2.400.3	LTS	Yes
5	User installs version	2.400.3	LTS	Yes
6	Release next weekly version	2.403	Weekly	No
7	Release next LTS based on stable weekly	2.402.1	LTS	Future

💡 User chooses LTS version for stability; weekly versions continue to release.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	After Step 7
Current Weekly Version	None	2.400	2.401	2.402	2.402	2.402	2.403	2.403
Current LTS Version	None	None	None	None	2.400.3	2.400.3	2.400.3	2.402.1
User Installed Version	None	None	None	None	None	2.400.3	2.400.3	2.400.3

Key Moments - 3 Insights

Why does Jenkins release both weekly and LTS versions?

Jenkins releases weekly versions to provide the latest features and fixes quickly. LTS versions are selected stable weekly releases for users who want a reliable, less frequently changing version. See execution_table steps 1-4.

Can users install weekly versions instead of LTS?

Yes, users can install weekly versions to get new features faster, but these may be less stable. LTS is recommended for production. Refer to execution_table steps 1-5.

How often are LTS versions released?

LTS versions are released periodically based on stable weekly releases, usually every 12 weeks or so. This is shown in execution_table steps 4 and 7.

Visual Quiz - 3 Questions

Look at the execution_table, which version is the first LTS release?

A 2.401

B 2.400.3

C 2.402

D 2.403

💡 Hint

Check the 'Type' column for 'LTS' and see the version at step 4.

At which step does the user install the LTS version?

A Step 3

B Step 6

C Step 5

D Step 7

💡 Hint

Look at the 'User Choice' column for 'Yes' in the execution_table.

If Jenkins stopped releasing weekly versions, what would happen to LTS releases?

A LTS releases would stop because they depend on weekly versions

B LTS releases would continue as normal

C Users would get more LTS releases

D Weekly versions would become LTS automatically

💡 Hint

Refer to the concept_flow where LTS is selected from stable weekly releases.

Concept Snapshot

Jenkins releases weekly versions with new features and fixes.
Some weekly versions are chosen as stable and become LTS (Long-Term Support) releases.
LTS versions are recommended for users needing stability.
Weekly versions update frequently; LTS updates less often.
Users choose between latest features (weekly) or stability (LTS).

Full Transcript

Jenkins has two main types of releases: weekly and LTS. Weekly releases come out every week with the newest features and fixes. From these weekly releases, Jenkins selects stable versions to become LTS releases. LTS stands for Long-Term Support and is meant for users who want a stable and reliable Jenkins version. Users can choose to install either the latest weekly version or the LTS version. The LTS versions update less often and are tested more thoroughly. This helps users balance between having the newest features and having a stable system. The process repeats as Jenkins continues to release new weekly versions and periodically updates the LTS version based on a stable weekly release.

Practice

1. What is the main difference between Jenkins LTS and weekly versions?

easy

A. LTS versions are more stable and updated less frequently

B. Weekly versions are more stable than LTS versions

C. LTS versions have fewer features than weekly versions

D. Weekly versions are only for testing and cannot be used in production

Solution

1. Step 1: Understand Jenkins version types

   Jenkins offers two main version types: LTS (Long-Term Support) and weekly releases.

2. Step 2: Compare update frequency and stability

   LTS versions are designed to be stable and receive updates less often, while weekly versions get new features and fixes more frequently but may be less stable.

3. Final Answer:

   LTS versions are more stable and updated less frequently -> Option A

4. Quick Check:

   Stability and update frequency = LTS [OK]

Hint: LTS means stable and slow updates, weekly means fast updates [OK]

Common Mistakes:

• Confusing stability between LTS and weekly
• Thinking weekly versions are for production only
• Assuming LTS has fewer features always

2. Which command correctly checks the Jenkins version installed on a Linux server?

easy

A. jenkins --version

B. jenkins version check

C. jenkins -v

D. java -jar jenkins.war --version

Solution

1. Step 1: Identify Jenkins version check command

   Jenkins runs as a Java application using the jenkins.war file, so checking version uses the java command with the war file.

2. Step 2: Validate correct syntax

   The correct syntax is: java -jar jenkins.war --version. Other options are invalid commands or incorrect flags.

3. Final Answer:

   java -jar jenkins.war --version -> Option D

4. Quick Check:

   Use java -jar jenkins.war --version [OK]

Hint: Use java -jar jenkins.war --version to check Jenkins version [OK]

Common Mistakes:

• Using 'jenkins --version' which is invalid
• Trying 'jenkins -v' which Jenkins does not support
• Typing commands without java or war file

3. If you install Jenkins weekly version and then run java -jar jenkins.war --version, what output should you expect?

medium

A. An error saying version cannot be determined

B. A version number with a date indicating the weekly build

C. The latest LTS version number

D. No output, just returns to prompt

Solution

1. Step 1: Understand output of version command

   The command shows the Jenkins version installed, including build info.

2. Step 2: Identify output for weekly version

   Weekly versions include a date or build number in the version string, unlike LTS which is a stable release number.

3. Final Answer:

   A version number with a date indicating the weekly build -> Option B

4. Quick Check:

   Weekly version output includes date/build info [OK]

Hint: Weekly versions show date in version output [OK]

Common Mistakes:

• Expecting LTS version number for weekly install
• Thinking command returns no output
• Assuming error occurs for weekly versions

4. You installed Jenkins LTS but notice frequent plugin compatibility errors. What is the most likely cause?

medium

A. Running Jenkins without Java installed

B. Installing weekly plugins on LTS Jenkins

C. Using an outdated LTS version with newer plugins

D. Incorrect Jenkins home directory permissions

Solution

1. Step 1: Analyze plugin compatibility issue

   Plugin errors often occur when Jenkins core and plugins versions mismatch.

2. Step 2: Identify cause related to LTS version

   Using an older LTS version while installing newer plugins can cause incompatibility.

3. Final Answer:

   Using an outdated LTS version with newer plugins -> Option C

4. Quick Check:

   Old LTS + new plugins = compatibility errors [OK]

Hint: Match plugin versions with Jenkins core version [OK]

Common Mistakes:

• Blaming weekly plugins on LTS without checking versions
• Ignoring Java installation issues
• Assuming permissions cause plugin errors

5. Your team wants a Jenkins version that balances stability and access to new features for a production environment. Which version strategy is best?

hard

A. Use the latest LTS version and update it every 12 weeks

B. Use the latest weekly version and update plugins weekly

C. Use an old LTS version and never update it

D. Use weekly versions but only update every 6 months

Solution

1. Step 1: Understand production needs

   Production environments need stability but also reasonable updates for security and features.

2. Step 2: Evaluate version strategies

   Latest LTS versions provide tested stability and updating every 12 weeks balances new features and risk.

3. Step 3: Reject risky options

   Weekly versions updated too often can cause instability; old LTS without updates risks security issues.

4. Final Answer:

   Use the latest LTS version and update it every 12 weeks -> Option A

5. Quick Check:

   LTS + regular updates = stable and current [OK]

Hint: Choose LTS with regular updates for production [OK]

Common Mistakes:

• Choosing weekly versions for production without caution
• Never updating Jenkins risking security
• Updating weekly versions too infrequently