Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gitlab-ci: enable skip running of the previous pushes on developers branches #5035

Closed
avtikhon opened this issue Jun 1, 2020 · 1 comment
Assignees
Labels
feature A new functionality qa Issues related to tests or testing subsystem

Comments

@avtikhon
Copy link
Contributor

avtikhon commented Jun 1, 2020

Tarantool version:
All

OS version:
All

Bug description:
Need to enable ability to skip running of the previous pushes in running gitlab-ci queue on developers branches. As found this feature has 2 special switching check boxes in gitlab-ci CI/CD configuration:
https://gitlab.com/help/ci/pipelines/settings#auto-cancel-pending-pipelines
To make it workable the whole testing project in gitlab-ci must be either with these options or w/o it.
But in the same project there are release branches testing which must be run for each push and can't be skipped. To resolve this issue found the single solution to split gitlab-ci project in two new with testing on branches which can be skipped and branches that can't be skipped.
Skip able branches: https://gitlab.com/tarantool/tarantool-core-branches/
Not skip able branches: https://gitlab.com/tarantool/tarantool/
Created patch for splitting jobs on two projects. This patch can be pushed into release branches only after the new gitlab-ci project https://gitlab.com/tarantool/tarantool-core-branches/ will be completely prepared as https://gitlab.com/tarantool/tarantool/ .

Steps to reproduce:

Optional (but very desirable):

  • coredump
  • backtrace
  • netstat
@avtikhon avtikhon added feature A new functionality qa Issues related to tests or testing subsystem labels Jun 1, 2020
@avtikhon avtikhon self-assigned this Jun 1, 2020
avtikhon added a commit that referenced this issue Jun 1, 2020
Needed to enable ability to skip running/pending jobs/pipelines in
running gitlab-ci queue on developers branches. As found this feature
had 2 special switching check boxes in gitlab-ci CI/CD configuration:
  https://gitlab.com/help/ci/pipelines/settings#auto-cancel-pending-pipelines

To make it workable the whole testing project in gitlab-ci must be
either with these options or w/o it. But in the same project there are
release branches testing, which must be run for each push and can't be
skipped. To resolve this issue found the single solution to split
gitlab-ci project in two:
  new one with testing on branches which can be skipped:
    https://gitlab.com/tarantool/tarantool-core-branches/
  and old one on branches that can't be skipped:
    https://gitlab.com/tarantool/tarantool/

Current patch can be pushed into release branches only after the new
gitlab-ci project https://gitlab.com/tarantool/tarantool-core-branches/
will be completely prepared as https://gitlab.com/tarantool/tarantool/.

Closes #5035
avtikhon added a commit that referenced this issue Jun 1, 2020
Needed to enable ability to skip running/pending jobs/pipelines in
running gitlab-ci queue on developers branches. As found this feature
had 2 special switching check boxes in gitlab-ci CI/CD configuration:
  https://gitlab.com/help/ci/pipelines/settings#auto-cancel-pending-pipelines

To make it workable the whole testing project in gitlab-ci must be
either with these options or w/o it. But in the same project there are
release branches testing, which must be run for each push and can't be
skipped. To resolve this issue found the single solution to split
gitlab-ci project in two:
  new one with testing on branches which can be skipped:
    https://gitlab.com/tarantool/tarantool-core-branches/
  and old one on branches that can't be skipped:
    https://gitlab.com/tarantool/tarantool/

Current patch can be pushed into release branches only after the new
gitlab-ci project https://gitlab.com/tarantool/tarantool-core-branches/
will be completely prepared as https://gitlab.com/tarantool/tarantool/.

Closes #5035
avtikhon added a commit that referenced this issue Jun 1, 2020
Needed to enable ability to skip running/pending jobs/pipelines in
running gitlab-ci queue on developers branches. As found this feature
had 2 special switching check boxes in gitlab-ci CI/CD configuration:
  https://gitlab.com/help/ci/pipelines/settings#auto-cancel-pending-pipelines

To make it workable the whole testing project in gitlab-ci must be
either with these options or w/o it. But in the same project there are
release branches testing, which must be run for each push and can't be
skipped. To resolve this issue found the single solution to split
gitlab-ci project in two:
  new one with testing on branches which can be skipped:
    https://gitlab.com/tarantool/tarantool-core-branches/
  and old one on branches that can't be skipped:
    https://gitlab.com/tarantool/tarantool/

Current patch can be pushed into release branches only after the new
gitlab-ci project https://gitlab.com/tarantool/tarantool-core-branches/
will be completely prepared as https://gitlab.com/tarantool/tarantool/.

Closes #5035
@avtikhon avtikhon added this to DOING in Quality Assurance Jun 1, 2020
@avtikhon avtikhon removed this from DOING in Quality Assurance Jul 3, 2020
@ylobankov
Copy link
Member

Not relevant anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A new functionality qa Issues related to tests or testing subsystem
Projects
None yet
Development

No branches or pull requests

2 participants