Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,458,867
Community Members
 
Community Events
176
Community Groups

Skip home zip during upgrade when using a response file

Edited
Onno van der Straaten
Onno van der Straaten Oct 24, 2020

Purportedly per Atlassian doc it should be possible to skip home zip creation when performing an unattended /automated upgrade. A home directory can become quite large so in real life cases not an option or very unpractical.

A manual upgrade will create a response file reponse.varfile with option

backupConfluence$Boolean=false

However, when you feed the installer with this option, the installer will still create the home zip!

There are more options that are ignored for example the option

launch.application$Boolean=false

will not stop the application from launching. BTW, this option comes from Atlassian documentation https://confluence.atlassian.com/doc/unattended-installation-838416261.html

The installer itself generates a different option

executeLauncherAction$Boolean=true

 

 

 

 

Comment
Watch
Like Be the first to like this
254 views

1 comment

Onno van der Straaten
Onno van der Straaten Oct 25, 2020

As it turns out this is a known issue for some time now see CONFSERVER-35722

My workaround for this problem is to delete other reponse.varfile files that might be picked up by Confluence.

Like
Reply

Comment

Log in or Sign up to comment
Confluence
Confluence
TAGS

Atlassian Community Events

See all events