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

Azure pipeline support for arm64 using qemu #519

Closed
wants to merge 1 commit into from

Conversation

odidev
Copy link

@odidev odidev commented Aug 18, 2020

Added azure pipeline support for arm64 using qemu.

Related to issue number #500

@@ -20,3 +20,4 @@ variables:
stages:
- template: stage-lint.yml
- template: stage-test.yml
- template: stage-aarch64.yml
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should probably go to deploy.yml

Copy link
Author

@odidev odidev Aug 26, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@webknjaz Sorry for the confusion. stage-aarch64.yml was for running pytest for aarch64, same as stage-test.yml is for x86, Mac and Windows.. I have removed the stage-aarch64.yml file and added the changes in stage-test.yml itself. I have also added build steps to deploy.yml.

@@ -0,0 +1,45 @@
stages:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Author

@odidev odidev Aug 26, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned above stage-aarch64.yml was for running pytest for aarch64, same as stage-test.yml is for x86, Mac and Windows.
Now I have removed the file and added in stage-test.yml file.

@@ -0,0 +1,70 @@
echo "exporting Mutlidict root directory"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Author

@odidev odidev Aug 26, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have removed the script and accumulated all the changes in stage-test.yml itself.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't change the need to have it in a shared repo rather than copy-pasted all around the place.

@asvetlov
Copy link
Member

I agree with @webknjaz

BTW, looks like composite actions (https://docs.github.com/en/actions/creating-actions/creating-a-composite-run-steps-action) can be used as a functional replacement for azure templates if we move to github workflows eventually.
This is not related to the issue though.

@webknjaz
Copy link
Member

Oh, nice, I haven't heard of the composite actions yet!

@asvetlov
Copy link
Member

asvetlov commented Aug 19, 2020

On my job I'm currently working with workflows a lot; recently learned about composite actions by accident.
I have no idea how long ago they were added.

@webknjaz
Copy link
Member

@odidev odidev force-pushed the odidev_multidict branch 3 times, most recently from 85ef572 to c88beca Compare August 26, 2020 14:59
Copy link
Member

@webknjaz webknjaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As per earlier comments, this should be implemented in the shared templates @ https://github.com/aio-libs/azure-pipelines and only referred from here.

@mattsplats
Copy link

@webknjaz Looks like odidev has followed up on your request: aio-libs/azure-pipelines#1

Tests are failing on this PR because the pipelines repo PR has not merged yet. Could you take a look at the pipeline change?

@asvetlov
Copy link
Member

Done by multidict 5.0.0 release

Thanks for the PR, I've borrowed many implementation details from it while building my own version

@asvetlov asvetlov closed this Oct 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants