You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 61049f4
Browse filesBrowse the repository at this point in the historyBrowse files
This policy encompasses Infra's approach to upgrades of Jenkins, Confluence and Jira and their respective plugins.
5
5
6
-
#Upgrades
6
+
## Jenkins
7
7
8
-
### Jenkins
9
-
10
-
**Main Jenkins instance**
8
+
### Main Jenkins instance
11
9
_Upgrades once a quarter_
12
10
13
-
Infra follows the <ahref="https://jenkins.io/download/lts/"target="_blank">LTS line of releases</a>, which the Jenkins Project releases on a 12week cycle. Once every three months, on the last Saturday or Sunday of the month following the Jenkins LTS release, ASF Infra upgrades the main instance.
11
+
Infra follows the <ahref="https://jenkins.io/download/lts/"target="_blank">LTS line of releases</a>, which the Jenkins Project releases on a 12-week cycle. Once every three months, on the last Saturday or Sunday of the month following the Jenkins LTS release, ASF Infra upgrades the main instance.
14
12
15
-
**Jenkins plugins**
16
-
_Upgrades once a month_
13
+
### Jenkins plugins
14
+
_Upgrade once a month_
17
15
18
16
We upgrade all plugins (there are more than 200!) before and after the main instance upgrade, as appropriate, and at the end of each month when there is no main instance upgrade to perform.
19
17
20
-
###Jira
18
+
## Jira
21
19
22
-
**Main Jira instance**
20
+
### Main Jira instance
23
21
_Upgrades every six months_
24
22
25
23
Jira gets a new release every two to six weeks, far too often (and unpredictable) for us to upgrade every release they make. Infra upgrades our Jira instance to whatever the latest release is every six months.
26
24
27
-
**Jira plugins**
28
-
_Upgrades every two months_
25
+
### Jira plugins
26
+
_Upgrade every two months_
29
27
30
28
We upgrade Jira plugins before or after each main instance upgrade, as appropriate, and once every two months between main instance upgrades.
31
29
32
-
###Confluence
30
+
## Confluence
33
31
34
-
**Main Confluence instance**
32
+
### Main Confluence instance
35
33
_Upgrades every six months_
36
34
37
35
Our goal is to upgrade Confluence to the latest version twice a year.
38
36
39
-
**Confluence plugins**
40
-
_Upgrades every two months_
37
+
### Confluence plugins
38
+
_Upgrade every two months_
41
39
42
40
Every two months we perform upgrades to plugins that are compatible with the version of the main Confluence instance we are running.
43
41
44
-
# Documentation
42
+
##Documentation
45
43
46
44
Infra documents what we upgraded and when, from what version to what version, on these pages:
47
45
@@ -52,10 +50,10 @@ Infra documents what we upgraded and when, from what version to what version, on
Since Jenkins, Jira and Confluence are **Core Services**, Infra issues a notice of a planned upgrade at least 72 hours ahead of the event on the wiki or a web page and by emails to the `[email protected]`, `[email protected]` and `[email protected]` mailing lists.
58
56
59
-
# In case of emergencies
57
+
##In case of emergencies
60
58
61
59
Occasionally things go wrong with a main or plugin upgrade, and security issues may arise. If we determine that there is an issue, we will work on it immediately until we resolve it. We will send an email to the relevant list about any unexpected downtime.
0 commit comments