-
Notifications
You must be signed in to change notification settings - Fork 131
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
config: uncomment many projects in projects-to-test-on.properties #543
Conversation
Are we sure no other existing checkstyle CI is using this file and uncommenting things manually? |
Looks like we do not use it https://github.com/checkstyle/checkstyle/search?q=projects-to-test-on.properties&type= |
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 think we can remove duplicates with excludes, it was used when we had no diff.groovy.
Old jdk can be removed, and keep only jdk9.
We can activate it a bit later, as we see benefits of new model of regression testing.
Or we can activate not and contributors can be advised to make copy of this file he is not lucky. But majority of executions will be lucky.
5e4aa71
to
617e32b
Compare
I removed project with exclusions, also openjdk is changed to git repo because github action does not support mercurial |
There is: ➜ checkstyle git:(master) grep -R "projects-to-test-on.properties" | grep -v "groovy"
.ci/no-exception-test.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/no-exception-test.sh: sed -i.'' 's/#guava|/guava|/' projects-to-test-on.properties
.ci/no-exception-test.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/no-exception-test.sh: sed -i.'' 's/#guava|/guava|/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#hibernate-orm/hibernate-orm/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#spotbugs/spotbugs/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#spoon/spoon/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#spring-framework/spring-framework/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#Hbase/Hbase/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#pmd/pmd/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#elasticsearch/elasticsearch/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#lombok-ast/lombok-ast/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#RxJava/RxJava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#java-design-patterns/java-design-patterns/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#MaterialDesignLibrary/MaterialDesignLibrary/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#apache-ant/apache-ant/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#apache-jsecurity/apache-jsecurity/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#android-launcher/android-launcher/' projects-to-test-on.properties
.ci/shippable.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/shippable.sh: sed -i.'' 's/#spring-framework/spring-framework/' projects-to-test-on.properties
.ci/shippable.sh: sed -i.'' 's/#nbia-dcm4che-tools/nbia-dcm4che-tools/' projects-to-test-on.properties
.ci/shippable.sh: sed -i.'' 's/#spotbugs/spotbugs/' projects-to-test-on.properties
.ci/shippable.sh: sed -i.'' 's/#pmd/pmd/' projects-to-test-on.properties
.ci/shippable.sh: sed -i.'' 's/#apache-ant/apache-ant/' projects-to-test-on.properties
Also in sevntu: ➜ sevntu-checks git:(master) ✗ grep -R "projects-to-test-on.properties" | grep -v "groovy"
.ci/wercker.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#hibernate-orm/hibernate-orm/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#spotbugs/spotbugs/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#spring-framework/spring-framework/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#Hbase/Hbase/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#pmd/pmd/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#elasticsearch/elasticsearch/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#lombok-ast/lombok-ast/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/^guava/#guava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#RxJava/RxJava/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#java-design-patterns/java-design-patterns/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#MaterialDesignLibrary/MaterialDesignLibrary/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#apache-ant/apache-ant/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#apache-jsecurity/apache-jsecurity/' projects-to-test-on.properties
.ci/wercker.sh: sed -i.'' 's/#android-launcher/android-launcher/' projects-to-test-on.properties
|
it looks like it is better to create new file that will be specific for github actions. Set of projects in it will be defined by limitation of github-action environment. |
Here is your fixed checkstyle search. Looks like file type is an issue for some reason.
Since everything is being merged into
This way we can merge everything into 1 file and have functionality to run only the projects necessary. I am preferring option 1 because we always tell everyone to run ALL repos and we only really start to exclude repos from running in CI because of timeframe and more exact error reporting. |
If we have no other choice it is fine, but I am just looking at the big picture and trying not to duplicate files for every single unique purpose. We will have to keep remembering to update each one and it won't be obvious to everyone, and eventually we'll forget one. I am not saying this has to come before or after #531 , I was just using it as an example of consolidating and expanding regression. |
This was my thoughts as well; what if we "compromise" and create a CI task that verifies that both files are the same except for |
This is tool, it simply should follow config file provided from outside and stricktly follow it. I still think creation of new file is good. All our old way to do regression should be reconsidered. With GitHub actions + diff.groovy all become a different . We are even have problems of using this config file, we can use some yml instead and even rethink content of it. Current config was created as quick hack to make launch.sh to work ( grandfather of diff.groovy) |
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.
lets use separate file for now to proceed quicker and avoid dependencies to other CIs
617e32b
to
166c661
Compare
@romani done |
166c661
to
7199a5f
Compare
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.
ok to merge
Useful for checkstyle/checkstyle#9258
Left commented out