- 20 Jan, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 19 Jan, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 15 Jan, 2016 3 commits
-
-
Robert Speicher authored
[ci skip] Closes #5931
-
Kamil Trzcinski authored
-
Steffen Köhler authored
some OAuth providers (kerberos for example) only provide a username and an email, but no name. Therefore a signup fails because the name is empty. Best guess for the name is probably the username, therefore use it as name.
-
- 14 Jan, 2016 35 commits
-
-
Kamil Trzcinski authored
This allows us to implement artifacts passing: runner will download artifacts from all prior builds
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Tomasz Maczukin authored
-
Rémy Coutable authored
-
Douwe Maan authored
-
Grzegorz Bizon authored
Added also a `Gitlab::Ci::Build::Artifacts::Metadata::ParserError` exception class.
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
We do not want to allow runners to upload a metadata file. This needs to be generated by Workhorse only.
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
In this version we will support only relative paths in artifacts metadata. Support for absolute paths will be introduced later.
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
This changes the format of metadata to handle paths, that may contain whitespace characters, new line characters and non-UTF-8 characters. Now those paths along with metadata in JSON format are stored as length-prefixed strings (uint32 prefix). Metadata file has a custom format: 1. First string field is metadata version field (string) 2. Second string field is metadata errors field (JSON strong) 3. All subsequent fields is pair of path (string) and path metadata in JSON format. Path's metadata contains all fields that where possible to extract from ZIP archive like date of modification, CRC, compressed size, uncompressed size and comment.
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
[ci skip]
-
Grzegorz Bizon authored
-