[GHC] #13121: Investigate whether uploading build artifacts from harbormaster would be usful
GHC
ghc-devs at haskell.org
Sat Jan 14 18:00:04 UTC 2017
#13121: Investigate whether uploading build artifacts from harbormaster would be
usful
-------------------------------------+-------------------------------------
Reporter: mpickering | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Compiler | Version:
Keywords: newcomer | Operating System: Unknown/Multiple
Architecture: | Type of failure: None/Unknown
Unknown/Multiple |
Test Case: | Blocked By:
Blocking: | Related Tickets:
Differential Rev(s): | Wiki Page:
-------------------------------------+-------------------------------------
In harbormaster it is possible to upload build artifacts and associate
them with each build, for example we could upload the user manual for each
build or even binaries. I am not sure what would be useful. One use case
might be checking the rendering of the user guide when it is modified.
The idea is to write a small utility program which uploads suitable
artifacts and then add an extra build step
to the relevant build plans which calls this program. The utility doesn't
have to be in-tree as it can be installed in the environment.
Some more information:
* There are some bindings to the phabricator API in [https://github.com
/haskell-infra/arc-lite arc-lite]
* The relevant API methods are `file.allocate`, `file.upload` and
`harbormaster.createartifact`
* `file.allocate` allows you to specify a time to delete a file, this
would be good to avoid consuming lots
of storage for builds.
* Artifacts appear in the "artifacts" tab
[https://phabricator.haskell.org/harbormaster/build/18367/ here]
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/13121>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list