Closed (fixed)
Project:
DrupalCI: Environments
Component:
PHP Containers
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
7 Oct 2016 at 23:17 UTC
Updated:
26 Jan 2017 at 03:34 UTC
Jump to comment: Most recent
Comments
Comment #2
cilefen commentedComment #3
MixologicIt's totally vestigial, from when drupal was exposing all kinds of php7 bugs.
Now that php7 has moved on to 7.1, I would agree that chasing the tip of 7.0 isnt ideal.
We just got some new things merged into dev today, and are working on a refactor that will make this easier to adapt to.
Ideally we do something simple with the php7 containers, like pick a release and call it done, knowing that we can add back in the web-7-dev stuff later.. Otherwise, it falls squarely in the middle of colliding with the work we are in the midst of.
Would that be acceptable?
Comment #4
cilefen commentedThat works for me. -dev can be a separate issue.
Comment #5
andypostSo now 7.1 released and maybe a time to create -dev version?
Comment #6
cilefen commented@Mixologic Do you want separate issues for:
Comment #7
elachlan commentedMoved to DrupalCI Environments.
Comment #8
damienmckennaComment #9
elachlan commentedThis is related to #2609560: Base DCI containers off official containers. Which should fix this issue, once completed.
Comment #10
elachlan commentedComment #11
MixologicBoth php 7.0 and 7.1 now run on stable versions, with options to test against 7.0.x and 7.1.x if necessary. The php 7 runs 7.0.14 and 7.1 runs 7.1.0 currently, and the plan is to continously upgrade those to their highest available patch version as they become available.