[Starlingx-discuss] Effort to make zuul linters happy
Hi all, Currently the zuul check only verifies linters and some of them fails. The zuul gate stage is disabled to make the integration possible. As it is desirable to use Zuul for gating code merges we need first to solve the linter problems in every repository. I've created a set of stories for each repository to start this effort. Now the only tasks created there is to go into Zuul logs and review what needs to be done to solve the issues and create the related tasks. In case someone wants to join this effort, here is the list of stories. https://storyboard.openstack.org/#!/story/2003359 : stx-clients https://storyboard.openstack.org/#!/story/2003360 : stx-config https://storyboard.openstack.org/#!/story/2003361 : stx-fault https://storyboard.openstack.org/#!/story/2003361 : stx-gplv2 https://storyboard.openstack.org/#!/story/2003363 : stx-gplv3 https://storyboard.openstack.org/#!/story/2003364 : stx-gui https://storyboard.openstack.org/#!/story/2003365 : stx-ha https://storyboard.openstack.org/#!/story/2003366 : stx-integ https://storyboard.openstack.org/#!/story/2003367 : stx-manifest https://storyboard.openstack.org/#!/story/2003368 : stx-metal https://storyboard.openstack.org/#!/story/2003369 : stx-nfv https://storyboard.openstack.org/#!/story/2003370 : stx-root https://storyboard.openstack.org/#!/story/2003371 : stx-update https://storyboard.openstack.org/#!/story/2003372 : stx-upstream https://storyboard.openstack.org/#!/story/2003373 : stx-utils Thanks -Erich
These repos are being deleted. https://storyboard.openstack.org/#!/story/2003361 : stx-gplv2 https://storyboard.openstack.org/#!/story/2003363 : stx-gplv3 https://storyboard.openstack.org/#!/story/2003373 : stx-utils Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran@intel.com] Sent: Wednesday, August 8, 2018 2:57 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Effort to make zuul linters happy Hi all, Currently the zuul check only verifies linters and some of them fails. The zuul gate stage is disabled to make the integration possible. As it is desirable to use Zuul for gating code merges we need first to solve the linter problems in every repository. I've created a set of stories for each repository to start this effort. Now the only tasks created there is to go into Zuul logs and review what needs to be done to solve the issues and create the related tasks. In case someone wants to join this effort, here is the list of stories. https://storyboard.openstack.org/#!/story/2003359 : stx-clients https://storyboard.openstack.org/#!/story/2003360 : stx-config https://storyboard.openstack.org/#!/story/2003361 : stx-fault https://storyboard.openstack.org/#!/story/2003361 : stx-gplv2 https://storyboard.openstack.org/#!/story/2003363 : stx-gplv3 https://storyboard.openstack.org/#!/story/2003364 : stx-gui https://storyboard.openstack.org/#!/story/2003365 : stx-ha https://storyboard.openstack.org/#!/story/2003366 : stx-integ https://storyboard.openstack.org/#!/story/2003367 : stx-manifest https://storyboard.openstack.org/#!/story/2003368 : stx-metal https://storyboard.openstack.org/#!/story/2003369 : stx-nfv https://storyboard.openstack.org/#!/story/2003370 : stx-root https://storyboard.openstack.org/#!/story/2003371 : stx-update https://storyboard.openstack.org/#!/story/2003372 : stx-upstream https://storyboard.openstack.org/#!/story/2003373 : stx-utils Thanks -Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
2003361 is a story for zuul linters in stx-fault, let's keep that one. It's shown twice in the list below. I've closed 2003363 and 2003373. The story for stx-gplv2 is 2003362, which I have also just closed. brucej -----Original Message----- From: Rowsell, Brent [mailto:Brent.Rowsell@windriver.com] Sent: Wednesday, August 8, 2018 12:03 PM To: Cordoba Malibran, Erich <erich.cordoba.malibran@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Effort to make zuul linters happy These repos are being deleted. https://storyboard.openstack.org/#!/story/2003361 : stx-gplv2 https://storyboard.openstack.org/#!/story/2003363 : stx-gplv3 https://storyboard.openstack.org/#!/story/2003373 : stx-utils Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran@intel.com] Sent: Wednesday, August 8, 2018 2:57 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Effort to make zuul linters happy Hi all, Currently the zuul check only verifies linters and some of them fails. The zuul gate stage is disabled to make the integration possible. As it is desirable to use Zuul for gating code merges we need first to solve the linter problems in every repository. I've created a set of stories for each repository to start this effort. Now the only tasks created there is to go into Zuul logs and review what needs to be done to solve the issues and create the related tasks. In case someone wants to join this effort, here is the list of stories. https://storyboard.openstack.org/#!/story/2003359 : stx-clients https://storyboard.openstack.org/#!/story/2003360 : stx-config https://storyboard.openstack.org/#!/story/2003361 : stx-fault https://storyboard.openstack.org/#!/story/2003361 : stx-gplv2 https://storyboard.openstack.org/#!/story/2003363 : stx-gplv3 https://storyboard.openstack.org/#!/story/2003364 : stx-gui https://storyboard.openstack.org/#!/story/2003365 : stx-ha https://storyboard.openstack.org/#!/story/2003366 : stx-integ https://storyboard.openstack.org/#!/story/2003367 : stx-manifest https://storyboard.openstack.org/#!/story/2003368 : stx-metal https://storyboard.openstack.org/#!/story/2003369 : stx-nfv https://storyboard.openstack.org/#!/story/2003370 : stx-root https://storyboard.openstack.org/#!/story/2003371 : stx-update https://storyboard.openstack.org/#!/story/2003372 : stx-upstream https://storyboard.openstack.org/#!/story/2003373 : stx-utils Thanks -Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
I've got an update to resolve bashate and pep8 warnings in stx-update, now out for review. This update also enables most of the pep8 errors that were being ignored, addressing the issues with those error types. I have left the zuul voting disabled for now, figuring that can be a separate update. https://review.openstack.org/#/c/590064/ -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Wednesday, August 08, 2018 6:38 PM To: Rowsell, Brent; Cordoba Malibran, Erich; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Effort to make zuul linters happy 2003361 is a story for zuul linters in stx-fault, let's keep that one. It's shown twice in the list below. I've closed 2003363 and 2003373. The story for stx-gplv2 is 2003362, which I have also just closed. brucej -----Original Message----- From: Rowsell, Brent [mailto:Brent.Rowsell@windriver.com] Sent: Wednesday, August 8, 2018 12:03 PM To: Cordoba Malibran, Erich <erich.cordoba.malibran@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Effort to make zuul linters happy These repos are being deleted. https://storyboard.openstack.org/#!/story/2003361 : stx-gplv2 https://storyboard.openstack.org/#!/story/2003363 : stx-gplv3 https://storyboard.openstack.org/#!/story/2003373 : stx-utils Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran@intel.com] Sent: Wednesday, August 8, 2018 2:57 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Effort to make zuul linters happy Hi all, Currently the zuul check only verifies linters and some of them fails. The zuul gate stage is disabled to make the integration possible. As it is desirable to use Zuul for gating code merges we need first to solve the linter problems in every repository. I've created a set of stories for each repository to start this effort. Now the only tasks created there is to go into Zuul logs and review what needs to be done to solve the issues and create the related tasks. In case someone wants to join this effort, here is the list of stories. https://storyboard.openstack.org/#!/story/2003359 : stx-clients https://storyboard.openstack.org/#!/story/2003360 : stx-config https://storyboard.openstack.org/#!/story/2003361 : stx-fault https://storyboard.openstack.org/#!/story/2003361 : stx-gplv2 https://storyboard.openstack.org/#!/story/2003363 : stx-gplv3 https://storyboard.openstack.org/#!/story/2003364 : stx-gui https://storyboard.openstack.org/#!/story/2003365 : stx-ha https://storyboard.openstack.org/#!/story/2003366 : stx-integ https://storyboard.openstack.org/#!/story/2003367 : stx-manifest https://storyboard.openstack.org/#!/story/2003368 : stx-metal https://storyboard.openstack.org/#!/story/2003369 : stx-nfv https://storyboard.openstack.org/#!/story/2003370 : stx-root https://storyboard.openstack.org/#!/story/2003371 : stx-update https://storyboard.openstack.org/#!/story/2003372 : stx-upstream https://storyboard.openstack.org/#!/story/2003373 : stx-utils Thanks -Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
I am interested in helping out with this effort. I have free cycles starting on Monday, please keep me in the loop. Lachlan -----Original Message----- From: Rowsell, Brent [mailto:Brent.Rowsell@windriver.com] Sent: August-08-18 3:03 PM To: Cordoba Malibran, Erich; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Effort to make zuul linters happy These repos are being deleted. https://storyboard.openstack.org/#!/story/2003361 : stx-gplv2 https://storyboard.openstack.org/#!/story/2003363 : stx-gplv3 https://storyboard.openstack.org/#!/story/2003373 : stx-utils Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran@intel.com] Sent: Wednesday, August 8, 2018 2:57 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Effort to make zuul linters happy Hi all, Currently the zuul check only verifies linters and some of them fails. The zuul gate stage is disabled to make the integration possible. As it is desirable to use Zuul for gating code merges we need first to solve the linter problems in every repository. I've created a set of stories for each repository to start this effort. Now the only tasks created there is to go into Zuul logs and review what needs to be done to solve the issues and create the related tasks. In case someone wants to join this effort, here is the list of stories. https://storyboard.openstack.org/#!/story/2003359 : stx-clients https://storyboard.openstack.org/#!/story/2003360 : stx-config https://storyboard.openstack.org/#!/story/2003361 : stx-fault https://storyboard.openstack.org/#!/story/2003361 : stx-gplv2 https://storyboard.openstack.org/#!/story/2003363 : stx-gplv3 https://storyboard.openstack.org/#!/story/2003364 : stx-gui https://storyboard.openstack.org/#!/story/2003365 : stx-ha https://storyboard.openstack.org/#!/story/2003366 : stx-integ https://storyboard.openstack.org/#!/story/2003367 : stx-manifest https://storyboard.openstack.org/#!/story/2003368 : stx-metal https://storyboard.openstack.org/#!/story/2003369 : stx-nfv https://storyboard.openstack.org/#!/story/2003370 : stx-root https://storyboard.openstack.org/#!/story/2003371 : stx-update https://storyboard.openstack.org/#!/story/2003372 : stx-upstream https://storyboard.openstack.org/#!/story/2003373 : stx-utils Thanks -Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi, I just checked the zuul script under stx-fault, and here's what I found: The linters job will do 2 checks: 1. check *.sh files under this project with bashate. But we don't have shell file in this project, so the find cmd will return nothing and the bashate will fail. 2. check *.yaml files with yamllint. But in the cmd, it will find yaml files with "-name middleware/io-monitor/recipes-common/io-monitor/io-monitor/io_monitor/test-tools/yaml/*" which is not a right folder under this project. So it will always fail. As most of the linters jobs in different projects are the same (copied as default), I guess we can fix them with one synced script. Yan -----Original Message----- From: Plant, Lachlan [mailto:Lachlan.Plant@windriver.com] Sent: Friday, August 10, 2018 02:09 To: Rowsell, Brent <Brent.Rowsell@windriver.com>; Cordoba Malibran, Erich <erich.cordoba.malibran@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Effort to make zuul linters happy I am interested in helping out with this effort. I have free cycles starting on Monday, please keep me in the loop. Lachlan -----Original Message----- From: Rowsell, Brent [mailto:Brent.Rowsell@windriver.com] Sent: August-08-18 3:03 PM To: Cordoba Malibran, Erich; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Effort to make zuul linters happy These repos are being deleted. https://storyboard.openstack.org/#!/story/2003361 : stx-gplv2 https://storyboard.openstack.org/#!/story/2003363 : stx-gplv3 https://storyboard.openstack.org/#!/story/2003373 : stx-utils Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran@intel.com] Sent: Wednesday, August 8, 2018 2:57 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Effort to make zuul linters happy Hi all, Currently the zuul check only verifies linters and some of them fails. The zuul gate stage is disabled to make the integration possible. As it is desirable to use Zuul for gating code merges we need first to solve the linter problems in every repository. I've created a set of stories for each repository to start this effort. Now the only tasks created there is to go into Zuul logs and review what needs to be done to solve the issues and create the related tasks. In case someone wants to join this effort, here is the list of stories. https://storyboard.openstack.org/#!/story/2003359 : stx-clients https://storyboard.openstack.org/#!/story/2003360 : stx-config https://storyboard.openstack.org/#!/story/2003361 : stx-fault https://storyboard.openstack.org/#!/story/2003361 : stx-gplv2 https://storyboard.openstack.org/#!/story/2003363 : stx-gplv3 https://storyboard.openstack.org/#!/story/2003364 : stx-gui https://storyboard.openstack.org/#!/story/2003365 : stx-ha https://storyboard.openstack.org/#!/story/2003366 : stx-integ https://storyboard.openstack.org/#!/story/2003367 : stx-manifest https://storyboard.openstack.org/#!/story/2003368 : stx-metal https://storyboard.openstack.org/#!/story/2003369 : stx-nfv https://storyboard.openstack.org/#!/story/2003370 : stx-root https://storyboard.openstack.org/#!/story/2003371 : stx-update https://storyboard.openstack.org/#!/story/2003372 : stx-upstream https://storyboard.openstack.org/#!/story/2003373 : stx-utils Thanks -Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
1. The xargs commands in the tox.ini files should be updated to include --no-run-if-empty 2. While the io-monitor path is no longer valid, it looks like it's an exclusion argument to the find commands, to skip any yaml files found under that directory. It doesn't cause the find command to fail. It should be removed from the tox.ini files, I agree, but it seems to have no effect. -----Original Message----- From: Chen, Yan [mailto:yan.chen@intel.com] Sent: Thursday, August 09, 2018 10:27 PM To: Plant, Lachlan; Rowsell, Brent; Cordoba Malibran, Erich; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Effort to make zuul linters happy Hi, I just checked the zuul script under stx-fault, and here's what I found: The linters job will do 2 checks: 1. check *.sh files under this project with bashate. But we don't have shell file in this project, so the find cmd will return nothing and the bashate will fail. 2. check *.yaml files with yamllint. But in the cmd, it will find yaml files with "-name middleware/io-monitor/recipes-common/io-monitor/io-monitor/io_monitor/test-tools/yaml/*" which is not a right folder under this project. So it will always fail. As most of the linters jobs in different projects are the same (copied as default), I guess we can fix them with one synced script. Yan -----Original Message----- From: Plant, Lachlan [mailto:Lachlan.Plant@windriver.com] Sent: Friday, August 10, 2018 02:09 To: Rowsell, Brent <Brent.Rowsell@windriver.com>; Cordoba Malibran, Erich <erich.cordoba.malibran@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Effort to make zuul linters happy I am interested in helping out with this effort. I have free cycles starting on Monday, please keep me in the loop. Lachlan -----Original Message----- From: Rowsell, Brent [mailto:Brent.Rowsell@windriver.com] Sent: August-08-18 3:03 PM To: Cordoba Malibran, Erich; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Effort to make zuul linters happy These repos are being deleted. https://storyboard.openstack.org/#!/story/2003361 : stx-gplv2 https://storyboard.openstack.org/#!/story/2003363 : stx-gplv3 https://storyboard.openstack.org/#!/story/2003373 : stx-utils Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran@intel.com] Sent: Wednesday, August 8, 2018 2:57 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Effort to make zuul linters happy Hi all, Currently the zuul check only verifies linters and some of them fails. The zuul gate stage is disabled to make the integration possible. As it is desirable to use Zuul for gating code merges we need first to solve the linter problems in every repository. I've created a set of stories for each repository to start this effort. Now the only tasks created there is to go into Zuul logs and review what needs to be done to solve the issues and create the related tasks. In case someone wants to join this effort, here is the list of stories. https://storyboard.openstack.org/#!/story/2003359 : stx-clients https://storyboard.openstack.org/#!/story/2003360 : stx-config https://storyboard.openstack.org/#!/story/2003361 : stx-fault https://storyboard.openstack.org/#!/story/2003361 : stx-gplv2 https://storyboard.openstack.org/#!/story/2003363 : stx-gplv3 https://storyboard.openstack.org/#!/story/2003364 : stx-gui https://storyboard.openstack.org/#!/story/2003365 : stx-ha https://storyboard.openstack.org/#!/story/2003366 : stx-integ https://storyboard.openstack.org/#!/story/2003367 : stx-manifest https://storyboard.openstack.org/#!/story/2003368 : stx-metal https://storyboard.openstack.org/#!/story/2003369 : stx-nfv https://storyboard.openstack.org/#!/story/2003370 : stx-root https://storyboard.openstack.org/#!/story/2003371 : stx-update https://storyboard.openstack.org/#!/story/2003372 : stx-upstream https://storyboard.openstack.org/#!/story/2003373 : stx-utils Thanks -Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On Thu, Aug 9, 2018 at 9:26 PM, Chen, Yan <yan.chen@intel.com> wrote:
1. check *.sh files under this project with bashate. But we don't have shell file in this project, so the find cmd will return nothing and the bashate will fail.
If there are no shell scripts then we can skip the bashate run.
2. check *.yaml files with yamllint. But in the cmd, it will find yaml files with "-name middleware/io-monitor/recipes-common/io-monitor/io-monitor/io_monitor/test-tools/yaml/*" which is not a right folder under this project. So it will always fail.
We should add an exception for paths like that to skip them. The yamllint check is useful to validate the Zuul config files.
As most of the linters jobs in different projects are the same (copied as default), I guess we can fix them with one synced script.
They started from the same template, yes, and should be adjusted to fit the requirements of the repo they are in. The majority of the shuffling of things around has settled down so this is a good time to start looking at these, we still do need to be mindful of the WRS backlog yet to me submitted, gratuitous formatting changes will cause those to need to be rebased, so this should be done with that in mind. The defined interface here is the tox environments, ie 'tox -e linters' should always run an appropriate set of lint jobs for that repo. These should always be usable both in the CI jobs and locally. dt -- Dean Troyer dtroyer@gmail.com
Leaving the bashate in place with xargs --no-run-if-empty would cover the case where someone introduces a shell script where none previously existed. Assuming people follow the convention of naming shell scripts with a .sh extension, at least. -----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Thursday, August 09, 2018 11:02 PM To: Chen, Yan Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Effort to make zuul linters happy On Thu, Aug 9, 2018 at 9:26 PM, Chen, Yan <yan.chen@intel.com> wrote:
1. check *.sh files under this project with bashate. But we don't have shell file in this project, so the find cmd will return nothing and the bashate will fail.
If there are no shell scripts then we can skip the bashate run.
2. check *.yaml files with yamllint. But in the cmd, it will find yaml files with "-name middleware/io-monitor/recipes-common/io-monitor/io-monitor/io_monitor/test-tools/yaml/*" which is not a right folder under this project. So it will always fail.
We should add an exception for paths like that to skip them. The yamllint check is useful to validate the Zuul config files.
As most of the linters jobs in different projects are the same (copied as default), I guess we can fix them with one synced script.
They started from the same template, yes, and should be adjusted to fit the requirements of the repo they are in. The majority of the shuffling of things around has settled down so this is a good time to start looking at these, we still do need to be mindful of the WRS backlog yet to me submitted, gratuitous formatting changes will cause those to need to be rebased, so this should be done with that in mind. The defined interface here is the tox environments, ie 'tox -e linters' should always run an appropriate set of lint jobs for that repo. These should always be usable both in the CI jobs and locally. dt -- Dean Troyer dtroyer@gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On Thu, Aug 9, 2018 at 10:18 PM, Penney, Don <Don.Penney@windriver.com> wrote:
Leaving the bashate in place with xargs --no-run-if-empty would cover the case where someone introduces a shell script where none previously existed. Assuming people follow the convention of naming shell scripts with a .sh extension, at least.
++, that is a better solution. In places that intentionally do not have shell scripts with a .sh ending we added explicit inclusions. DevStack is the pathological example of this...[0] dt [0] https://git.openstack.org/cgit/openstack-dev/devstack/tree/tox.ini#n10 -- Dean Troyer dtroyer@gmail.com
participants (7)
-
Chen, Yan
-
Cordoba Malibran, Erich
-
Dean Troyer
-
Jones, Bruce E
-
Penney, Don
-
Plant, Lachlan
-
Rowsell, Brent