1276155 - update gaia webapps

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia, defect)

Description

[Jovan Gerodetti]

Ben, Alberto, can we setup a way to update the gh-pages versions of the gaia webapps with the versions in pine / master?

I'm thinking of two types. One automatic update after every merged commit inside "gaia/webapps_dev" and one in "gaia/webapps/" which we need to update manually after we made sure that no app is broken.

Comment 1

[Ben Francis [:benfrancis]]

Yeah I know how to do it manually but I don't know how to do the automatic push/merge/rebase on commit.

What would be in webapps_dev and what would be in webapps?

Comment 2

[Jovan Gerodetti]

Well I was thinking that webapps_dev would contain the latest version, like a nightly build and webapps our latest stable release.

For the automatic update, can we create a merge web hook triggering a script that preforms the gh-pages update? Do we have a place where this could be hosted on? We'd need a small script that can clone gaia, checkout kanikani or later master, copy all apps to gh-pages/webapps_dev and push that.

What do you think?

Comment 3

[Ben Francis [:benfrancis]]

> Well I was thinking that webapps_dev would contain the latest version, like a nightly build and webapps our latest stable release.

I'm not sure this is the best way to use our version control. I would suggest a single master version of the latest code which should be in a working state at all times, then we'll eventually branch release branches off master to stabilise.

> For the automatic update, can we create a merge web hook triggering a script that preforms the gh-pages update? Do we have a place where this could be hosted on? We'd need a small script that can clone gaia, checkout kanikani or later master, copy all apps to gh-pages/webapps_dev and push that.

Sounds good, can this be hosted on GitHub itself? In the meantime we can manually merge master in gh-pages periodically when we have something to merge.