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
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?
The text was updated successfully, but these errors were encountered:
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 variableTRAVIS_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?
The text was updated successfully, but these errors were encountered: