You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Please provide AppImage for download on GitHub Releases #1092
Is there any way to change the title for the release it generates to "Continuous Linux build" instead of just "Continuous build"? Pretty sure it'll be confusing to newbie users on Windows and/or OSX otherwise. 😄
The backtrace says that the crash happens while loading a certificate file and I assume the SSL errors are printed while that is happening. To me this looks like the SSL library is not included in the AppImage file or something similar.
Sorry guys, I have been recently very occupied with work. I will try building it on my forked repo then will create merge request if everything goes well.
I've made a change in order to get continuous AppImage builds in the v3.12.x and the generated image is working for me. Using this, we could manually upload that AppImage when we release v3.12.2. The change is not expected to be merged to the master branch, and having a unified version would require a more elaborated configuration.
The current image does not match v3.12.1 because we have already advanced one commit in the branch.
My intention was that the continuous release would be called Continuous build (v3.12.x) but the command git rev-parse --abbrev-ref HEAD is not returning the branch name in the travis server; I don't know why.
That's a good idea. For the naming problem, is it something that could be solved by simply hard coding the correct name? It seems the config file there is only used for the v3.12.x branch anyway... 😄
Closing this since we have had AppImage for quite a while now 😃 I'd say any remaining issues with the AppImages (if there are any) are probably a new issue.
Activity
justinclift commentedon Aug 18, 2017
Good timing. Working on our 3.10.0 release bits soon. 😄
justinclift commentedon Aug 18, 2017
k, to make this happen, what do we need to do? Is there an example "best practice" one I can look at and pretty much cut-n-paste what they did? 😉
probonopd commentedon Aug 18, 2017
Check out https://github.com/probonopd/uploadtool
justinclift commentedon Aug 18, 2017
k, I'll probably muck around with this tomorrow and see if I can figure it out. 😄
justinclift commentedon Sep 2, 2017
@deepsidhu1313 You mentioned an interest in Snap packaging on Linux. Any interest in AppImage packages too? 😄
Ahhh, ignore that. Seems things are mostly setup atm and just needs a bit of tweaking (as per below).
probonopd commentedon Sep 2, 2017
In case you are not aware, the AppImage is already being built for each git push on Travis CI. It is just not uploaded to GitHub Releases yet.
justinclift commentedon Sep 2, 2017
k. Looking at it now. I've just done the token generation and added the env variable to Travis. Next step figuring out what to put in .travis.yml
justinclift commentedon Sep 2, 2017
k, seem to have gotten an initial first pass of things working:
Is there any way to change the title for the release it generates to "Continuous Linux build" instead of just "Continuous build"? Pretty sure it'll be confusing to newbie users on Windows and/or OSX otherwise. 😄
justinclift commentedon Sep 2, 2017
... and then looking at the source there's an obvious
RELEASE_NAMEvariable. Testing now. 🙄probonopd commentedon Sep 2, 2017
Sure, it's just a bash script...
106 remaining items
MKleusberg commentedon Aug 15, 2020
The backtrace says that the crash happens while loading a certificate file and I assume the SSL errors are printed while that is happening. To me this looks like the SSL library is not included in the AppImage file or something similar.
deepsidhu1313 commentedon Aug 21, 2020
Sorry guys, I have been recently very occupied with work. I will try building it on my forked repo then will create merge request if everything goes well.
justinclift commentedon Aug 22, 2020
@deepsidhu1313 No worries at all, we all go through stages like that. 😁
mgrojo commentedon Nov 9, 2020
For me, current continuous build AppImage runs well under Ubuntu 18.04.
Get a continuous release with AppImage in the v3.12.x branch
mgrojo commentedon Feb 5, 2021
I've made a change in order to get continuous AppImage builds in the v3.12.x and the generated image is working for me. Using this, we could manually upload that AppImage when we release v3.12.2. The change is not expected to be merged to the master branch, and having a unified version would require a more elaborated configuration.
The current image does not match v3.12.1 because we have already advanced one commit in the branch.
My intention was that the continuous release would be called
Continuous build (v3.12.x)but the commandgit rev-parse --abbrev-ref HEADis not returning the branch name in the travis server; I don't know why.justinclift commentedon Feb 6, 2021
That's a good idea. For the naming problem, is it something that could be solved by simply hard coding the correct name? It seems the config file there is only used for the
v3.12.xbranch anyway... 😄mgrojo commentedon Feb 6, 2021
Yes, that's the simplest approach. We can do that until someone comes up with a more general solution.
FriedrichFroebel commentedon Feb 6, 2021
Have you tried using the environment variables provided by Travis instead, especially
TRAVIS_BRANCHfor the branch name? See https://docs.travis-ci.com/user/environment-variables/#default-environment-variables for the environment variables available by default and what they map to.Simpler version for AppImage and branch name in the continuous release
Generalize branch name in AppImage version and continuous release
mgrojo commentedon Feb 6, 2021
Thanks, @FriedrichFroebel, that's very useful.
MKleusberg commentedon Feb 10, 2023
Closing this since we have had AppImage for quite a while now 😃 I'd say any remaining issues with the AppImages (if there are any) are probably a new issue.
probonopd commentedon Feb 14, 2023
Thank you very much @MKleusberg.