aboutsummaryrefslogtreecommitdiffhomepage
path: root/scripts/ij.bazelproject
Commit message (Collapse)AuthorAge
* [Skylint] Do not crash ControlFlowChecker on nested functions.Gravatar Taras Tsugrii2018-02-13
| | | | | | | | | | | ControlFlowChecker has a precondition check that assumes nested functions do not occur. While this assumption is reasonable for a valid Skylark syntax, linter can actually be invoked on malformed files and users would get a stack trace instead of a human-readable linter error. Alternative and possibly a better strategy would to not run CFChecker in case parse errors are detected. fixes #4511 Closes #4512. PiperOrigin-RevId: 185538897
* Remove Bazel's Docker tests.Gravatar Philipp Wollermann2018-01-24
| | | | | | | | | | | | | | We'll just replace them with either native support for running tests inside Docker containers on CI or with VMs running the operating system. This gets rid of the "let's download 8 GB of Docker images" step when running `bazel build //...`. RELNOTES: None. Closes #4506. PiperOrigin-RevId: 183078052
* Fix broken target in Intellij project definition.Gravatar buchgr2017-12-13
| | | | | RELNOTES: None. PiperOrigin-RevId: 178892596
* Moving the RemoteWorker into tools/remote directory.Gravatar olaola2017-12-05
| | | | | | | | This is because I want to add another remote execution related tool, the remote_client, which will use the Remote Execution API to fetch blobs from a remote cache. I will use this tool as part of end-to-end tests for remote execution. TESTED=remote integration tests, presubmit RELNOTES: None PiperOrigin-RevId: 177995895
* Have intellij ignore docker tests.Gravatar John Cater2017-09-08
| | | | | Change-Id: Iabc89286a10dd4d3314f3480f87ac74b34aee969 PiperOrigin-RevId: 167855167
* Remove non-existent target from IntelliJ config.Gravatar John Cater2017-08-10
| | | | | Change-Id: Id31ff0fcf72388fe1e5697b57e67385c6c27824b PiperOrigin-RevId: 164720069
* Add more of our common targets to the IJWB project file.Gravatar Philipp Wollermann2017-07-19
| | | | | | | | | | | | This will make it easier to work on Bazel's core tools like buildjar, singlejar and the JUnit test runner. Also correctly mark their tests as test code in the project. RELNOTES: None. Change-Id: Id79810b4c78b73d92b9c01b1d33f77b7504eab3d PiperOrigin-RevId: 162472964
* Bazel moved to Java 8.Gravatar philwo2017-06-29
| | | | | | Happy dance \o/ PiperOrigin-RevId: 160412092
* Include all directories in ij.bazelproject.Gravatar Philipp Wollermann2017-06-22
| | | | | | | | Without this change you can't work on any code that's not in src/{main,test} in IntelliJ, e.g. tools like the remote_worker. Closes #3224. PiperOrigin-RevId: 159812248
* Add a basic ij.bazelproject file for developing Bazel with IntelliJ.Gravatar John Cater2016-12-12
-- Change-Id: Iedbdf32a80e0a4390ff8084a67eba191f544517f Reviewed-on: https://cr.bazel.build/7770 PiperOrigin-RevId: 141771456 MOS_MIGRATED_REVID=141771456