[Wikidata-bugs] [Maniphest] [Edited] T192006: wdqs-frontend docker image should rebuild automatically when a new patch is pushed to master
Addshore updated the task description. (Show Details) CHANGES TO TASK DESCRIPTION...Instead some jenkins / github hook should hit the travis API / trigger a new build As this requires a travis token it might be an idea to use a specific account for it that only has access to the wikibase-docker repo under the wmde org. We have such a user, https://github.com/WikidataBuilder, the question is, who still has the password? **Posible solution**...TASK DETAILhttps://phabricator.wikimedia.org/T192006EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: AddshoreCc: Addshore, Aklapper, Lahi, Gq86, GoranSMilovanovic, QZanden, Gstupp, LawExplorer, Abbe98, Jonas, Wikidata-bugs, aude, Lydia_Pintscher, Mbch331___ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
[Wikidata-bugs] [Maniphest] [Edited] T192006: wdqs-frontend docker image should rebuild automatically when a new patch is pushed to master
Addshore updated the task description. (Show Details) CHANGES TO TASK DESCRIPTIONCurrently the wdqs-frontend docker image builds from master, but only when build is manually triggeredered, or a new commit is made to wikibase-docker wmde git repo**Posible solution** Triggering builds with the API: https://docs.travis-ci.com/user/triggering-build Webhooks could also work but they would require some extra service to look at the webhooks and determine when the merge actually happened on master... We could look into a gerrit plugin (as in T87768#3958112) using the API... We could create a tiny jenkins job triggering the travis API The jenkins job could be small and generic, triggering the master build of the given github repo on travis. Possible ENV vars for the image: - AUTH_HEADER (secret token) Triggering builds with the API: https://docs.travis-ci.com/user/triggering-builds / a webhook - REPO (example wmde/wikibase-docker) We could creatThis will require a tiny jenkins job triggering theravis user token for the requests.. We could also create a small travis API,job on the GUI repo... or look into a gerrit plugin (as in T87768#3958112)https://github.com/wikimedia/wikidata-query-gui triggering the same API request..TASK DETAILhttps://phabricator.wikimedia.org/T192006EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: AddshoreCc: Addshore, Aklapper, Lahi, Gq86, GoranSMilovanovic, QZanden, Gstupp, LawExplorer, Abbe98, Jonas, Wikidata-bugs, aude, Lydia_Pintscher, Mbch331___ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
[Wikidata-bugs] [Maniphest] [Edited] T192006: wdqs-frontend docker image should rebuild automatically when a new patch is pushed to master
Addshore updated the task description. (Show Details) CHANGES TO TASK DESCRIPTION...Triggering builds with the API: https://docs.travis-ci.com/user/triggering-builds / a webhook We could create a tiny jenkins job triggering the travis API, or look into a gerrit plugin (as in T87768#3958112)TASK DETAILhttps://phabricator.wikimedia.org/T192006EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: AddshoreCc: Addshore, Aklapper, Lahi, Gq86, GoranSMilovanovic, QZanden, Gstupp, LawExplorer, Salgo60, Abbe98, Jonas, Wikidata-bugs, aude, Lydia_Pintscher, Mbch331___ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
[Wikidata-bugs] [Maniphest] [Edited] T192006: wdqs-frontend docker image should rebuild automatically when a new patch is pushed to master
Addshore updated the task description. (Show Details) CHANGES TO TASK DESCRIPTION...Instead some jenkins / github hook should hit the travis API / trigger a new build **Posible solution** Triggering builds with the API: https://docs.travis-ci.com/user/triggering-builds We could create a tiny jenkins job triggering the travis API, or look into a gerrit plugin (as in T87768#3958112)TASK DETAILhttps://phabricator.wikimedia.org/T192006EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: AddshoreCc: Addshore, Aklapper, Lahi, Gq86, GoranSMilovanovic, QZanden, Gstupp, LawExplorer, Salgo60, Abbe98, Jonas, Wikidata-bugs, aude, Lydia_Pintscher, Mbch331___ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
[Wikidata-bugs] [Maniphest] [Edited] T192006: wdqs-frontend docker image should rebuild automatically when a new patch is pushed to master
Addshore updated the task description. (Show Details) CHANGES TO TASK DESCRIPTION...Instead some jenkins / github hook should hit the travis API / trigger a new build Triggering builds with the API: https://docs.travis-ci.com/user/triggering-buildsTASK DETAILhttps://phabricator.wikimedia.org/T192006EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: AddshoreCc: Addshore, Aklapper, Lahi, Gq86, GoranSMilovanovic, QZanden, Gstupp, LawExplorer, Salgo60, Abbe98, Jonas, Wikidata-bugs, aude, Lydia_Pintscher, Mbch331___ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
[Wikidata-bugs] [Maniphest] [Edited] T192006: wdqs-frontend docker image should rebuild automatically when a new patch is pushed to master
Addshore updated the task description. (Show Details) CHANGES TO TASK DESCRIPTION...Instead some jenkins / github hook should hit the docker cloud building api etc totravis API / trigger a new build.TASK DETAILhttps://phabricator.wikimedia.org/T192006EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: AddshoreCc: Addshore, Aklapper, Lahi, Gq86, GoranSMilovanovic, QZanden, Gstupp, LawExplorer, Abbe98, Wikidata-bugs, aude, Mbch331___ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
