Bitrise-init tool / the bitrise scanner issues and updates

Changelog
1

Started working on adding Carthage configuration auto detection support to bitrise-init / the bitrise config scanner tool.

2

Carthage support PR: https://github.com/bitrise-core/bitrise-init/pull/68

3

We decided to add Podfile fix to the new version of bitrise-init.

The scanner sometimes fails with:

[15:42:39] e[34;1mSearching for Podfilese[0m
[15:42:39] 1 Podfiles detected
[15:42:39] - LocallySelected/Podfile
[15:42:49] e[31;1mAnalyzer failed, error: No Podfile exists at path `LocallySelected/Podfile`.e[0m

No Podfile exists at path comes from cocoapods-core gem’s Podfile.from_file() function, see: https://coveralls.io/jobs/318882/source_files/33543988#L213

As a fix, i expanded the Podfile path, used by this ruby scripts and improved the error logging, PR: https://github.com/bitrise-core/bitrise-init/pull/70

4

Another Podfile related issue:

[09:10:13] e[34;1mSearching for Podfilese[0m
[09:10:13] 1 Podfiles detected
[09:10:13] - Podfile
[09:10:24] e[31;1mAnalyzer failed, error: Pod::DSLErrore[0m

This seems to be an issue in the Podfile or in Pod’s spec, based on this threads:

5

bitrise-init will print the files in the search dir if no platform detected.

tree . -L 3

Related PR: https://github.com/bitrise-core/bitrise-init/pull/71

1 Like
6

bitrise-init 1.1.0 released, started updating the project-scanner step.

1 Like
7

project-scanner 1.1.0 is shared in the steplib.