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

Feature: work from branches other than master. #115

Closed
graphicore opened this issue Aug 26, 2019 · 4 comments
Closed

Feature: work from branches other than master. #115

graphicore opened this issue Aug 26, 2019 · 4 comments
Assignees

Comments

@graphicore
Copy link
Contributor

In a designers workflow, they need to check from their working branch and also in a sandboxed environment before going to the (unsandboxed) version with release branch. We can't use branches right now from our spreadsheet info.

see #114

full report

Step # 0 Review the Request and Generate the Files Package

finished: FAILED

Failing with reason: Abandoned because we can't work from custom branches right now.

Task ApproveProcess FAILED

Manifest Server CSVSpreadsheet/upstream can't create files package.

Report…

ERROR Error: unexpected HTTP status code: 404

@graphicore graphicore changed the title [Font Bakery Dashboard] fail to register family: Solway Feature: work from branches other than master. Aug 26, 2019
@graphicore
Copy link
Contributor Author

One use case for this is to enable #117 — a sandboxed workflow.

Another use case, that we need to discuss (if it isn't documented already): currently it's not possible to specify another branch than master in our spreadsheet database via manifestSources/CSVSpreadsheet. I'm not sure if we require our production upstream repos to have the fonts put into their master branch, but some projects may not want to put binaries into their repositories, so a way could be to have e.g. a google-fonts branch where the binaries for GF would be put in and use that as an upstream for releases targeted at google fonts.

NEXT research: is using master required for our upstream contributions? If yes, where (are the docs/instructions) and why.

@graphicore graphicore self-assigned this Aug 27, 2019
@graphicore
Copy link
Contributor Author

There's now a "branch" row in the spreadsheet that will be used if set. However, to be complete the interface should allow (at least for sandboxed mode) to request a specific branch and also display the branch requested and used in certain user interfaces e.g.:

Screenshot from 2019-08-27 21-13-37

E.g.: the sourceDetails log shows a _branch which is fine right now but the table below doesn't. That info in the table is what the user can request and all those situations where that data is shown or an interface asks for it should be updated to also include branch.

@graphicore
Copy link
Contributor Author

@vv-monsalve see this process I just initiated: https://fontbakery.graphicore.de/dispatcher/process/f139fe33-e6ea-418f-a28a-4665884d4580

It now uses the branch "QA-Solway" feel free to play with the dispatcher (which is sandboxed now) while I keep working on this and #117

@vv-monsalve
Copy link

vv-monsalve commented Aug 27, 2019 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants