LBRYCommunity/lbry-docker
1
0
Fork 0
Code Issues 2 Pull requests 2 Projects Releases 1 Packages Wiki Activity

lbrynet-multiarch-compiler steps require TRAVIS_COMMIT env var. #73

Merged
EnigmaCurry merged 1 commit from lbrynet-refactor into master 2019-06-04 14:48:53 +02:00
Conversation 0 Commits 1 Files changed 1 +2 -1
EnigmaCurry commented 2019-05-30 22:19:37 +02:00 (Migrated from github.com)
Copy link

Introduced in lbrynet commit #925e39c5a, the compile steps require setting TRAVIS_COMMIT environment variable.

Introduced in [lbrynet commit #925e39c5a](https://github.com/lbryio/lbry/commit/925e39c5a80952f7e7a3018b17327824af0f4395#diff-617ad45cf870bcc9e06d8c2938f8666d), the compile steps require setting TRAVIS_COMMIT environment variable.
Leopere (Migrated from github.com) approved these changes 2019-06-04 14:46:06 +02:00
Leopere (Migrated from github.com) left a comment
Copy link

The only concern I have is I'm aiming for this stuff to not depend on external build processors like Travis but it's fine this is pretty use case specific and something more generic can be dreamt up later.

The only concern I have is I'm aiming for this stuff to not depend on external build processors like Travis but it's fine this is pretty use case specific and something more generic can be dreamt up later.
Sign in to join this conversation.
Reviewers
No reviewers
Leopere
Labels
Clear labels   
Accepted

Just for marking accepted PR's

  
area: devops

   
area: discovery

   
area: docs

   
area: livestream

   
area: proposal

Work is part of a proposal

  
consider soon

Discuss this issue at the next planning meeting, then remove this label

  
Epic

   
good first issue

Good for newcomers

  
hacktoberfest

Welcome to Hacktoberfest

  
help wanted

Extra attention is needed

  
icebox

Long-term storage

  
In Review

Pull Requests that are currently in review and potentially waiting tweaks or feedback for clarity.

  
level: 1

No knowledge of the existing code required

  
level: 2

Some knowledge of the existing code is recommended

  
level: 3

Significant knowledge of the existing code is recommended

  
level: 4

Intimate knowledge of the existing code is recommended

  
needs: exploration

Solution unclear, needs research

  
needs: grooming

Issue needs to be groomed before work can start

  
needs: priority

Priority level needs to be defined

  
needs: repro

Issue needs step-by-step instructions on how to reproduce in latest code

  
needs: tech design

Needs technical design signoff before implementation can begin

  
on hold

Temporarily paused

  
priority: blocker

Issue is blocking release, do ASAP

  
priority: high

Work needs to be moved into sprint ASAP

  
priority: low

Work should be done but can stay in the backlog for now

  
priority: medium

Work needs to be done within 2-3 sprints

  
resilience

   
Tom's Wishlist

   
type: bug

Existing functionality is wrong or broken

  
type: discussion

A conversation. No specific changes requested

  
type: improvement

Existing (or partially existing) functionality needs to be changed

  
type: new feature

New functionality that does not exist yet

  
type: refactor

Minimal user-visible changes, but significant internal work

  
type: task

Either work that's not related to the code, or a small chore that does not fit into other categories

  
type: testing

Solution needs additional user testing

  
unplanned

Work that was not planned into the spirnt, took priority over planned work

No labels
Accepted
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
help wanted
icebox
In Review
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-docker#73
No description provided.
Delete branch "lbrynet-refactor"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?