Infrastructure: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
(Updated who is responsible for static analysis tools)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Potential scope for infrastructure work in the Qt project:
Potential scope for infrastructure work in the Qt project:


* Gerrit maintenance, feature additions, bug fixing, CI integration
*Gerrit maintenance, feature additions, bug fixing, CI integration
* Additional CI tools, extending CI tools such as CDash and Jenkins
*Additional CI tools, extending CI tools such as CDash and Jenkins
* Higher level Qt specific tools such as Gamma Ray
*Higher level Qt specific tools such as Gamma Ray
* Tools to make development, debugging and contribution to Qt easier.
*Tools to make development, debugging and contribution to Qt easier.


== Potential Tasks ==
==Potential Tasks==


* Gerrit
*Gerrit
** Fixing issues in new features, getting them upstream
**Fixing issues in new features, getting them upstream
** CI integration generalization - CDash, Jenkins, Hudson
**CI integration generalization - CDash, Jenkins, Hudson
** Improved static analysis for uploaded changes
**Improved static analysis for uploaded changes
** Enabling topic review functionality again
**Enabling topic review functionality again
* Process for adding more CI, daily/weekly/monthly testing on wider range of hardware, compilers, OS
*Process for adding more CI, daily/weekly/monthly testing on wider range of hardware, compilers, OS
* How should tools like Gamma Ray be collaborated on/promoted?
*How should tools like Gamma Ray be collaborated on/promoted?


We (Kitware) are developing against the topic provided by Code Think with the topic branch functionality. We have fixed several issues and made our changes available on Github [https://github.com/cjh1/gerrit/tree/topic_views] along with providing a test server [http://reviewtest.source.kitware.com:81] running the code in the branch. We also attended the GitTogether and discussed integration of the topic branch functionality with Shawn Pearce.
We (Kitware) are developing against the topic provided by Code Think with the topic branch functionality. We have fixed several issues and made our changes available on Github [https://github.com/cjh1/gerrit/tree/topic_views] along with providing a test server [http://reviewtest.source.kitware.com:81] running the code in the branch. We also attended the GitTogether and discussed integration of the topic branch functionality with Shawn Pearce.


== People ==
==People==


There is no official structure in place yet, but here goes a self-nominated list as a first approximation. Add yourself if you want to help or drive a task (I am sure there are more):
There is no official structure in place yet, but here goes a self-nominated list as a first approximation. Add yourself if you want to help or drive a task (I am sure there are more):


* [[User:Mhanwell|Marcus D. Hanwell]] - bootstrapping this, Gerrit, topic review, CI, process
*[[User:Mhanwell|Marcus D. Hanwell]] - bootstrapping this, Gerrit, topic review, CI, process
* [[User:Charleyb|Charley Bay]] - CI, static analysis
*[[User:Jimis|Dimitrios Apostolou]], [[AnnaWojciechowska|Anna Wojciechowska]] - static analysis
* [[User:Tosaraja|Tony Sarajärvi]] - CI
*[[User:Tosaraja|Tony Sarajärvi]] - CI
* [[User:Buddenha|Oswald Buddenhagen]] - Sanity Bot master, "Gerrit and Git stuff"
*[[User:Buddenha|Oswald Buddenhagen]] - Sanity Bot master, "Gerrit and Git stuff"

Latest revision as of 13:57, 23 February 2021

Potential scope for infrastructure work in the Qt project:

  • Gerrit maintenance, feature additions, bug fixing, CI integration
  • Additional CI tools, extending CI tools such as CDash and Jenkins
  • Higher level Qt specific tools such as Gamma Ray
  • Tools to make development, debugging and contribution to Qt easier.

Potential Tasks

  • Gerrit
    • Fixing issues in new features, getting them upstream
    • CI integration generalization - CDash, Jenkins, Hudson
    • Improved static analysis for uploaded changes
    • Enabling topic review functionality again
  • Process for adding more CI, daily/weekly/monthly testing on wider range of hardware, compilers, OS
  • How should tools like Gamma Ray be collaborated on/promoted?

We (Kitware) are developing against the topic provided by Code Think with the topic branch functionality. We have fixed several issues and made our changes available on Github [1] along with providing a test server [2] running the code in the branch. We also attended the GitTogether and discussed integration of the topic branch functionality with Shawn Pearce.

People

There is no official structure in place yet, but here goes a self-nominated list as a first approximation. Add yourself if you want to help or drive a task (I am sure there are more):