Skip to content

Please provide AppImage for download on GitHub Releases #1092

Closed

Description

@probonopd

Please provide the AppImage for download on GitHub Releases, thanks.

Reference:
AppImage/appimage.github.io#15

Activity

  1. justinclift commented on Aug 18, 2017

    @justinclift
    Member

    Good timing. Working on our 3.10.0 release bits soon. 😄

  2. justinclift commented on Aug 18, 2017

    @justinclift
    Member

    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? 😉

  3. probonopd commented on Aug 18, 2017

    @probonopd
    ContributorAuthor
  4. justinclift commented on Aug 18, 2017

    @justinclift
    Member

    k, I'll probably muck around with this tomorrow and see if I can figure it out. 😄

  5. justinclift commented on Sep 2, 2017

    @justinclift
    Member

    @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).

  6. probonopd commented on Sep 2, 2017

    @probonopd
    ContributorAuthor

    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.

  7. justinclift commented on Sep 2, 2017

    @justinclift
    Member

    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

  8. justinclift commented on Sep 2, 2017

    @justinclift
    Member

    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. 😄

  9. justinclift commented on Sep 2, 2017

    @justinclift
    Member

    ... and then looking at the source there's an obvious RELEASE_NAME variable. Testing now. 🙄

  10. probonopd commented on Sep 2, 2017

    @probonopd
    ContributorAuthor

    Is there any way to change the title for the release it generates to "Continuous Linux build" instead of just "Continuous build"?

    Sure, it's just a bash script...

  11. 106 remaining items

  12. MKleusberg commented on Aug 15, 2020

    @MKleusberg
    Member

    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.

  13. deepsidhu1313 commented on Aug 21, 2020

    @deepsidhu1313
    Contributor

    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.

  14. justinclift commented on Aug 22, 2020

    @justinclift
    Member

    @deepsidhu1313 No worries at all, we all go through stages like that. 😁

  15. mgrojo commented on Nov 9, 2020

    @mgrojo
    Member

    For me, current continuous build AppImage runs well under Ubuntu 18.04.

    Built for x86_64-little_endian-lp64, running on x86_64
    Qt Version 5.5.1
    SQLCipher Version 3.2.0 (based on SQLite 3.8.6).

  16. mgrojo commented on Feb 5, 2021

    @mgrojo
    Member

    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.

  17. justinclift commented on Feb 6, 2021

    @justinclift
    Member

    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... 😄

  18. mgrojo commented on Feb 6, 2021

    @mgrojo
    Member

    Yes, that's the simplest approach. We can do that until someone comes up with a more general solution.

  19. FriedrichFroebel commented on Feb 6, 2021

    @FriedrichFroebel
    Contributor

    Have you tried using the environment variables provided by Travis instead, especially TRAVIS_BRANCH for 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.

  20. mgrojo commented on Feb 6, 2021

    @mgrojo
    Member

    Thanks, @FriedrichFroebel, that's very useful.

  21. MKleusberg commented on Feb 10, 2023

    @MKleusberg
    Member

    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.

  22. probonopd commented on Feb 14, 2023

    @probonopd
    ContributorAuthor

    Thank you very much @MKleusberg.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions