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

AppVeyor Automated Build Services for Windows Binaries #964

Open
6 of 29 tasks
ryanRfox opened this issue May 24, 2018 · 7 comments
Open
6 of 29 tasks

AppVeyor Automated Build Services for Windows Binaries #964

ryanRfox opened this issue May 24, 2018 · 7 comments
Labels
1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2b Gathering Requirements Status indicating currently refining User Stories and defining Requirements 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 5a Docs Needed Status specific to Documentation indicating the need for proper documentation to be added 6 Build Impact flag identifying the build process 6 Deployment Impact flag identifying the deployment process (e.g. Docker, Travis, etc.) 6 UX Impact flag identifying the User Interface (UX)
Milestone
Future Feature Re...

Comments

@ryanRfox
Copy link
Contributor

ryanRfox commented May 24, 2018 •
edited
Loading

User Story
As a Windows User I want trusted binaries so that I may deploy the BitShares software without building from source.

Related Tasks:

Task List

  • Define Test Cases
    • functioning demo within personal repo
    • Script for Core Team to GitHub and/or Travis-CI settings
  • Connect AppVayor to GitHub for the bitshares-core repo
  • Build Configuration (https://www.appveyor.com/docs/build-configuration/)
    • Build pipeline
    • Configuring build
    • Build versioning
    • AssemblyInfo patching
    • NET Core .csproj files patching
    • Clone directory
    • Environment variables
    • Script blocks in build configuration
    • Installing additional software
    • Hosts entries
    • Build matrix
    • Rolling builds
    • Scheduled builds
    • Build Queue
    • Testing
    • Pull Request

Additional Context (optional)

  • Currently the BitShares-Core Team provide binaries with each tagged release for both Windows and Linux. However, they could be produced in a more transparent way.
  • The BitShares-UI Team uses AppVeyor for Windows binaries with each releases. This Issue intends to build upon their successes.
  • AppVeyor (https://www.appveyor.com/)
    • Build Environments (https://www.appveyor.com/docs/build-environment/):
      • Visual Studio 2013
        • Boost: 1.56, 1.58
        • OpenSSL: OpenSSL 1.0.2L
      • Visual Studio 2015
        • Boost: 1.60, 1.62, 1.63, 1.65, 1.66, 1.67
        • OpenSSL: OpenSSL 1.0.2L
      • Visual Studio 2017
        • Boost: 1.65, 1.66, 1.67
        • OpenSSL: OpenSSL 1.0.2L

CORE TEAM TASK LIST

  • Evaluate / Prioritize Feature Request
  • Refine User Stories / Requirements
  • Define Test Cases
  • Design / Develop Solution
  • Perform QA/Testing
  • Update Documentation
@ryanRfox ryanRfox added 1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2b Gathering Requirements Status indicating currently refining User Stories and defining Requirements 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 5a Docs Needed Status specific to Documentation indicating the need for proper documentation to be added 6 Build Impact flag identifying the build process 6 Deployment Impact flag identifying the deployment process (e.g. Docker, Travis, etc.) 6 UX Impact flag identifying the User Interface (UX) labels May 24, 2018
@marcialvieira marcialvieira mentioned this issue May 29, 2018
Closed
13 tasks
@ShineQi ShineQi mentioned this issue Aug 29, 2018
Closed
@ryanRfox
Copy link
Contributor Author

ryanRfox commented Sep 4, 2018 •
edited
Loading

Assigned @cogutvalera for estimated 10 hours.
I goofed. Incorrect assignment of the Issue number. This Issue is open to be claimed.

@ryanRfox
Copy link
Contributor Author

ryanRfox commented Sep 4, 2018

Please see this note in #1304 about static linking, as it may provide insights for your solution.

@marcialvieira
Copy link
Contributor

marcialvieira commented Sep 4, 2018 •
edited
Loading

Hi @ryanRfox and everyone, I'm interested in working on this issue as a continuation of #958

@ryanRfox
Copy link
Contributor Author

ryanRfox commented Sep 4, 2018

Great! I've assigned @marcialvieira with 10 hours estimate. Thank you for taking care of all of our build platforms binaries.

@cogutvalera
Copy link
Member

@marcialvieira welcome ! This will be cool when will be done !

@ShineQi ShineQi mentioned this issue Apr 27, 2019
Open
@pmconrad
Copy link
Contributor

pmconrad commented May 5, 2019

1st shot for fc: bitshares/bitshares-fc#128

@abitmore abitmore added this to the Future Feature Release milestone Jun 17, 2020
@abitmore
Copy link
Member

I think https://github.com/bitshares/bitshares-gitian can do the job already. Perhaps close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2b Gathering Requirements Status indicating currently refining User Stories and defining Requirements 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 5a Docs Needed Status specific to Documentation indicating the need for proper documentation to be added 6 Build Impact flag identifying the build process 6 Deployment Impact flag identifying the deployment process (e.g. Docker, Travis, etc.) 6 UX Impact flag identifying the User Interface (UX)
Projects
None yet
Milestone
Future Feature Release
Development

No branches or pull requests
5 participants
@pmconrad @abitmore @ryanRfox @marcialvieira @cogutvalera