An error occurred fetching the project authors.
- 13 May, 2021 1 commit
-
-
Furkan Ayhan authored
-
- 05 May, 2021 1 commit
-
-
Maxime Orefice authored
This commit stop exposing a new attribute which allowed us to determine when showing our download dropdown button on the pipeline index page. We will now always display it by default.
-
- 30 Apr, 2021 1 commit
-
-
Furkan Ayhan authored
-
- 28 Apr, 2021 1 commit
-
-
Maxime Orefice authored
-
- 15 Apr, 2021 1 commit
-
-
Furkan Ayhan authored
This will help us to track possible dramatic failure changes when we deploy new features / bug fixes.
-
- 09 Apr, 2021 1 commit
-
-
gentcys authored
-
- 06 Apr, 2021 4 commits
-
-
Huzaifa Iftikhar authored
-
Furkan Ayhan authored
This reverts merge request !57232
-
Furkan Ayhan authored
-
Furkan Ayhan authored
-
- 30 Mar, 2021 1 commit
-
-
lauraMon authored
* Also adds a uses_needs? method to Ci::Pipeline
-
- 23 Mar, 2021 1 commit
-
-
Craig Andrews authored
Signed-off-by: Craig Andrews <candrews@integralblue.com>
-
- 09 Mar, 2021 1 commit
-
-
Winkie's authored
-
- 04 Mar, 2021 1 commit
-
-
Aishwarya Subramanian authored
CI_PROJECT_CONFIG_PATH is same as CI_CONFIG_PATH. This MR moves CI_CONFIG_PATH as a Project variable (so it can use it in the include section). This is necessary since the include section can resolve on pre-defined project variables. Removes support for CI_PROJECT_CONFIG_PATH to avoid duplication of variables that have the same behavior
-
- 01 Mar, 2021 2 commits
-
-
Furkan Ayhan authored
We are trying to remove ProcessPipelineService#update_retried method. When doing this, we found that this method is still used for some cases. This commit fixes those usages.
-
Maxime Orefice authored
This commit renames our merge_request_pipeline as merged_request_pipeline. This is part of our effort to consolidate our naming with merge request pipeline.
-
- 26 Feb, 2021 1 commit
-
-
Furkan Ayhan authored
When status of downstream pipeline is updated, the upstream cache is not updated. In this commit; - Removed "cachable?" check - Moved from EE to CE and refactored upstream/downstream pipeline cache expiration - Implement calling ExpirePipelineCacheWorker from ExpireJobCacheWorker
-
- 24 Feb, 2021 4 commits
-
-
Allison Browne authored
-
Allison Browne authored
Perfomance and readability optimizations
-
Allison Browne authored
51.1960s -> 34.8263s
-
Maxime Orefice authored
-
- 18 Feb, 2021 1 commit
-
-
Thong Kuah authored
This should prevent object modification leading to accidental execution order dependencies between tests
-
- 10 Feb, 2021 1 commit
-
-
Allison Browne authored
To avoid using runner resources on deleted projects we cancel all cancelable jobs as the first step in deletion
-
- 03 Feb, 2021 1 commit
-
-
Maxime Orefice authored
This commits allow us to expose our new quality report on a a merge request. This will allow the frontend to display quality degration easily on the merge request.
-
- 28 Jan, 2021 1 commit
-
-
Shinya Maeda authored
This commit moves the resource group implementation to the super class.
-
- 27 Jan, 2021 2 commits
-
-
Maxime Orefice authored
This commit refactors our pipeline artifact factories. It removes duplicates and renames some factories to be consistent with existing ones.
-
Cong Chen authored
-
- 22 Jan, 2021 3 commits
-
-
Maxime Orefice authored
This commit generates a codequality report as a pipeline_artifact after a pipeline completes. It will be used to display codequality degradations on a MR diff.
-
pbair authored
With the change to using before_save hook to set the iid on an object, normal validations can't be used to verify the presence of the iid. In normal situations, the iid should always be set by either ensure_scope_iid hook or application logic, but since we're lacking database constraints on some tables we don't want to silently insert bad data. To prevent unforeseen issues cause by bugs, add an additional before_save hook to raise an exception if the iid is not set as it should be.
-
pbair authored
Convert AtomicInternalId to set iid values in before_create or before_update callbacks, rather than before_validation.
-
- 19 Jan, 2021 1 commit
-
-
Alex Kalderimis authored
This enables the Jira sync builds feature.
-
- 15 Jan, 2021 1 commit
-
-
Maxime Orefice authored
This commit refactors our existing model to make it easier to add a new file_type called code_quality. This new type will be used in a follow up MR to create a new report.
-
- 16 Dec, 2020 1 commit
-
-
Ben Bodenmiller authored
This changes the `CI_HAS_OPEN_MERGE_REQUEST` to `CI_OPEN_MERGE_REQUESTS`.
-
- 10 Dec, 2020 1 commit
-
-
Erick Bajao authored
We moved this to pipeline completion so that we have the total count of failures across all builds. We need this count to check if the limit is reached.
-
- 09 Dec, 2020 1 commit
-
-
Alex Kalderimis authored
This adds support for the `build` module for JiraConnect, and synchronizes pipeline status for linked Jira issues. Specifically: - we add a new section to the application descriptor (requiring an update of our installed JiraConnect app) - we add a new worker triggered by changes in status of pipelines - for every pipeline that is the head-pipeline of a relevant MR (determined by the presence of Jira issue keys in either the branch name or the title) we send that status information to Jira. Some notes: - The concept of a build seems to map most closely to the GitLab concept of a pipeline, so that is the unit of synchronization. - The Jira API allows the number of 'tests' in a build to be reported, with a breakdown by pass/fail/skip. Currently this is implemented to be the number of Ci::Builds in a pipeline - since we cannot guarantee that exact test numbers are available. This may be subject to change, or at least upgrade for test frameworks for which we have breakdown stats.
-
- 08 Dec, 2020 1 commit
-
-
Doug Stull authored
- adhere to styleguide
-
- 07 Dec, 2020 1 commit
-
-
Shinya Maeda authored
This commit optimizes the query by removing redundant clauses.
-
- 04 Dec, 2020 1 commit
-
-
Stan Hu authored
If no pipeline hooks are active for a project, we still go through the trouble of generating the hook data, which may make a number of SQL, Gitaly, and Redis calls unnecessarily. Most projects don't have any hooks, so we can reduce the amount of load by only building the hook data if there are active hooks or services. This requires several cheap SQL queries. Note that the optimal way would be to lazily load the hook data, but that requires more complex changes. This is a similar optimization that was implemented for PostReceive (https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/31741). Relates to https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/12055
-
- 02 Dec, 2020 1 commit
-
-
Fabio Pitino authored
-
- 01 Dec, 2020 1 commit
-
-
Erick Bajao authored
As we parse the cobertura XML, based on the given project full path and pipeline worktree paths, we will make some assumptions on how to determine the correct path of filenames that are not relative to the project root.
-