- 14 Jan, 2016 40 commits
-
-
Grzegorz Bizon authored
[ci skip]
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
Artifacts metadata field will be used to store a filename of gzipped file containing metadata definition for given artifacts archive.
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
This is needed because of backward compatibility. Previously artifacts archive had `.tar.gz` format, but artifacts browser requires ZIP format now.
-
Grzegorz Bizon authored
`artifacts?` method checks if artifacts archive is available.
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
This support is not completed though, as parent directory that is first in collection returned by `directories!` is not iterable yet.
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
This implementation makes it possible to browse artifacts, it depends on artifacts metadata.
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
`StringPath` class is something similar to Ruby's `Pathname` class, but does not involve any IO operations. `StringPath` objects require passing string representation of path, and array of paths that represents universe to constructor to be intantiated.
-
Grzegorz Bizon authored
This reverts nesting artifacts controller in builds module.
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
This will contain serialized array of files inside artifacts tarball.
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Douwe Maan authored
Improve the consistency of commit titles, branch names, tag names, issue/MR titles, on their respective project pages See #3956. Following is before/after for each page: ## Group title ### Before  ### After  --- ## Commit title ### Before  ### After  --- ## Branch name ### Before  ### After  --- ## Tags name in list ### Before  ### After  --- ## Tag name ### Before  ### After  --- ## Issue title in list ### Before  ### After  --- ## MR title in list ### Before  ### After  See merge request !2422
-