Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

[ARM/CI] Add manual triggering CI for arm and armel #9853

Merged
merged 1 commit into from
Mar 14, 2017

Conversation

hqueue
Copy link
Member

@hqueue hqueue commented Feb 28, 2017

Add following manual triggering CI for arm and armel.
This will be used with a new arm32 CI script (#9445) which is already applied to CoreFx(dotnet/corefx#16378) and Core-Setup (dotnet/core-setup#1512).

  • Ubuntu arm Cross Release Build (Existing but not working for a year and never used recently.)
  • Ubuntu arm Cross Debug Build (Existing but not working for a year and never used recently.)
  • Ubuntu16.04 arm Cross Release Build
  • Ubuntu16.04 arm Cross Debug Build
  • Tizen armel Cross Release Build
  • Tizen armel Cross Debug Build

Currently there are two default CI for ARM cross using ARM emulator which will be disabled after enabling new arm32 CI.

  • Linux ARM Emulator Cross Release Build
  • Linux ARM Emulator Cross Debug Build

After merging this PR, new arm32 CI script in #9445 will be tested with new commands.

Related issues:
https://github.com/dotnet/core-setup/issues/790
https://github.com/dotnet/core-setup/issues/725

@hqueue
Copy link
Member Author

hqueue commented Feb 28, 2017

@dotnet-bot test ci please

@hqueue
Copy link
Member Author

hqueue commented Feb 28, 2017

@dotnet-bot test ci please

@hqueue hqueue force-pushed the arm/ci_legs branch 2 times, most recently from 0512a53 to 1bd2c8a Compare February 28, 2017 13:22
@hqueue
Copy link
Member Author

hqueue commented Feb 28, 2017

@dotnet-bot test ci please

@hqueue
Copy link
Member Author

hqueue commented Feb 28, 2017

@dotnet-bot test ci please

1 similar comment
@hqueue
Copy link
Member Author

hqueue commented Feb 28, 2017

@dotnet-bot test ci please

@hqueue
Copy link
Member Author

hqueue commented Feb 28, 2017

@dotnet-bot test ci please

@hqueue
Copy link
Member Author

hqueue commented Feb 28, 2017

@dotnet-bot test ci please

@hqueue
Copy link
Member Author

hqueue commented Feb 28, 2017

@dotnet-bot test ci please

@hqueue
Copy link
Member Author

hqueue commented Feb 28, 2017

@dotnet-bot test ci please

1 similar comment
@hqueue
Copy link
Member Author

hqueue commented Feb 28, 2017

@dotnet-bot test ci please

@hqueue
Copy link
Member Author

hqueue commented Feb 28, 2017

I've ran test ci please and result can be found at https://ci.dot.net/job/dotnet_coreclr/job/master/job/GenPRTest/job/generator_prtest/107/.

Among the generated jobs, I think following jobs are added or changed by this PR.

00:02:08.104     GeneratedJob{name='arm_cross_checked_ubuntu'}
00:02:08.104     GeneratedJob{name='arm_cross_checked_ubuntu16.04'}
00:02:08.104     GeneratedJob{name='arm_cross_checked_ubuntu16.04_prtest'}
00:02:08.104     GeneratedJob{name='arm_cross_checked_ubuntu_prtest'}
00:02:08.104     GeneratedJob{name='arm_cross_debug_ubuntu'}
00:02:08.104     GeneratedJob{name='arm_cross_debug_ubuntu16.04'}
00:02:08.104     GeneratedJob{name='arm_cross_debug_ubuntu16.04_prtest'}
00:02:08.104     GeneratedJob{name='arm_cross_debug_ubuntu_prtest'}
00:02:08.104     GeneratedJob{name='arm_cross_release_ubuntu'}
00:02:08.104     GeneratedJob{name='arm_cross_release_ubuntu16.04'}
00:02:08.104     GeneratedJob{name='arm_cross_release_ubuntu16.04_prtest'}
00:02:08.104     GeneratedJob{name='arm_cross_release_ubuntu_prtest'}
00:02:08.104     GeneratedJob{name='armel_cross_checked_tizen'}
00:02:08.104     GeneratedJob{name='armel_cross_checked_tizen_prtest'}
00:02:08.104     GeneratedJob{name='armel_cross_debug_tizen'}
00:02:08.104     GeneratedJob{name='armel_cross_debug_tizen_prtest'}
00:02:08.104     GeneratedJob{name='armel_cross_release_tizen'}
00:02:08.104     GeneratedJob{name='armel_cross_release_tizen_prtest'}

@gkhanna79 I'm looking for someone who can review and test this changes to prevent a accidental change which might cause break existing CI. Can you invite someone who can look into this?

@hqueue hqueue changed the title [ARM/CI][WIP] Add manual triggering CI for arm and armel [ARM/CI] Add manual triggering CI for arm and armel Feb 28, 2017
@gkhanna79
Copy link
Member

@mmitche Can you PTAL?

Copy link
Member

@mmitche mmitche left a comment

Choose a reason for hiding this comment

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

Looks good except for the couple questions

Utilities.getFolderName(branch)

// Copy the Windows test binaries and the Corefx build binaries
copyArtifacts(WindowTestsName) {
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 look quite right. Is this trying to copy corefx binaries from latest?

Copy link
Member Author

@hqueue hqueue Mar 1, 2017

Choose a reason for hiding this comment

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

I'm trying to copy (1) test binary and (2) corefx binary from the latest to prepare coreclr test.

Because I don't know well about relation between coreclr CI and corefx CI, I just followed a way of current CI for arm and other architectures.
https://github.com/dotnet/coreclr/blob/master/netci.groovy#L2505-L2516 (for arm)
https://github.com/dotnet/coreclr/blob/master/netci.groovy#L2884-L2900 (for other)

If this is not a right way, please let me know how to fetch correct banries of corefx and test to prepare testing.

Copy link
Member Author

Choose a reason for hiding this comment

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

If comments is misleading I will update the comments.

Copy link
Member

Choose a reason for hiding this comment

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

Okay I think that's right

netci.groovy Outdated
arm_abi='armel'
corefx_os='tizen'
}
copyArtifacts("${corefxFolder}/${corefx_os}_${arm_abi}_cross_${lowerConfiguration}") {
Copy link
Member

Choose a reason for hiding this comment

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

Or is this the intended corefx copy.

Copy link
Member Author

Choose a reason for hiding this comment

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

Addressed above :)

Copy link
Member

Choose a reason for hiding this comment

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

I think you have it all correct except there is no checked configuration of corefx (only debug and reease). So you might want to copy from the release version in the checked and release coreclr cases, and from the debug version in the debug coreclr case

Copy link
Member Author

Choose a reason for hiding this comment

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

Oops, I almost missed it.
Thank you for the feedback and I've updated this as you suggested :)

@gkhanna79
Copy link
Member

Is this ready for merge?

@hqueue
Copy link
Member Author

hqueue commented Mar 3, 2017

I'm ready and waiing for @mmitche, since he has some questions which I've answered.

@mmitche
Copy link
Member

mmitche commented Mar 3, 2017

@dotnet-bot test ci please (one final check, but otherwise looks good)

@hqueue
Copy link
Member Author

hqueue commented Mar 6, 2017

@dotnet-bot test ci please

@hqueue
Copy link
Member Author

hqueue commented Mar 6, 2017

@dotnet-bot test ci please

Add follwoing manual triggering CI for arm and armel.
This will be used by new arm32 CI script which is already applied to Core-Setup and CoreFX.

  Ubuntu arm Cross Release Build
  Ubuntu arm Cross Debug Build
  Ubuntu16.04 arm Cross Release Build
  Ubuntu16.04 arm Cross Debug Build
  Tizen arm Cross Release Build
  Tizen arm Cross Debug Build

Currently there are two default CI for ARM cross using ARM emulator
which will be disabled after enabling new arm32 CI.
  Linux ARM Emulator Cross Release Build
  Linux ARM Emulator Cross Debug Build

Signed-off-by: Hyung-Kyu Choi <hk0110.choi@samsung.com>
@hqueue
Copy link
Member Author

hqueue commented Mar 6, 2017

@dotnet-bot test ci please

@hqueue
Copy link
Member Author

hqueue commented Mar 6, 2017

@mmitche I've update the PR by applying your feedback and I think it's ready for merge.

@hqueue
Copy link
Member Author

hqueue commented Mar 9, 2017

@gkhanna79 @mmitche Can you please take a look again ? It's ready for merge and I can test new arm CI #9445 after this PR is merged. Thanks.

@hqueue
Copy link
Member Author

hqueue commented Mar 13, 2017

@gkhanna79 @mmitche I don't want to be impatient, but I'm curious when this will be merged.

@gkhanna79 gkhanna79 merged commit 50cae4e into dotnet:master Mar 14, 2017
@karelz karelz modified the milestone: 2.0.0 Aug 28, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants