-
Notifications
You must be signed in to change notification settings - Fork 173
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
Create gitlab pipeline #534
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks alot.
Is the intention to replace all existing Github Actions or just the benches with Gitlab?
I think we need to run the tests too then preferable on Linux, macos and Windows as we do currently.
So initially I was thinking about that because it's easier for CI team to maintain pipelines in one place. But since you have tests on different platforms we have to keep some of the GHA tests for some time |
Ok, then we should probably remove |
stage: lint | ||
<<: *kubernetes-env | ||
script: | ||
- rustup component add rustfmt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why isn't the rustfmt
component part of the base image? Seems like setting up the toolchain components should be in a single place?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually, we run cargo fmt
from the nightly release in other repos. I'll add comment here to fix it later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. I guess the question still stands though: wherever you install the nightly toolchain could be a good place to add the rustfmt
component as well? And then run cargo +nightly fmt
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer cargo fmt
from stable, but cargo +nightly fmt
works too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's not a big deal, we can add it to the CI image for stable, too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added clippy and fmt to the image however need to wait while issue in substrate is fixed
stage: lint | ||
<<: *docker-env | ||
script: | ||
- rustup component add clippy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same concern here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above, I prefer CI to use stable but yes, I'm ok running nightly clippy too. Curious though, why is clippy not included in the base image?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean paritytech/base-ci-linux
? It was never requested before to run a stable clippy
or fmt
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM,
I'm not convinced about moving clippy
to Gitlab though because the Github UI is so nice instead of reading text output from Gitlab.
I agree with this. |
@dvdplm @niklasad1 can you please point me to what's wrong with GitLab's Just the highlighted warnings? Also note that these are the outputs on the same commit, completely different! Both installed on stable Rust. |
The fact that |
Yes, it's very unlikely that you would click on the individual jobs when reviewing PRs to look at potential lint warnings.
It's just because the current clippy lint runs |
@niklasad1 I'm a little bit confused. Was this pr closed accidentally or on purpose? |
fb17068
to
7f76577
Compare
stage: lint | ||
<<: *kubernetes-env | ||
script: | ||
- rustup component add rustfmt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stage: lint | ||
<<: *docker-env | ||
script: | ||
- rustup component add clippy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- echo ${CI_RUNNER_DESCRIPTION} | ||
- echo "RUNNER_NAME=${CI_RUNNER_DESCRIPTION}" > runner.env | ||
|
||
publish-bench: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you need to use paritytech/ci-linux
here? It's better off with a lighter paritytech/tools
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's better off with a lighter paritytech/tools
Agree, fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
then it maybe makes sense to remove that default image from k8s anchor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer to keep k8s anchor as it is so it is equal through all our .gitlab-ci.yml
files in different repos
Co-authored-by: Denis Pisarev <17856421+TriplEight@users.noreply.github.com>
stage: lint | ||
<<: *kubernetes-env | ||
script: | ||
- rustup component add rustfmt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer cargo fmt
from stable, but cargo +nightly fmt
works too.
stage: lint | ||
<<: *docker-env | ||
script: | ||
- rustup component add clippy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above, I prefer CI to use stable but yes, I'm ok running nightly clippy too. Curious though, why is clippy not included in the base image?
@radupopa2010 I think we need to merge master in here. |
rebase fixed the pipeline |
I think it's possible. I see a few options: send an email, send a matrix message or create a GitHub issue. I can create a new issue in our tracker where we can discuss the way how alert is sent and the conditions. |
stage: lint | ||
<<: *kubernetes-env | ||
script: | ||
- rustup component add rustfmt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's not a big deal, we can add it to the CI image for stable, too.
stage: lint | ||
<<: *docker-env | ||
script: | ||
- rustup component add clippy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean paritytech/base-ci-linux
? It was never requested before to run a stable clippy
or fmt
.
- echo ${CI_RUNNER_DESCRIPTION} | ||
- echo "RUNNER_NAME=${CI_RUNNER_DESCRIPTION}" > runner.env | ||
|
||
publish-bench: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
then it maybe makes sense to remove that default image from k8s anchor.
Added gitlab pipeline for this repo.
Closes https://github.com/paritytech/ci_cd/issues/240