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

Automatically ship daily builds #19

Open
iloveeclipse opened this issue Jul 1, 2017 · 4 comments
Open

Automatically ship daily builds #19

iloveeclipse opened this issue Jul 1, 2017 · 4 comments

Comments

@iloveeclipse
Copy link
Member

iloveeclipse commented Jul 1, 2017

I wonder if we can somehow automate the spotbugs build on github so after merging a PR it could upload generated "daily" build (and Eclipse update site) to the server?

@KengoTODA
Copy link
Member

maybe we can use cron build supported by Travis CI.
https://docs.travis-ci.com/user/cron-jobs/

@iloveeclipse
Copy link
Member Author

What about this: https://docs.travis-ci.com/user/deployment/pages/?

Or we can automatically create tags on each merged pull request and copy the bits to releases: https://docs.travis-ci.com/user/deployment/releases/

I must say I have no experience with travis at all so just guessing here.

@koppor
Copy link

koppor commented Jul 15, 2017

In JabRef, we host our own server on ScaleWay and upload the builds via ssh to https://builds.jabref.org/. The source of the script is available at https://github.com/JabRef/jabref/blob/master/scripts/upload-to-builds.jabref.org.sh

In case one does not want to maintain a separate server, the build artifacts from CircleCI could be a solution. Let CircleCI build the artifacts and publish the link to gh-pages.

In JabRef, we also use CircleCI for building binaries. See https://github.com/JabRef/jabref/wiki/CI.

@KengoTODA
Copy link
Member

I tried to use GitHub Pages Deployment feature, here is diff: master...KengoTODA:62751c96

This is not so good because it generates huge commit like this. This is expected behaviour and we can see note in description page like below:

Deploying to GitHub Pages uses git push --force to overwrite the history on the target branch, so make sure you only deploy to a branch used for that specific purpose, such as gh-pages.

I will try to make encrypted SSH key or personal access token to push changes by git push command.

KengoTODA added a commit to KengoTODA/spotbugs.github.io that referenced this issue Jul 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants