# Status of ci.qa.php.net? - Thread: https://externals.io/message/102975 - Original archive: https://news-web.php.net/php.internals/102975 - Started by Christoph M. Becker on 2018-07-26T09:34:52+00:00 - Messages: 7 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · RFCs at https://externals.io/rfc.md · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #102975 — Christoph M. Becker — 2018-07-26T09:34:52+00:00 URL: https://externals.io/message/102975#102975 Hi! refers to , but the latter appears to be unavailable. It seems the site was about Jenkins CI – has it been superseeded by Travis and Appveyor? If so, qa.php.net should be updated. -- Christoph M. Becker --- ## #102976 — Ferenc Kovacs — 2018-07-28T11:04:35+00:00 URL: https://externals.io/message/102975#102976 · In reply to: #102975 On Thu, Jul 26, 2018 at 11:34 AM, Christoph M. Becker wrote: > Hi! > > refers to , but the latter > appears to be unavailable. It seems the site was about Jenkins CI – has > it been superseeded by Travis and Appveyor? If so, qa.php.net should be > updated. > > -- > Christoph M. Becker > > -- > > > > Hi, it was mostly managed and used by me and at one point it went down and I did not had the time to contact the provider and figure out what happened. I'm fine with being removed or if you think that it would be useful we can try bringing it back. -- Ferenc Kovács @Tyr43l - http://tyrael.hu --- ## #102984 — Christoph M. Becker — 2018-07-30T12:44:28+00:00 URL: https://externals.io/message/102975#102984 · In reply to: #102976 > On Thu, Jul 26, 2018 at 11:34 AM, Christoph M. Becker > wrote: > > > […] > > it was mostly managed and used by me and at one point it went down and I > did not had the time to contact the provider and figure out what happened. > I'm fine with being removed or if you think that it would be useful we can > try bringing it back. Thanks, Ferenc! I think, now that we're having Travis and Appveyor, there's not much need for having our own Jenkins, and I think it's more worthwhile to actually cater to the user submitted test reports. I'll remove the ci.qa.php.net related stuff from the QA website in a few days. -- Christoph M. Becker --- ## #103008 — mail@pmmaga.net — 2018-08-01T18:29:05+00:00 URL: https://externals.io/message/102975#103008 · In reply to: #102984 On Mon, Jul 30, 2018 at 1:44 PM Christoph M. Becker wrote: > > > > […] > be > > […] > happened. > > […] > can > > […] > > Thanks, Ferenc! I think, now that we're having Travis and Appveyor, > there's not much need for having our own Jenkins, and I think it's more > worthwhile to actually cater to the user submitted test reports. > > I'll remove the ci.qa.php.net related stuff from the QA website in a few > days. > Hi all, Although travis and appveyor do most of the work, I think there is still some value in having our own Jenkins. Namely, the ability to run other test suites for each change in the PHP repo. IIRC, the old jenkins instance was also running the wordpress tests for every change to PHP, which can help us find issues earlier. I have been maintaining a Jenkins instance for PHP that you can find in https://php-ci.pmmaga.net/ with the configuration and pipeline definitions in https://github.com/pmmaga/php-jenkins-pipelines If anyone finds some value in having something like this and wishes to revive our instance, I'd be glad to help setting it up. If we feel that Travis + Appveyor are enough, that's fine too :) Regards, Pedro --- ## #103075 — Christoph M. Becker — 2018-08-10T11:19:27+00:00 URL: https://externals.io/message/102975#103075 · In reply to: #103008 > Although travis and appveyor do most of the work, I think there is still > some value in having our own Jenkins. Namely, the ability to run other test > suites for each change in the PHP repo. IIRC, the old jenkins instance was > also running the wordpress tests for every change to PHP, which can help us > find issues earlier. I have been maintaining a Jenkins instance for PHP > that you can find in https://php-ci.pmmaga.net/ with the configuration and > pipeline definitions in https://github.com/pmmaga/php-jenkins-pipelines > > If anyone finds some value in having something like this and wishes to > revive our instance, I'd be glad to help setting it up. If we feel that > Travis + Appveyor are enough, that's fine too :) Well, on further consideration it seems that having our own CI would be nice, especially if we'd run further test suites or different configurations there. On the other hand, someone would actually to have a look at the test results, and act on failing tests. Any volunteers? -- Christoph M. Becker --- ## #103093 — mail@pmmaga.net — 2018-08-13T16:07:36+00:00 URL: https://externals.io/message/102975#103093 · In reply to: #103075 On Fri, Aug 10, 2018 at 12:19 PM Christoph M. Becker wrote: > > > […] > > Well, on further consideration it seems that having our own CI would be > nice, especially if we'd run further test suites or different > configurations there. On the other hand, someone would actually to have > a look at the test results, and act on failing tests. Any volunteers? > > -- > Christoph M. Becker > I'd say that if we want this, then it should be integrated with github and be a third check (next to travis and appveyor). Depending on the stability, it could be a required or an optional check. This would be better than expecting someone to manually check it. Regards, Pedro --- ## #103094 — Ferenc Kovacs — 2018-08-13T17:17:34+00:00 URL: https://externals.io/message/102975#103094 · In reply to: #103093 > On Fri, Aug 10, 2018 at 12:19 PM Christoph M. Becker > wrote: > > > […] > > I'd say that if we want this, then it should be integrated with github and > be a third check (next to travis and appveyor). Depending on the stability, > it could be a required or an optional check. This would be better than > expecting someone to manually check it. > > Regards, > Pedro > the integration part is the easiest ( all of the mainstream products are supporting github and the pushing the build results ). I think first we should figure out what do we want exactly, what is missing from our current CI pipeline (more platforms, more resources, we want to be able to log into the build environment for better debuging, etc.), depending on the answers we can figure out if we want another SaaS offering or to build our own and what product/tool do we want to use. -- Ferenc Kovács @Tyr43l - http://tyrael.hu