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.

Sign up for GitHub

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

Jump to bottom

Maintainers can rely on a CI system to enforce build and test checks for PRs for Windows #51

Closed
4 tasks done
CodeMonkeyLeet opened this issue Nov 22, 2017 · 1 comment
Closed
4 tasks done

Maintainers can rely on a CI system to enforce build and test checks for PRs for Windows #51

CodeMonkeyLeet opened this issue Nov 22, 2017 · 1 comment
Assignees
@johnkord
Labels
ci/cd Issue is related to the code integration/deployment pipeline engineering Issue is related to tools and processes necessary for maintaining the Open Enclave repo story Issue describes a user scenario to be enabled. Unit of prioritization for project planning. windows Issue has to do with supporting Open Enclave on Windows
Projects
v0.5x Windows Support
Milestone
v0.5

Comments

@CodeMonkeyLeet
Copy link
Contributor

CodeMonkeyLeet commented Nov 22, 2017 •
edited

We need to onboard a Windows as a default CI configuration in Jenkins to catch build regressions, and specifically regressions in the ELF enclaves on Windows scenario:

The previous investigation on this has been closed in favor of converging on the same CI Jenkins infrastructure as used for the Linux configurations:

Need to set up a continuous integration pipelines for Windows, which requires extra investigation as the existing solution for Linux (#50) does not converge for Windows.

AppVeyor is one solution that other Azure teams have used and provide CI that is publicly visible to OSS contributors as well.

If we can get a single solution, this can be merged with the Linux one #50.
@CodeMonkeyLeet CodeMonkeyLeet mentioned this issue Nov 22, 2017
Closed
@CodeMonkeyLeet CodeMonkeyLeet added the story Issue describes a user scenario to be enabled. Unit of prioritization for project planning. label Nov 30, 2017
@CodeMonkeyLeet CodeMonkeyLeet added this to Backlog in Public preview via automation Nov 30, 2017
@CodeMonkeyLeet CodeMonkeyLeet added this to the 2018.01 milestone Nov 30, 2017
@CodeMonkeyLeet CodeMonkeyLeet modified the milestones: 2018.01, 2018.05 Jan 6, 2018
@CodeMonkeyLeet
Copy link
Contributor Author

Deferring Windows work items as target of opportunity.

@CodeMonkeyLeet CodeMonkeyLeet added engineering Issue is related to tools and processes necessary for maintaining the Open Enclave repo investigation Project tag indicating an issue requiring investigation for triage labels Jun 27, 2018
@CodeMonkeyLeet CodeMonkeyLeet changed the title Establish a CI workflow for OpenEnclave on Windows Maintainers can rely on a CI system to enforce build and test checks for PRs for Windows Jun 27, 2018
@CodeMonkeyLeet CodeMonkeyLeet added the windows Issue has to do with supporting Open Enclave on Windows label Nov 6, 2018
@CodeMonkeyLeet CodeMonkeyLeet removed this from the Future.Windows milestone Nov 6, 2018
@CodeMonkeyLeet CodeMonkeyLeet removed this from Backlog in Public preview Nov 6, 2018
@CodeMonkeyLeet CodeMonkeyLeet added ci/cd Issue is related to the code integration/deployment pipeline and removed investigation Project tag indicating an issue requiring investigation for triage labels Nov 6, 2018
@CodeMonkeyLeet CodeMonkeyLeet added this to To do in v0.5x via automation Nov 6, 2018
@CodeMonkeyLeet CodeMonkeyLeet added this to the 2018.11 milestone Nov 6, 2018
@CodeMonkeyLeet CodeMonkeyLeet moved this from To do to Prioritized Stories in v0.5x Nov 7, 2018
Britel pushed a commit that referenced this issue Nov 19, 2018
@dthaler
Update sockets APIs to match API doc (#51)
5793fcc 
* Update sockets.h to match API doc
* Remove buffer copies from send/recv paths
* Move socket APIs into separate static libs

Doc had OE_NETWORK_INSECURE in one place and OE_NETWORK_UNTRUSTED in
others.  Changed everywhere to the latter for now.

Signed-off-by: Dave Thaler <dthaler@microsoft.com>
@CodeMonkeyLeet CodeMonkeyLeet modified the milestones: 2018.11, 2019.01 Dec 5, 2018
@anitagov anitagov moved this from Prioritized Stories to In progress in v0.5x Mar 6, 2019
@lilyfang lilyfang modified the milestones: 2019.01, 2019.03 Mar 19, 2019
@andyleejordan andyleejordan modified the milestones: 2019.03, v0.5 Mar 20, 2019
@CodeMonkeyLeet CodeMonkeyLeet added this to In Progress in Windows Support Mar 21, 2019
@CodeMonkeyLeet CodeMonkeyLeet moved this from In Progress to To do in Windows Support Mar 21, 2019
@CodeMonkeyLeet CodeMonkeyLeet moved this from Backlog to Priority Queue in Windows Support Mar 21, 2019
Windows Support automation moved this from Priority Queue to Done Mar 21, 2019
@maxbeyond maxbeyond mentioned this issue Jun 27, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@johnkord johnkord

Labels
ci/cd Issue is related to the code integration/deployment pipeline engineering Issue is related to tools and processes necessary for maintaining the Open Enclave repo story Issue describes a user scenario to be enabled. Unit of prioritization for project planning. windows Issue has to do with supporting Open Enclave on Windows
Projects
No open projects
Windows Support
  
Done
v0.5x
  
In progress
Milestone
v0.5
Development

No branches or pull requests
4 participants
@andyleejordan @lilyfang @johnkord @CodeMonkeyLeet