Hi!
Today I noticed the message on travis-ci.org:
Please be aware travis-ci.org will be shutting down in several weeks,
with all accounts migrating to travis-ci.com. Please stay tuned here for
more information.
As far as I know, our repo is still not migrated. Anybody looked into it?
Also, as I understand, the .com builds will be managed used credits
system, with OSS getting allocated credits:
https://docs.travis-ci.com/user/billing-faq#what-if-i-am-building-open-source
but this has to be done manually. I can reach out to them but wanted to
ask first in case somebody already did.
Looks like we need to take care of it pretty soon or we risk losing
access to the CI.
Stas Malyshev
smalyshev@gmail.com
On Sat, Jan 2, 2021 at 6:51 AM Stanislav Malyshev smalyshev@gmail.com
wrote:
Hi!
Today I noticed the message on travis-ci.org:
Please be aware travis-ci.org will be shutting down in several weeks,
with all accounts migrating to travis-ci.com. Please stay tuned here for
more information.As far as I know, our repo is still not migrated. Anybody looked into it?
Also, as I understand, the .com builds will be managed used credits
system, with OSS getting allocated credits:https://docs.travis-ci.com/user/billing-faq#what-if-i-am-building-open-source
but this has to be done manually. I can reach out to them but wanted to
ask first in case somebody already did.Looks like we need to take care of it pretty soon or we risk losing
access to the CI.
Hi Stas,
We haven't been using Travis as our primary CI for a while already. We use
AppVeyor for Windows testing and Azure Pipelines for everything else. The
only thing Travis is still used for is a daily cron job that tests PHP on
"exotic" architectures like aarch64 and s390x. Having those builds is a
nice to have, but not particularly critical.
Regards,
Nikita
On Sat, Jan 2, 2021 at 6:51 AM Stanislav Malyshev smalyshev@gmail.com
wrote:Today I noticed the message on travis-ci.org:
Please be aware travis-ci.org will be shutting down in several weeks,
with all accounts migrating to travis-ci.com. Please stay tuned here for
more information.As far as I know, our repo is still not migrated. Anybody looked into it?
Also, as I understand, the .com builds will be managed used credits
system, with OSS getting allocated credits:https://docs.travis-ci.com/user/billing-faq#what-if-i-am-building-open-source
but this has to be done manually. I can reach out to them but wanted to
ask first in case somebody already did.Looks like we need to take care of it pretty soon or we risk losing
access to the CI.We haven't been using Travis as our primary CI for a while already. We use
AppVeyor for Windows testing and Azure Pipelines for everything else. The
only thing Travis is still used for is a daily cron job that tests PHP on
"exotic" architectures like aarch64 and s390x. Having those builds is a
nice to have, but not particularly critical.
The exception being the PHP-7.3 branch, which in security mode. Unless
we add GH CI for that branch as well, switching to travis-ci.com seems
to be useful. Maybe we get enough free credits for the relatively rare
builds?
Christoph
Hi!
The exception being the PHP-7.3 branch, which in security mode. Unless
we add GH CI for that branch as well, switching to travis-ci.com seems
to be useful. Maybe we get enough free credits for the relatively rare
builds?
I don't think it's possible to migrate only one branch, but if we
migrate the whole repo and use cron-only builds for upper branches, and
request OSS credits if we run out of free ones, I think we should be OK.
Given that we have 7.3 still which aren't supported by Azure as I
understand, I think we should migrate the repo but not invest too much
into making it work for 8.x, just make it work for more infrequent 7.x
builds. I'm not sure how credits work there yet, but I think we could
ask enough of them to have 7.3 and maybe even 7.4 supported and not
worry too much about the rest.
--
Stas Malyshev
smalyshev@gmail.com
The exception being the PHP-7.3 branch, which in security mode. Unless
we add GH CI for that branch as well, switching to travis-ci.com seems
to be useful. Maybe we get enough free credits for the relatively rare
builds?I don't think it's possible to migrate only one branch, but if we
migrate the whole repo and use cron-only builds for upper branches, and
request OSS credits if we run out of free ones, I think we should be OK.Given that we have 7.3 still which aren't supported by Azure as I
understand, I think we should migrate the repo but not invest too much
into making it work for 8.x, just make it work for more infrequent 7.x
builds. I'm not sure how credits work there yet, but I think we could
ask enough of them to have 7.3 and maybe even 7.4 supported and not
worry too much about the rest.
I meant to switch the repo to travis-ci.com, but to only run PHP-7.3
jobs there (the rest should be migrated to GH actions). As I understand
it, OSS projects get 10k credits for free, which would allow for about
1000 minutes in a Linux environment. If we'd only run a single build
per release (with two jobs), that might just be enough till EOL.
Christoph
The exception being the PHP-7.3 branch, which in security mode. Unless
we add GH CI for that branch as well, switching to travis-ci.com seems
to be useful. Maybe we get enough free credits for the relatively rare
builds?I don't think it's possible to migrate only one branch, but if we
migrate the whole repo and use cron-only builds for upper branches, and
request OSS credits if we run out of free ones, I think we should be OK.Given that we have 7.3 still which aren't supported by Azure as I
understand, I think we should migrate the repo but not invest too much
into making it work for 8.x, just make it work for more infrequent 7.x
builds. I'm not sure how credits work there yet, but I think we could
ask enough of them to have 7.3 and maybe even 7.4 supported and not
worry too much about the rest.I meant to switch the repo to travis-ci.com, but to only run PHP-7.3
jobs there (the rest should be migrated to GH actions). As I understand
it, OSS projects get 10k credits for free, which would allow for about
1000 minutes in a Linux environment. If we'd only run a single build
per release (with two jobs), that might just be enough till EOL.
Any news here? Tomorrow PHP 7.3.27 will be tagged, likely without any
Travis-CI build to confirm that it's not broken on Linux.
Regards,
Christoph
Hi!
Any news here? Tomorrow PHP 7.3.27 will be tagged, likely without any
Travis-CI build to confirm that it's not broken on Linux.
As far as I can see, it's migrated to .com, but we're currently out of
free credits. Not sure how we run through them so fast, we may need to
adjust the cron settings there or reach out to them and ask for OSS
credits. I am a bit busy today but maybe could write tonight or somebody
else could do it. We may also try to limit the users allowed to trigger
the builds...
I have however a 7.3 build here:
https://travis-ci.com/github/smalyshev/php-src/builds/215525375 that
looks fine.
Stas Malyshev
smalyshev@gmail.com
Hi,
Hi!
Any news here? Tomorrow PHP 7.3.27 will be tagged, likely without any
Travis-CI build to confirm that it's not broken on Linux.I have however a 7.3 build here:
https://travis-ci.com/github/smalyshev/php-src/builds/215525375 that
looks fine.
likewise:
https://revive.beccati.com/bamboo/browse/PHP-SRC8-TESTS-897
Sorry it took a while as I broke the build script when PHP-8.0 was
branched and I hadn't had time to check and fix it.
Cheers
Matteo Beccati
Development & Consulting - http://www.beccati.com/