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

Provide trusted Build Services for macOS and Linux #958

Closed
6 of 13 tasks
ryanRfox opened this issue May 24, 2018 · 7 comments
Closed
6 of 13 tasks

Provide trusted Build Services for macOS and Linux #958

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 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
3.3.0 - Feature R...

Comments

@ryanRfox
Copy link
Contributor

ryanRfox commented May 24, 2018 •
edited
Loading

User Story
As a BitShares User having macOS or Linux as my OS, I want trusted binaries so that I may deploy the BitShares software without building from source.

Targeted platforms in this Issue:

  • macOS Build Services (Travis-CI)
  • Linux Build services (Travis-CI)

Related Issue:

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 and Travis-CI for automated builds of their software releases. This Issue intends to build upon their successes.
  • Other automated build services exist and are to be considered as well. A transparent build process is a key requirement.

CORE TEAM TASK LIST

  • Evaluate / Prioritize Feature Request
  • Refine User Stories / Requirements
  • Define Test Cases
    • functioning demo within personal repo
    • Script for Core Team to GitHub and/or Travis-CI settings
  • 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 6 Build Impact flag identifying the build process 6 Deployment Impact flag identifying the deployment process (e.g. Docker, Travis, etc.) labels May 24, 2018
@ryanRfox ryanRfox mentioned this issue May 24, 2018
Open
29 tasks
@marcialvieira
Copy link
Contributor

marcialvieira commented May 29, 2018 •
edited
Loading

Hi @ryanRfox and everyone, I would like to perform the integration for the automated build, is it a continuation of the #742? If I'm right the next step is the AppVeyor of #964, then this one, right? I estimate it should not take more than 10 hours, what do you think?

@ryanRfox ryanRfox added the 6 UX Impact flag identifying the User Interface (UX) label Sep 4, 2018
@ryanRfox
Copy link
Contributor Author

ryanRfox commented Sep 4, 2018 •
edited
Loading

Assigned @marcialvieira and working to build a task list and estimations.

Note: this Issues has been modified to cover only Travis-CI builds for macOS and Linux. #964 will cover only Windows on AppVeyor. These Issues do not have dependencies.

@ryanRfox ryanRfox changed the title Provide Automated Build Services to Deliver Binaries for Target Platforms Provide Automated Build Services to Deliver Binaries for Linux and OSX Sep 4, 2018
@ryanRfox ryanRfox changed the title Provide Automated Build Services to Deliver Binaries for Linux and OSX Provide Automated Build Services to Deliver Binaries for Various Platforms Sep 4, 2018
@ryanRfox ryanRfox changed the title Provide Automated Build Services to Deliver Binaries for Various Platforms Provide Automated Build Services for macOS and Linux Sep 4, 2018
@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.

@abitmore
Copy link
Member

abitmore commented Sep 4, 2018

Just a note, please keep in mind that we value security much more than convenience.

@pmconrad
Copy link
Contributor

pmconrad commented Sep 5, 2018

Wrt trusted, builds should be reproducible. I. e. provide an automated build that can be run by anyone, and that will always produce a bitwise identical result.
https://reproducible-builds.org/

@marcialvieira marcialvieira mentioned this issue Nov 2, 2018
Closed
8 tasks
@pmconrad
Copy link
Contributor

Related: #897

@pmconrad
Copy link
Contributor

Closing, resolved through https://github.com/bitshares/bitshares-gitian .

Note that the issue title mentions "automated" while OP is about "trusted" binaries.

@abitmore abitmore added this to the 3.3.0 - Feature Release milestone Sep 18, 2019
@abitmore abitmore changed the title Provide Automated Build Services for macOS and Linux Provide trusted Build Services for macOS and Linux Jun 17, 2020
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 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
3.3.0 - Feature Release
Development

No branches or pull requests
4 participants
@pmconrad @abitmore @ryanRfox @marcialvieira