continuous

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix for changes to validation in test fixture.

    • -7
    • +16
    ./ContinuousIntegrationTestFixtureTest.groovy
  1. … 1 more file in changeset.
Change `AbstractIntegrationSpec` to fail when a test runs a build that fails with more than one exception and does not verify the number of exceptions in the failure using `assertHasFailures()`.

This is to avoid additional exceptions unintentionally being introduced, for example when a failure starts being thrown because of configuration cache problems alongside the expected failure.

    • -7
    • +16
    ./ContinuousIntegrationTestFixtureTest.groovy
  1. … 81 more files in changeset.
Change `AbstractIntegrationSpec` to fail when a test runs a build that fails with more than one exception and does not verify the number of exceptions in the failure using `assertHasFailures()`.

This is to avoid additional exceptions unintentionally being introduced, for example when a failure starts being thrown because of configuration cache problems alongside the expected failure.

    • -7
    • +16
    ./ContinuousIntegrationTestFixtureTest.groovy
  1. … 11 more files in changeset.
Change `AbstractIntegrationSpec` to fail when a test runs a build that fails with more than one exception and does not verify the number of exceptions in the failure using `assertHasFailures()`.

This is to avoid additional exceptions unintentionally being introduced, for example when a failure starts being thrown because of configuration cache problems alongside the expected failure.

    • -7
    • +16
    ./ContinuousIntegrationTestFixtureTest.groovy
  1. … 11 more files in changeset.
Change `AbstractIntegrationSpec` to fail when a test runs a build that fails with more than one exception and does not verify the number of exceptions in the failure using `assertHasFailures()`.

This is to avoid additional exceptions unintentionally being introduced, for example when a failure starts being thrown because of configuration cache problems alongside the expected failure.

    • -7
    • +16
    ./ContinuousIntegrationTestFixtureTest.groovy
  1. … 11 more files in changeset.
Change `AbstractIntegrationSpec` to fail when a test runs a build that fails with more than one exception and does not verify the number of exceptions in the failure using `assertHasFailures()`.

This is to avoid additional exceptions unintentionally being introduced, for example when a failure starts being thrown because of configuration cache problems alongside the expected failure.

    • -7
    • +16
    ./ContinuousIntegrationTestFixtureTest.groovy
  1. … 81 more files in changeset.
Change `AbstractIntegrationSpec` to fail when a test runs a build that fails with more than one exception and does not verify the number of exceptions in the failure using `assertHasFailures()`.

This is to avoid additional exceptions unintentionally being introduced, for example when a failure starts being thrown because of configuration cache problems alongside the expected failure.

    • -7
    • +16
    ./ContinuousIntegrationTestFixtureTest.groovy
  1. … 81 more files in changeset.
Remove parallel and continuous incubation messages

    • -4
    • +0
    ./ContinuousIntegrationTestFixtureTest.groovy
  1. … 5 more files in changeset.
IDs are advertised for [build invocation, workspace, user] to allow cross referencing invocations and linking invocations of the same user and workspace (#1963)

This commit also adds TaskStateInternal.getOriginBuildId() that advertises the ID of the build that produced the outputs that will be reused for the UP_TO_DATE and FROM_CACHE outcomes.

    • -0
    • +1
    ./ContinuousIntegrationTestFixtureTest.groovy
  1. … 68 more files in changeset.
Report task outcome statistics after build finishes

This changes the format of the Build Result to have consistent

duration display to the console.

- Move TerseDurationFormatter and reuse it for BuildResultLogger.

Inject a DurationFormatter into the BuildResultLogger with a

concrete TersePrettyDurationFormatter impl.

- Remove cache stats reporting

- Fix tests that scrape build result message

Issue: #1639

    • -13
    • +5
    ./ContinuousIntegrationTestFixtureTest.groovy
  1. … 37 more files in changeset.
Fix test failure on IBM Java 6

+review REVIEW-5855

    • -1
    • +1
    ./ContinuousIntegrationTestFixtureTest.groovy
Fix output parsing in AbstractContinuousIntegrationTest

- parsing of multiple results caused test failures when there

was output after a "Waiting for changes to input files of tasks..."

line.

- this cause flaky test failures because Play integ tests some times

log "[info] play - Listening for HTTP on /0:0:0:0:0:0:0:0:XXXXX"

after the waiting for changes line.

+review REVIEW-5855

    • -0
    • +134
    ./ContinuousIntegrationTestFixtureTest.groovy
  1. … 1 more file in changeset.
remove ContinuousModeParameters and move flag to StartParameters - simplifies parameter handling in Tooling API provider

+review REVIEW-5509

    • -35
    • +0
    ./ContinuousModeParametersTest.groovy
  1. … 11 more files in changeset.
Simplify implementation of triggering a build in continuous mode.

Removes the formal 'trigger' abstraction, replacing with lower level primitives directly the build action executer. The primary benefit here is fewer moving parts and types.

As invoking the listening is now done at the end of the build execution loop instead of via a build listener, the task inputs accumulator had to be elevated to global scope. This is something to be addressed in forthcoming commits.

+review REVIEW-5481

  1. … 10 more files in changeset.
Add a test for BlockingTriggerable

+review REVIEW-5492

    • -0
    • +38
    ./BlockingTriggerableTest.groovy
  1. … 2 more files in changeset.
Continuous Mode: Only watch files for tasks that are in the task execution plan

- Simplify "trigger" mechanism

- got rid of all of the TriggerGenerator/TriggerGeneratorFactory classes

- ContinuousModeBuildActionExecutor waits on a "triggerable"

- BlockingTriggerable waits for a message as a TriggerListener

- TaskInputsWatcher registers a BuildListener to keep a list of tasks that will be executed

- on buildFinished, we convert each Task's inputs to a FileCollection and start a file watcher

- on file change, we trigger the TriggerListeners

+review REVIEW-5492

    • -38
    • +0
    ./DefaultTriggerGeneratorFactoryTest.groovy
    • -41
    • +0
    ./DefaultTriggerGeneratorTest.groovy
  1. … 15 more files in changeset.
Add some file watch listener building blocks, and use them to process events.

This change also shuts down the watching between builds.

+review REVIEW-5466

  1. … 6 more files in changeset.
Make FileWatcherEvent a sealed type and prevent illegal states.

+review REVIEW-5466

  1. … 5 more files in changeset.
Refactor file watcher

+review REVIEW-5466

  1. … 34 more files in changeset.
remove features from file watching solution - don't prepare for Windows file tree watching mode - don't track source of files to watch for - don't implement reuse of file watches

+review REVIEW-5466

  1. … 18 more files in changeset.
introduce FileWatcherListener and remove quiet period logic

+review REVIEW-5466

  1. … 16 more files in changeset.
refactor file watcher to support reusing watches and continuous watching

+review REVIEW-5466

    • -2
    • +6
    ./DefaultTriggerGeneratorFactoryTest.groovy
  1. … 24 more files in changeset.
Use CyclicBarrierHttpServer for triggering builds in continuous mode

+review REVIEW-5459

    • -2
    • +3
    ./DefaultTriggerGeneratorFactoryTest.groovy
  1. … 13 more files in changeset.
Add some continuous mode tests

+review REVIEW-5459

    • -0
    • +33
    ./DefaultTriggerGeneratorFactoryTest.groovy
    • -0
    • +46
    ./FileWatchStrategyTest.groovy
  1. … 9 more files in changeset.
Rename Trigger behaviors to trigger strategies

+review REVIEW-5459

  1. … 8 more files in changeset.
Add trigger infrastructure

- TriggerGeneratorFactory to create TriggerGenerator's

- TriggerGenerator to create TriggerDetails based on something

- TriggerListener to receive TriggerDetails when a trigger is tripped

- Implementation is the same as the dumb timer in

ContinuousModeBuildActionExecuter (5 second timer)

- Catching all Throwables right now to keep the loop alive

+review REVIEW-5459

    • -0
    • +27
    ./DefaultTriggerDetailsTest.groovy
    • -0
    • +41
    ./DefaultTriggerGeneratorTest.groovy
  1. … 15 more files in changeset.
Wire "watch mode" command line options into build executer

- Rename watch mode to continuous mode

- Still using --watch for command line right now

- Build executer for continuous mode just keeps building without any

external triggers right now (5 seconds after last build)

- Extract command line parsing into separate converter (so integ tests can

use it) - TBD

- Put all of the "Parameter" objects into a Parameters holder

- No integ tests yet

    • -0
    • +35
    ./ContinuousModeParametersTest.groovy
  1. … 23 more files in changeset.