Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Step duplicates the build #10

Closed
benrnz-sv opened this issue Nov 10, 2016 · 6 comments
Closed

Step duplicates the build #10

benrnz-sv opened this issue Nov 10, 2016 · 6 comments
Assignees

Comments

@benrnz-sv
Copy link

Hi guys,
I've noticed that the NUnit-Runner step is always rebuilding the code inside the step. This causes all my code to effectively build twice. I'd prefer to run the unit tests against already built nunit projects output by the Builder step.

Is it possible to make this step more compose-able with other steps such that, you are required to have a Builder step beforehand for it to work? For example the publish to Hockey step does not build the code inside its step, it requires the artefacts to already be built.

This would also reduce the maintenance work on this step to keep it in sync with changes to the Builder step.

Or at least can there be an option to build again if others are requiring this.

Thanks guys

@viktorbenei
Copy link

@godrei please review

@godrei
Copy link
Contributor

godrei commented Dec 6, 2016

Hi @benrnz-sv ,
the problem is, that for creating release version and for running tests most of the times you need to build the project with different configuration-platform combinations, thats why every xamarin steps are building the project.

For example: nunit-runner step needs an iPhoneSimulator build, but test-cloud needs iPhone build for releasing you probably need Release configuration, instead of debug.

@benrnz-sv
Copy link
Author

Thanks for the response.
I understand the need for specific builds for specific purposes, but let me give you an example of why this would be useful for me.
I have a separate build to run nightly UI Test automation in Xamarin Test Cloud. This build first builds the solution using the Archive step, then runs all the unit tests. The build configuration is actually iPhoneSimulator to be compatible with what TestCloud needs. So, if I use the NUnit step this adds another minute to my build time. Instead what I'm doing is using a Script step to manually run nunit so it doesn't do this. This is a little messy because it increases the amount of maintenance I need to do to maintain the script step and variables as compared to using the NUnit step.

Can it be an option you select if the build configuration is compatible?

@godrei
Copy link
Contributor

godrei commented Jan 5, 2017

Hi @benrnz-sv ,
sorry for my late response.
I understand your issue and agree that allowing to opt-out the build process would be usefully in xamarin test steps.

Could you please create a feature request on discuss.bitrise.io, for better visibility?

@godrei
Copy link
Contributor

godrei commented Mar 6, 2017

Closing as we did not receive a reply - @benrnz-sv please let us know if we can help with anything and we'll reopen this issue!

@godrei godrei closed this as completed Mar 6, 2017
@benrnz-sv
Copy link
Author

Apologies,I didn't see the notification of this until now. Will do, I'll create a feature request.
Thanks.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants