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

Manual edits on jpf-core wiki should get merged #3

Open
cyrille-artho opened this issue Nov 13, 2018 · 0 comments
Open

Manual edits on jpf-core wiki should get merged #3

cyrille-artho opened this issue Nov 13, 2018 · 0 comments

Comments

@cyrille-artho
Copy link
Member

The current setup pushes accepted PRs on this repository to the wiki of jpf-core. However, the reverse direction is not supported. A cron job could be a solution.

However, it's actually not straightforward to pull the changes from the hidden wiki repo to our wiki repository jpf-wiki-sync, via cron.
This is because Travis only allows us to configure to run nightly builds in cron; i.e., it runs the normal build that it would otherwise also run whenever a change is pushed. For our purpose, this is not very useful.
The .travis.yml script we have pushes the changes from jpf-wiki-sync to the wiki of jpf-core. This makes sense for normal changes (merged pull requests to the wiki repo): we want them to be visible on the wiki page of jpf-core.
However, the cron should do the reverse, to merge changes people sometimes make on the wiki web interface: it should pull changes from the wiki of jpf-core, and merge them into master on jpf-wiki-sync. If not successful, it would be good to have an error message; otherwise the script should be quiet.

It is possible in theory to do this with .travis.yml, by checking if environment variable TRAVIS_EVENT_TYPE is set to "cron". However, getting all this to work well according to the criteria above, will take some work.

Perhaps someone can find an example template script, so we simply have to adapt it?

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

No branches or pull requests

1 participant