| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
We exclude known EE projects, and check the project directory
name for EE forks.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This finishes the procedure for migrating events from the old format
into the new format. Code no longer uses the old setup and the database
tables used during the migration process are swapped, with the old table
being dropped.
While the database migration can be reversed this will 1) take a lot of
time as data has to be coped around 2) won't restore data in the
"events.data" column as we have no way of restoring this.
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37241
|
|\
| |
| |
| |
| | |
Move Incoming Email checks to System Checks
See merge request !14028
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
| |
That way we don't need to install it in production, since it's really
not needed there.
|
|\
| |
| |
| |
| | |
Validate PO files in static analysis
See merge request !13000
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The initializers including this were doing so at the top level, so every object
loaded after them had a `current_application_settings` method. However, if
someone had rack-attack enabled (which was loaded before these initializers), it
would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't
have that method.
To fix this:
1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need
`Object.new.current_application_settings` to work.
2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it
like that in several places.
3. Change the initializers to use that new form.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- Allow imports into nested groups
- Make sure it sets the correct visibility level when creating new
groups
While doing this, I moved the import into a testable class, that made
it easier to improve.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Related to !13108. Mostly this is just running the rake task and
changing the task a bit to catch cases like the project already existing
or so. The rake task moves archives to the vendor/project_template
directory, which are checked in too.
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Don't include anything to Kernel only because of tasks
Closes #36003
See merge request !13380
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Unfortunately rake doesn't have nested context,
everything just runs on a main rake object.
This is probably due to compatibility issue,
but anyway, we could just extend the object.
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
'master'
Unset the `RUBYOPT` env variable before installing `gitaly-ruby`
Closes #35941 and #35967
See merge request !13313
|
| |
| |
| |
| |
| |
| | |
GitLab Shell on each test run
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
| |
| |
| |
| | |
This reverts commit 23c502b43404aa70741462da5d57c23196f6088a, reversing
changes made to 1018ab0516fd94d1ffbc05a0ad8499947dd9630d.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Improve GitHub importer
Closes #27429
See merge request !12886
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Allow projects to be started from a template
Closes #32420
See merge request !13108
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* master: (623 commits)
Fix issues with pdf-js dependencies
fix missing changelog entries for security release on 2017-01-23
Update top bar issues icon
Fix pipeline icon in contextual nav for projects
Since mysql is not a priority anymore, test it less
Fix order of CI lint ace editor loading
Add container registry and spam logs icons
Fix different Markdown styles
Backport to CE for:
Make new dropdown dividers full width
Fix spec
Fix spec
Fix spec
Bump GITLAB_SHELL_VERSION and GITALY_VERSION to support unhiding refs
Add changelog
Install yarn via apt in update guides
Use long curl options
fix
Add a spec for concurrent process
Remove monkey-patched Array.prototype.first() and last() methods
...
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
First iteration, and some stuff is missing. But basically this rake task
does a clone of a project we've pointed it to. Than creates a project on
the GDK, which should be running in the background. This project is
exported, after which we move that archive to the location we need it.
We clean up by removing the generated project.
The first idea was to export the project on .com too, however than we
might run into ImportExport versions mismatch. This could've been
circumvented by checkout out an older commit locally. This however is
not needed yet, so we opted to not go this route yet, instead we will
iterate on what we got.
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
Gitaly needs to know where to find gitlab-shell
See merge request !13306
|
| | |/
| |/| |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| | |
If we call `system('rake', 'taks_name')`, `ENV['RUBYOPT']` is set to
`'-rbundler/setup'` but some tasks (e.g. `gitlab:gitaly:install` need
a clean env since they install their own Gem bundle.
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|\ \
| | |
| | |
| | |
| | | |
[CE] Added Legacy Storage format
See merge request !13149
|
| | | |
|
|/ / |
|
| | |
|
| |
| |
| |
| | |
Closes #35615
|
|/ |
|
|
|
|
|
|
|
| |
Fixes an issue where, when using branch versions, the component wouldn't
be updated after the first branch checkout. We also save one step, since
checking out the FETCH_HEAD with `-f` already does what `reset --hard`
did.
|
|\
| |
| |
| |
| |
| |
| | |
Remove coffee-rails gem
Closes #34831
See merge request !12715
|