Join Log in
Score:0
kmalarski avatar Server

How to test updates of Jenkins and its plugins on a cloned docker container with volume

kp flag
kmalarski

I migrated this question from SO due to lack of feedback.

I am running an instance of Jenkins on a docker container and, most likely as a result of some mistakes in learning how to configure it, I ended up having an "anonymous" volume holding the state of it that I currently link as follows:

sudo docker run --name=my_name --mount source=my_long_volume_id,target=/var/jenkins_home [command continues]

Now, I would like to test how the plugins' updates, as well as the update of Jenkins itself work. The question is: how can I do it safely (i.e. not touching the running instance)? Because if I run another instance linking the same volume, the original instance would be simultaneously affected. But if I do not link this volume, I would need to manually install all the "not-updated-yet" versions of everything to test the exact same situation.

Maybe alternatively, is there a reasonable way I can clone the volume itself so that I can rerun this container with the "testing-clone" of the volume?

24
0 + 0
ธงชาติไทย
Elon Musk
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.