Hey @xiangxinyong, Welcome to openEuler Community.
All of the projects in OpenEuler Community are maintained by @openeuler-ci-bot.
That means the developpers can comment below every pull request or issue to trigger Bot Commands.
Please follow instructions at https://gitee.com/openeuler/community/blob/master/en/command.md to find the details.

@imjoey @freesky-edward

/kind enhancement

IMHO, the CI is neccessary and important not only to order check but to yaml node spelling check and member id existing check. I suggest to add them as well.

@xiangxinyong @freesky-edward Sorry for bothering you. I am trying to add a job named task-check-community-yaml in jenkins but unfortunately I can not figure out which repository I should add relative script to. I guess we're using jenkins shared libraries for basic checking, right? If not, do I need an jenkins account for mannual configuration? So could you please give me a hand? Great thanks.

Hey @imjoey I am willing to add a jenkinsfile like hadoop community:

https://github.com/apache/hadoop/blob/trunk/Jenkinsfile

so that all the projects in https://gitee.com/openeuler will have their own jenkinsfile.

Our infra jenkins server is here:

http://114.116.250.98/

If you want to make some modifications in the jenkins server,
please feel free to ping me or @freesky-edward .

So I guess your task-check-community-yaml can be added in
https://gitee.com/openeuler/infrastructure as a jenkinsfile.
Any thoughts?

@imjoey sorry for making you confused, actually, we only set up the jenckins server right now, all the jobs priting in PR you can see are configuration on jenkins console by manual, so if you are going to add a new pipleline task, folowing this way would be a brisk choice.
but for the further plan, the SCM solution that is mentioned by @xiangxingyong above should be a new direction we are considering. that will allow the maintainers of each projects in openeuler group(note: excluse src-openeuler) are able to DIY their own tasks. but there still several parts should be done:

• submit the jenkinsfile by maintainer
• configuration the pipleline as well as the authentication.
  for the second step, it would better find an easy way instead of jenkins console, e.g. scripts configuration. the best practice as far as I know is travis against github.com. but it may take much workload.
  any suggestion will be much appreciated.

@xiangxinyong @freesky-edward Thank you for the tips.

A standalone Jenkinsfile for each repository is much convenient for contributors to customize the CI process and also I do not need asking for jenkins server access any more. That's great!

BTW: with regard to there are hundreds of repositories, we could also take advantage of Global Shared Libraries for common pipeline tasks to ease the CI workload.

@imjoey Thanks your suggestions:)
yep. we need global pipeline since we have hundreds of repos.
Actually we have already global pipeline for https://gitee.com/src-openeuler repos,
you can find the details from here http://114.116.250.98/
The global pipline is based on one gitee's global webhook for all the repos:)

@xiangxinyong yes, that's really awesome and thanks for the great work. Days ago, I submitted an issue that we'd better to prevent the .pyc files from being added into repository, please see 1 for details. I'm considering to contribute to the openeuler-check-binary-file project in jenkins to recognize more binary file like .pyc, .class, .jar and etc. Could you please guide me where to find the relative scripts defined in openeuler-check-binary-file? Thanks.

@imjoey thanks, all the ci files are in ci_check repository, could you please open PR for the privillege first?

@imjoey script file for binary check task is located at https://gitee.com/src-openeuler/ci_check/blob/master/job_scripts/check_binary.py,feel free to update.

@freesky-edward @TommyLike thank you for the help.