| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Added also a `Gitlab::Ci::Build::Artifacts::Metadata::ParserError`
exception class.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This is needed because of backward compatibility. Previously artifacts
archive had `.tar.gz` format, but artifacts browser requires ZIP format
now.
|
| |
|
|
| |
`artifacts?` method checks if artifacts archive is available.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This support is not completed though, as parent directory that is first
in collection returned by `directories!` is not iterable yet.
|
| | |
|
| |
|
|
|
| |
This implementation makes it possible to browse artifacts, it
depends on artifacts metadata.
|
| |
|
|
| |
This reverts nesting artifacts controller in builds module.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| | |
titles, on their respective project pages
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
LDAP Sync blocked user edgecases
Allow GitLab admins to block otherwise valid GitLab LDAP users
(https://gitlab.com/gitlab-org/gitlab-ce/issues/3462)
Based on the discussion on the original issue, we are going to differentiate "normal" block operations to the ldap automatic ones in order to make some decisions when its one or the other.
Expected behavior:
- [x] "ldap_blocked" users respond to both `blocked?` and `ldap_blocked?`
- [x] "ldap_blocked" users can't be unblocked by the Admin UI
- [x] "ldap_blocked" users can't be unblocked by the API
- [x] Block operations that are originated from LDAP synchronization will flag user as "ldap_blocked"
- [x] Only "ldap_blocked" users will be automatically unblocked by LDAP synchronization
- [x] When LDAP identity is removed, we should convert `ldap_blocked` into `blocked`
Mockup for the Admin UI with both "ldap_blocked" and normal "blocked" users:
There will be another MR for the EE version.
See merge request !2242
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Show referenced MRs & Issues only when the current viewer can access them
This addresses both issues identified in #6066.
## The private MR by user `remy2` with a note referencing to a public issue
---
## The public issue viewed by user `remy` **who doesn't have access to `remy2/private-project`** before the fix
---
## The public issue viewed by user `remy` **who doesn't have access to `remy2/private-project`** with the fix
---
## The public issue viewed by user `remy2` with the fix (no change)
See merge request !2405
|
| | |\ \ \
| | | |/
| | |/|
| | | | |
fix/private-references
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is moved to a model method rather than an helper method because the
API will need it too.
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Allow broadcast messages to be edited
Closes #3046
See merge request !2268
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Closes #3046
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now it returns the fully-formatted message so we can be consistent about
how it's shown.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | |_|/ /
|/| | | |
|
| |/ / / |
|
| |\ \ \
| | | |
| | | | |
See merge request !2406
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
merge request close message moved and merge request now refered by `!`.
Fixes #4161
See merge request !2387
|
| | | | | | |
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Comment and close button does not submit comment
See merge request !2399
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
closing/reopening properly.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
