| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Fixes flaky master
|
| |\
| |
| |
| |
| |
| |
| | |
Fix flaky time related failure in spec/models/ci/pipeline_schedule_spec.rb
Closes #62760
See merge request gitlab-org/gitlab-ce!29778
|
| | |
| |
| |
| | |
Also removes test from quarantine
|
| |/
|
|
|
|
|
|
| |
We are deprecating this service in favor of instance wide clusters.
Therefore we removed some code that is not anymore needed for a
readonly cluster and also we added some flags to allow for this
deprecation. These flags are to be removed in the next release when
we finally completelly remove KubernetesService.
|
| |\
| |
| |
| |
| |
| |
| | |
Preventing blocked users and their PipelineSchdules from creating new Pipelines
Closes #47756
See merge request gitlab-org/gitlab-ce!27318
|
| | |
| |
| |
| | |
updated several specs and factories to accomodate new permissions
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Revert "Disable retrying cancelled jobs"
Closes #62350
See merge request gitlab-org/gitlab-ce!29201
|
| | |/
| |
| | |
This reverts merge request !27503
|
| | |
| |
| |
| |
| | |
See
https://gitlab.com/gitlab-org/gitlab-ce/issues/62760
|
| |/
|
|
|
| |
`Time.now` is local time, yet `Time.zone.now` is application
configuration time. They can be different.
|
| |\
| |
| |
| |
| | |
Introduce sidekiq worker for auto merge process
See merge request gitlab-org/gitlab-ce!28780
|
| | |
| |
| |
| |
| | |
As we have a central domain for auto merge process today,
we should use a single worker for any auto merge process.
|
| |\ \
| |/
|/|
| |
| |
| |
| |
| |
| | |
'set-real-next-run-at-for-preventing-duplciate-pipeline-creations' into 'master'
Make pipeline schedule worker resilient
Closes gitlab-com/gl-infra/production#805 and #61955
See merge request gitlab-org/gitlab-ce!28407
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, pipeline schedule worker is unstable because it's
sometimes killed by excessive memory consumption.
In order to improve the performance, we add the following fixes:
1. next_run_at is always real_next_run, which means the value
always takes into account of worker's cron schedule
1. Remove exlusive lock. This is already covered by real_next_run
change.
1. Use RunPipelineScheduleWorker for avoiding memory killer.
Memory consumption is spread to the multiple sidekiq worker.
|
| |/
|
|
|
|
|
| |
- Renames attributes from stat to project_statistiscs_name and attribute
to statistic_attribute
- Reordes methods on UpdateProjectStatistics concern
- Removes unused module from Ci::Build
|
| |
|
|
|
|
| |
We've already migrated all the legacy artifacts to the new realm,
which is ci_job_artifacts table.
It's time to remove the old code base that is no longer used.
|
| |
|
|
|
| |
Extracts combining the job_artifacts relation with the with_reports
scope for getting report artifacts into a method.
|
| | |
|
| | |
|
| |
|
|
| |
Update documentation to reflect removal
|
| |
|
|
|
| |
Rails 5 requires that belongs_to associations have the associated record
present. These tests were failing because they had nil values.
|
| |
|
|
|
|
|
|
|
|
|
| |
Immediate configuration is not ideal for group and instance
level clusters as projects that may never be deployed would
still have Kubernetes namespaces and service accounts created
for them.
As of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25586
we now create only the resources that are required for the
project being deployed, at the time of deployment.
|
| |\
| |
| |
| |
| | |
Strip whitespace for PipelineSchedule#cron
See merge request gitlab-org/gitlab-ce!27990
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Add env_var and file as supported types for CI variables. Variables of
type file expose to users existing gitlab-runner behaviour - save
variable value into a temp file and set the path to this file in an ENV
var named after the variable key.
Resolves https://gitlab.com/gitlab-org/gitlab-ce/issues/46806.
|
| | |
| |
| |
| | |
Refactor
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Adds an endpoint on PipelinesController
- Adds a service that iterates over every build in a stage and
plays it.
- Includes 'play_manual' details on EntitySerializer
- Builds a new Stage state: PlayManual. An stage can take this status if
it has manual builds or an skipped, scheduled or manual status
- Includes FE modifications and specs
|
| |\ \
| |/
|/|
| |
| |
| |
| |
| |
| | |
'53064-bypassing-pipeline-jobs-by-canceling-the-pipeline-and-manually-running-later-jobs' into 'master'
Disable retrying cancelled jobs
Closes #53064
See merge request gitlab-org/gitlab-ce!27503
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Specs that test canceled jobs now
- expect them not to be retryable or playable
- expect them not to show retry buttons
Specs that test retryability now
- use failed status instead of canceled status
|
| | |
| |
| |
| |
| |
| |
| | |
With Pipelines for Merge Requests feature, users cannout keep using
$CI_COMMIT_REF_NAME and _SLUG predefined variables for dynamic
environments. We fix this problem by explicitly looking at the source
ref.
|
| | |
| |
| |
| |
| | |
This enables sending a chat message to Slack or Mattermost
upon a successful, failed, or canceled deployment
|
| |\ \
| | |
| | |
| | |
| | | |
Add CI variable CI_REF_PROTECTED
See merge request gitlab-org/gitlab-ce!26716
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This variable shows if the branch the runner is executing is protected
or not.
References: #50909
|
| | | |
| | |
| | |
| | | |
Model.new.attributes now also returns encrypted attributes.
|
| | |/
|/|
| |
| | |
Refactor existing tests as a shared example
|
| |\ \
| | |
| | |
| | |
| | | |
Backport metrics report type
See merge request gitlab-org/gitlab-ce!26798
|
| | |/
| |
| |
| |
| | |
This backports the changes from
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10452
|
| |/
|
|
| |
with expired artifacts
|
| |
|
|
|
| |
Backports https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10161
(code out of ee/ folder).
|
| |\
| |
| |
| |
| | |
Fix MWPS doesn't work for merge request pipelines
See merge request gitlab-org/gitlab-ce!26906
|
| | |
| |
| |
| |
| |
| | |
MWPSService currently uses the old pipeline lookup method. It searches
related merge requests with pipeline.ref, however, this doesn't work
for attached/detached merge request pipelines.
|
| |/
|
|
|
|
|
| |
- rewords examples starting with 'should'
- rewords examples starting with 'it'
Note: I had to manually fixup "onlies" to "only"
|
| |\
| |
| |
| |
| | |
Drop legacy artifacts usage as there are no leftovers
See merge request gitlab-org/gitlab-ce!24294
|
| | |
| |
| |
| |
| |
| | |
Legacy artifacts have been correctly migrated to new place -
ci_job_artifacts. Now it's time to remove the related code, but before
that we should ensure it doesn't break anything by using feature flag.
|
| |/
|
|
|
|
| |
We're moving from using terminology related to terminals when
we refer to Websockets connections in Workhorse.
It's more appropiate a concept like channel.
|
| |
|
|
| |
This is for merge request pipelines
|
| |
|
|
| |
While we debug why this is failing
|
| |
|
|
| |
Adds `# frozen_string_literal: true` to spec/models ruby files
|
