cubicweb issueshttps://forge.extranet.logilab.fr/cubicweb/cubicweb/-/issues2020-06-23T14:41:38Zhttps://forge.extranet.logilab.fr/cubicweb/cubicweb/-/issues/9Build the new cubicweb image for all the intranet apps on the public head2020-06-23T14:41:38ZFabien Amargerfabien.amarger@logilab.frBuild the new cubicweb image for all the intranet apps on the public headThe public head should be used on all Logilab intranet apps. Then these apps could be used to test the last CubicWeb version.The public head should be used on all Logilab intranet apps. Then these apps could be used to test the last CubicWeb version.v3.28https://forge.extranet.logilab.fr/cubicweb/cubicweb/-/issues/44integrates logilab-common changelog's into its own documentation and in CW ch...2020-06-16T12:47:03ZLaurent Peuchintegrates logilab-common changelog's into its own documentation and in CW changelogRight now no one sees it and is aware of it.
Also add it to CW's changelog to say that we've made synchronous release with it.Right now no one sees it and is aware of it.
Also add it to CW's changelog to say that we've made synchronous release with it.v3.28Laurent PeuchLaurent Peuchhttps://forge.extranet.logilab.fr/cubicweb/cubicweb/-/issues/5Add test for the content negociation2020-06-10T07:17:39ZFabien Amargerfabien.amarger@logilab.frAdd test for the content negociationv3.28Fabien Amargerfabien.amarger@logilab.frFabien Amargerfabien.amarger@logilab.frhttps://forge.extranet.logilab.fr/cubicweb/cubicweb/-/issues/10Introduce types2020-06-03T12:34:49ZFabien Amargerfabien.amarger@logilab.frIntroduce typesthen use pytype or mypy or other type checker
start with yams https://www.logilab.org/ticket/10146733
original ticket : https://www.cubicweb.org/ticket/17260453then use pytype or mypy or other type checker
start with yams https://www.logilab.org/ticket/10146733
original ticket : https://www.cubicweb.org/ticket/17260453v3.28Laurent PeuchLaurent Peuchhttps://forge.extranet.logilab.fr/cubicweb/cubicweb/-/issues/43update logilab-common's changelog2020-06-03T09:46:32ZLaurent Peuchupdate logilab-common's changelogWe haven't done that while there quite some modifications.We haven't done that while there quite some modifications.v3.28https://forge.extranet.logilab.fr/cubicweb/cubicweb/-/issues/35Fix tests of CW2020-05-28T08:25:59ZFabien Amargerfabien.amarger@logilab.frFix tests of CWhttps://forge.extranet.logilab.fr/cubicweb/cubicweb/pipelines/7523https://forge.extranet.logilab.fr/cubicweb/cubicweb/pipelines/7523v3.28https://forge.extranet.logilab.fr/cubicweb/cubicweb/-/issues/4Check if content negotiation for next release2020-05-27T13:32:27ZFabien Amargerfabien.amarger@logilab.frCheck if content negotiation for next releaseCheck if content negotiation is well enough to be published in the next release.
By the way, add determine what should be done to improve it.Check if content negotiation is well enough to be published in the next release.
By the way, add determine what should be done to improve it.v3.28https://forge.extranet.logilab.fr/cubicweb/cubicweb/-/issues/7Check if `?vid=rdf` is still working, fix it if is not2020-05-27T13:32:24ZFabien Amargerfabien.amarger@logilab.frCheck if `?vid=rdf` is still working, fix it if is notAfter implementing content negociation, the `?vid=rdf` route leads to an error. Is this what we want?After implementing content negociation, the `?vid=rdf` route leads to an error. Is this what we want?v3.28https://forge.extranet.logilab.fr/cubicweb/cubicweb/-/issues/6fix qunit tests in devtools2020-05-27T12:23:30ZFabien Amargerfabien.amarger@logilab.frfix qunit tests in devtoolshttps://jenkins.logilab.org/job/cubicweb-default/465/TOXENV=py3-misc,distributions=cubicweb/testReport/cubicweb.devtools.test.unittest_qunit/QUnitTestCaseTC/test_simple_failure/ says that xauth is missing.
Add it to the dev requirements...https://jenkins.logilab.org/job/cubicweb-default/465/TOXENV=py3-misc,distributions=cubicweb/testReport/cubicweb.devtools.test.unittest_qunit/QUnitTestCaseTC/test_simple_failure/ says that xauth is missing.
Add it to the dev requirements.
c.f. https://forge.extranet.logilab.fr/cubicweb/cubicweb/-/jobs/25782
original ticket : https://www.cubicweb.org/ticket/17262151v3.28https://forge.extranet.logilab.fr/cubicweb/cubicweb/-/issues/8Rebuild the "readthedoc" for each new release2020-05-27T12:23:08ZFabien Amargerfabien.amarger@logilab.frRebuild the "readthedoc" for each new releaseIt was done in the precedent forge, but it is not implement in the heptapod forge.It was done in the precedent forge, but it is not implement in the heptapod forge.v3.28Laurent PeuchLaurent Peuchhttps://forge.extranet.logilab.fr/cubicweb/cubicweb/-/issues/36Trigger builds of dependents projects when all tests of a project pass2020-05-19T12:40:59ZLaurent PeuchTrigger builds of dependents projects when all tests of a project passBased on this dependency graph:
![dependencies](/uploads/1f41740f7a8c896893669865a8bf21ce/dependencies.png)
Once all the tests of a project passed, the tests of the projects depending on this are triggered to ensure that everything is ...Based on this dependency graph:
![dependencies](/uploads/1f41740f7a8c896893669865a8bf21ce/dependencies.png)
Once all the tests of a project passed, the tests of the projects depending on this are triggered to ensure that everything is green everywhere.
For now this is done using curl but once we'll move to a more recent version of gitlab-heptapod we'll be able to use this way better system: https://docs.gitlab.com/ee/ci/multi_project_pipelines.htmlv3.28