Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable Travis CI #172

Closed
wants to merge 3 commits into from
Closed

Enable Travis CI #172

wants to merge 3 commits into from

Conversation

b4n
Copy link
Member

@b4n b4n commented Oct 21, 2014

_This has to be discussed a little before merging_

Here it is a bit more complex than on Geany, but it's also probably more important. Same concern applies than on Geany, so I won't repeat myself here and concentrate on technical questions.

  1. We need a recent Geany (we can't simply install the Ubuntu 12.04 package). Here I made the setup rules build it from latest Git, but it might not be so great:
    1. Any build issue in Geany git will break GP.
    2. It means we rebuild from source each time. Maybe a better solution would be to install from the nightly builds .debs but unfortunately the Wheezy ones aren't compatible with Ubuntu 12.04.
  2. As you can see with the additional commit, I couldn't build GeanyPy because Ubuntu 12.04 don't seem to have libpython-dev, which is quite weird.
  3. As you can also see, I had a fairly weird problem with cppcheck that I can't reproduce on my machine (which has cppcheck 1.66). If anyone can tell me what's going on here, please go ahead (especially as other cppcheck calls worked fine, see above in the log).

Finally, you might see that the GTK2 build currently fails, but that's legitimate, see #171 (so that's a good point for Travis CI as I found the error when setting it up :).

eht16 referenced this pull request Jan 17, 2016
The previous symlink cycle detection would check if the child directory is
within parent. This however breaks the case where in the root of the
project there are symlinks to directories outside the project directory.

Fix this by simply recording the resolved real paths during the tree
creation. Skip subtree creation if the path was visited previously.
@eht16
Copy link
Member

eht16 commented Jan 17, 2016

To wake this one up: regarding the question how to get an up2date version of Geany into the build environment: I'd prefer the nightly builds way.
In the meantime, Travis offers Ubuntu 14.04 as beta environment (https://docs.travis-ci.com/user/ci-environment). Maybe we can check this, it might also help solving the geanypy problems.
The Debian Wheezy nightly builds install fine in Ubuntu 14.04.
Alternatively, we could also setup a nightly build for Ubuntu 12.04. However, this seems a bit overkill just for Travis because I guess normal users have already upgraded their Ubuntus to more recent versions.

And in theory the nightly builds approach has the disadvantage if we change some API in Geany and on the same day use this new API in G-P, the nightly builds will be too old.
Though I think this won't happen too often and/or we could maybe shorten the nightly interval from 24h to 12h hours or even less (they won't rebuild if there were no changes in GIT master).

@b4n b4n mentioned this pull request Mar 7, 2016
9 tasks
@b4n
Copy link
Member Author

b4n commented Mar 9, 2016

Obsoleted by #394

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants