Shamil's Blog. Software Engineering Processes, Android, CI, Devops.

Upgrade involves:

1. dependency versions chain upgrade: studio -> gradle plugin -> kotlin version
2. solving mysterious problems with desugaring D8 (add "android.enableD8.desugaring=false" to gradle.properties)

I'm not very happy when I'm unexpectedly forced to spend 3h+ on infinite chain of tasks. This repeats itself for most of the Android Studio upgrades.

Labels: android, android studio, kotlin, upgrade

I've recently bought a Jira license in order to have my own bugtracker for projects I do. For my projects I personally like to use classical bugtracking, which cannot be fully replaced by something like Trello.
When the time came to update Jira version, the quick check shown that there's no way to update Jira in any automatic way. Administrator must each time go to web site, choose OS version, start download, abort it, copy link from Downloads and wget- or curl- it on server. Then manually unpack it and play with symlinks (or some other way to gracefully abort upgrade if one prefers).
Seems like in this case Atlassian has some business requirements that override product usability. This is first sign that the product design is drawn by primarily interests of non-tech people in Atlassian. As long as Jira product is sold to support the technical process and make it cheaper, this decision to make update process unstable (as it needs special attention), this ruins my trust in product and company in general. To understand the scale of this decision just imagine that for example 10 different products on your servers need manual update process. This is at least annoying and bug-prone because involves human factor. So from my point of view this is a clear sign that (1) either company generates enough money to let marketing people make shitty decisions and override technical ones and not to think about competitors or (2) company's left hand does not know (and care) about right one. Any of which is very bad from the client point of view. Any good alternatives for a bugtracker?

Labels: autoupdate, bugtracker, bugtracking, jira, linux, manual, no-autoupdate, shit, upgrade

Last week I downgraded Google Play using "Uninstall updates" button (on android ver 2.3.4), so I got fast Market app back (v. 2.3.4). Old Market app worked good and installed apps without problems, but when I needed to test In-app-billing, it for sure did not work :-) (Google requires ) So I tried to force it autoupdate (usually Market and Play apps updated automatically). I even installed all-hated Google Services Framework and Play Services, hoping that they will help Market to autoupdate. They did not. I followed recommendations to clear Market cache and data, but it only cleared list of "My apps". $%$#$&!

So the only way was to manually update Market to Play. As this is original apk signed with Google keys, all went OK. IAB working now.

Labels: android, autoupdate, downgrade, evil, framework, google, market, play, services, update, upgrade

there's bug, more info: password is always required, no key auth. Need to upgrade to 0.62 (beta?) here

Labels: bug, bugfix, far, pageant, putty, upgrade, winscp

Today I upgraded my office workstation from Ubuntu 9.04 to 10.04. While upgrading it frozen twice, but after soft rebooting (via ssh from another computer) and using startx to get X up, then re-starting upgrade manager again, everything is ok. (I would be surprised if upgrade was without problems, 'cas it's opensource ;-). sorry. )
My theme worked ok (only the wallpaper has gone), but moving window close and min/max buttons to the left is amazingly uncomfortable. To resolve this run 'gconf-editor' from command-line, it opens gnome configuration editor, just like windows registry editor (very much like!). Then just change this key's value:

/apps/metacity/general/button_layout

to:

menu:minimize,maximize,close

Changes applies immediately after saving value.

Labels: 10.04, opensource, shit, ubuntu, upgrade, window manager