Docker sage upgrade script and new user questions

[Madz]

Nice work wnjj!

[stuckless]

Originally Posted by wnjj

I found a Gradle plugin for publishing GitHub releases. I’ve tested it out on a temp repo and have it working to build the release and add binaries. It should be able to just replace the Bintray one in build.gradle with no other changes needed. The last piece needed is to set up a user & token for Travis to use to access OpenSageTV.

Since you are doing this... you might look at moving to github actions at the same time. Travis appears to be be going away (I think).

[wnjj]

Originally Posted by stuckless

Since you are doing this... you might look at moving to github actions at the same time. Travis appears to be be going away (I think).

Worth doing if it means all of it can be just on GitHub. I don’t know if actions supports actions into a different organization but perhaps it does.

For now the quick thing is to swap the plugin. It looks like the preferred/supported method is to create a “machine user” on GitHub that has write access to OpenSageTV. I assume the easiest way to do that is to have Jeff create that user and I can give it permissions? That way he can create the token and add it to the travis environment variables.

It looks like travis-ci.org is just migrating to travis-ci.com and it’s supposedly quick to do but I don’t know why it’s all happening or what that means for the future.

[stuckless]

Originally Posted by wnjj

Worth doing if it means all of it can be just on GitHub. I don’t know if actions supports actions into a different organization but perhaps it does.

For now the quick thing is to swap the plugin. It looks like the preferred/supported method is to create a “machine user” on GitHub that has write access to OpenSageTV. I assume the easiest way to do that is to have Jeff create that user and I can give it permissions? That way he can create the token and add it to the travis environment variables.

It looks like travis-ci.org is just migrating to travis-ci.com and it’s supposedly quick to do but I don’t know why it’s all happening or what that means for the future.

I did migrate all our repos (yesterday) to travis-ci.com, using the migrate option. So not sure what that means, but we should be good in that they are migrated.

I agree that Github Actions is better longer term plan. I haven't done anything myself using actions, but, it seems pretty straight forward. They also support doing windows builds, so, it would be possible to create a linux/windows release build from Actions.

[wnjj]

The code has been modified and Travis-CI successfully uploaded to GitHub. Version 9.2.5 can be found here: https://github.com/OpenSageTV/sagetv.../tag/9.2.5.168

[wayner]

Has the docker been rebuilt with the latest version? So if I restart the docker will it upgrade to the latest version? I am on 9.2.268 and here is what my log shows:

*** Running /etc/my_init.d/10-adduser...
*** Running /etc/my_init.d/20-upgrade-sagetv...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
SageTV Home: /opt/sagetv/server
Could not check online version. Trying to continue with currently installed version

[stuckless]

Originally Posted by wayner

Has the docker been rebuilt with the latest version? So if I restart the docker will it upgrade to the latest version? I am on 9.2.268 and here is what my log shows:

*** Running /etc/my_init.d/10-adduser...
*** Running /etc/my_init.d/20-upgrade-sagetv...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
SageTV Home: /opt/sagetv/server
Could not check online version. Trying to continue with currently installed version

Yep, the install files are/were hosted on bintray but since that is no more, the upgrade cannot work.