- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 10 for Masing (0.18 sec)
-
.cm/platform_labels.cm
{% endfor %} # To simplify the automations section, some calculations are placed under unique YAML keys defined here. # Read the "|" not as "or", but as a "pipe", taking the output of the previous command and passing it to the next command. # TODO: It would be very nice to avoid having this list somehow, but it needs to be defined in YAML and not in JS for the looping template to work
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Mon Apr 22 15:32:31 GMT 2024 - 2.5K bytes - Viewed (0) -
.cm/summary_table.cm
- 'platforms/core-execution/build-cache-packaging/' - 'platforms/core-runtime/build-operations/' - 'platforms/core-runtime/files/' - 'platforms/core-execution/hashing/' - 'platforms/core-execution/snapshots/' - build_infrastructure: name: 'build_infrastructure' subprojects: - '.teamcity/' - '.github/' - '/build-logic/'
Plain Text - Registered: Wed Apr 17 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 6.5K bytes - Viewed (0) -
.teamcity/subprojects.json
"name": "functional", "path": "platforms/core-runtime/functional", "unitTests": true, "functionalTests": false, "crossVersionTests": false }, { "name": "hashing", "path": "platforms/core-execution/hashing", "unitTests": true, "functionalTests": false, "crossVersionTests": false }, { "name": "ide", "path": "platforms/ide/ide", "unitTests": true,
Json - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Apr 16 15:50:57 GMT 2024 - 26.8K bytes - Viewed (0) -
.github/PULL_REQUEST_TEMPLATE.md
- [ ] Provide unit tests (under `<subproject>/src/test`) to verify logic. - [ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes. - [ ] Ensure that tests pass sanity check: `./gradlew sanityCheck`. - [ ] Ensure that tests pass locally: `./gradlew <changed-subproject>:quickTest`. ### Reviewing cheatsheet
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Feb 13 22:36:19 GMT 2024 - 1.7K bytes - Viewed (0) -
architecture-standards/0002-avoid-using-java-serialization.md
- **Flexibility and Control:** Java serialization offers limited control over the serialization process, such as excluding certain fields, customizing naming conventions, and handling complex data structures more gracefully. - **Security:** Java serialization poses security risks, especially related to deserialization vulnerabilities.
Plain Text - Registered: Wed Feb 14 11:36:15 GMT 2024 - Last Modified: Thu Feb 08 21:48:27 GMT 2024 - 1.9K bytes - Viewed (0) -
.teamcity/src/main/kotlin/util/WarmupEc2Agent.kt
vcs.useAbsoluteVcs(VersionedSettingsBranch.fromDslContext().vcsRootId()) features { freeDiskSpace { // Lower the limit such that the agent work directories aren't cleaned during the AMI baking process requiredSpace = "100mb" } } params { param("defaultBranchName", "master") param("env.JAVA_HOME", javaHome(BuildToolBuildJvm, Os.LINUX)) }
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Dec 05 00:08:14 GMT 2023 - 1.2K bytes - Viewed (0) -
CONTRIBUTING.md
## Making your change ### Code change guidelines All code contributions should contain the following: * Create unit tests using [Spock](https://spockframework.org/spock/docs/2.0/index.html) for new classes or methods that you introduce.
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Feb 09 15:30:53 GMT 2024 - 15.6K bytes - Viewed (0) -
architecture-standards/0001-use-architectural-decision-records.md
The main logic with ADRs is to describe (architectural) decisions made: * To provide best practices and solutions we (as *build tool* team) want to promote. * To avoid asking the same thing multiple times during code review. * To explain *rejected solutions*, for now and future development, in case they are proposed again. ADRs can be written by any team.
Plain Text - Registered: Wed Feb 14 11:36:15 GMT 2024 - Last Modified: Wed Feb 07 00:43:19 GMT 2024 - 2.8K bytes - Viewed (0) -
architecture/standards/0001-use-architectural-decision-records.md
The main logic with ADRs is to describe (architectural) decisions made: * To provide best practices and solutions we (as the *build tool* team) want to promote. * To avoid asking the same thing multiple times during code review. * To explain *rejected solutions*, for now, and future development, in case they are proposed again. ADRs can be written by any team.
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Sat Mar 02 21:54:40 GMT 2024 - 2.8K bytes - Viewed (0) -
architecture/standards/0002-avoid-using-java-serialization.md
- **Flexibility and Control:** Java serialization offers limited control over the serialization process, such as excluding certain fields, customizing naming conventions, and handling complex data structures more gracefully. - **Security:** Java serialization poses security risks, especially related to deserialization vulnerabilities. - **Version Compatibility:**
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Thu Feb 29 22:32:18 GMT 2024 - 2.3K bytes - Viewed (0)