<p>That's not true. Immutable servers simply means that the servers cannot be changed but the can be deleted and created from the updated source code.</p>

CC BY-SA 4.0
2021-09-07T10:44:49.480Z
Please add further details to expand on your answer, such as working code or documentation citations.
Community
CC BY-SA 4.0
2021-09-06T15:38:09.010Z
2021-09-06T15:38:09.010Z
Greatness Akuma
<p>No.</p>

<p>Immutable is exactly what it means, immutable, no change on configuration or code running or system library or whatever, if a change has to be made, create a new image and deploy it, never change it while running.</p>

<p>Source code updates are the least thing to change on a running server, this should not happen on a running server, immutable or not. </p>

<p>You should create a versioned release of your code to deploy on servers, once you have this level of fixed versioning you can step ahead to versioning your server image which include this code release.</p>

<p>Any change, being a code patch or a system patch or a configuration change should trigger a new release to be deployed.</p>

CC BY-SA 3.0
2018-03-09T13:16:31.837Z
2018-03-09T13:16:31.837Z
Tensibai
<p>So once an Immutable Server is in place, nothing should change at all. Or is it only configuration.</p>

<p>Are source code updates acceptable on Immutable Servers?</p>

CC BY-SA 3.0
2018-03-09T13:39:11.290Z
If the source code repository is pulled *after* the server is brought up (i.e. not included in the server configuration itself) or is in a workspace hosted elsewhere (mounted via NFS, for example) that's part of the server operation and IMHO updating such code should be OK. I'm assuming something like a build server here.
Dan Cornilescu
<continuous-integration><continuous-delivery><continuous-deployment><immutable-servers>
Does Immutable Servers imply no source code updates on the servers?
Basil A
# Does Immutable Servers imply no source code updates on the servers?

(Asked by: username_0 on 2018-03-09)

So once an Immutable Server is in place, nothing should change at all. Or is it only configuration.

Are source code updates acceptable on Immutable Servers?

**Tags:** continuous-integration, continuous-delivery, continuous-deployment, immutable-servers

> **Comments:**
> **username_1**: If the source code repository is pulled *after* the server is brought up (i.e. not included in the server configuration itself) or is in a workspace hosted elsewhere (mounted via NFS, for example) that's part of the server operation and IMHO updating such code should be OK. I'm assuming something like a build server here.  

---

## 2 answers

### Answer by username_4 on 2018-03-09. Score: 7 | Accepted answer

No.

Immutable is exactly what it means, immutable, no change on configuration or code running or system library or whatever, if a change has to be made, create a new image and deploy it, never change it while running.

Source code updates are the least thing to change on a running server, this should not happen on a running server, immutable or not.

You should create a versioned release of your code to deploy on servers, once you have this level of fixed versioning you can step ahead to versioning your server image which include this code release.

Any change, being a code patch or a system patch or a configuration change should trigger a new release to be deployed.


---

### Answer by username_2 on 2021-09-06. Score: 0

That's not true. Immutable servers simply means that the servers cannot be changed but the can be deleted and created from the updated source code.

> **Comments:**
> **username_3**: Please add further details to expand on your answer, such as working code or documentation citations.  

---

