Stealing your CI setup #3415
Unanswered
maximkrouk
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there 😅
I was experimenting with extracting CI logic into a https://github.com/capturecontext/swift-package-action. And I'm facing some issues using it in my package repo CaptureContext/swift-interception#2, since I took core implementation from this repo I can't really think of a better place to ask about the issues I have 😄
The problem now is that xcodebuild doesn't see provided build destinations even if it's output with
-showdestinations
contains the one I'm passing toxcodebuild test
😓Maybe you faced and fixed it with some excluded Xcodes/Platforms in your workflow or smth, would be cool if you could take a look or maybe even consider creating your own action like this 😎
I'm still thinking about the API, but the general idea behind such extraction is to have a shared set of tools to increase the ergonomics of running tests. Currently you also have a lot of packages with different makefiles and when some approaches evolve you'll have to update everything manually (as well as I would have to do now, but I decided to extract it first c:)
I add
swift-package-action
package as git submodule to every package to easily modify it as needed from any package + to use the same set of tools from a local makefile. The action itself simply bypasses args to action-localmake
with predefined make goals likexcodebuild
orxcodebuild-macros
.Beta Was this translation helpful? Give feedback.
All reactions