resolves TASK-782
Updated PR to resolve issue when no task tables exist
Updated PR based on review comments.
This does not include updated tests.
This resolves a problem where task would fail because the incrementer selection occured before the tables were created.
Added unit test for SqlServerSequenceIncrementer
updated based on code review
This commit now validates that the value passed via a PageRequest to
sort the results by is a valid value.
Resolves#739
Fixed to allow for all letter cases
Ensure that Task's org.springframework.cloud.task.configurationorg.springframework.cloud.task.configuration.MetricsAutoConfiguration is configured Before org.springframework.boot.actuate.autoconfigure.metrics.MetricsAutoConfiguration (that in turn is configured Before the CompositeMeterRegistryAutoConfiguration).
Resolves#691
Before this commit, Spring Cloud Task did not correctly configure the
provided PlatformTransactionManager with the TaskRepository. This
commit addressis this bug.
Resolves#652
Polished PR on Merge
In short the Oracle CHAR type is blank padded to the end of the field. So we were not getting an exact match on queries when looking for the LOCK_KEY or CLIENT_ID
- New dependencies
- micrometer-core
- java-cfenv - required by the CF tags configuration.
- Add TaskMetrics configuration that installs two Meters (Timer and LongTaskTimer) that produce the following time-series:
- spring.cloud.task - shows task duration (updated only after the task has completed).
- spring.cloud.task.active - provides run time information about the non-completed tasks.
Both meters are started at TaskExecutionListener#onTaskStartup() and ended at onTaskEnd() or onTaskFailure().
- Add common Task tags assigned to all time-series produced by the Task (not only the s.c.task and s.c.task.active). This allows to analyze CPU, Memory and other measurements grouped by task/execution ids.
- Add Cloud Found tags - Activated only for CF target platform.
Resolves#608
Updated to spring-cloud-build 2.2.0.BUILD-SNAPSHOT
Updated Tests to support the changes in the latest H2 database
Must use "-ifNotExists", when using the H2 TCP Server
- Deployer core/local uses 2.0.0.BUILD-SNAPSHOT
- Use pring-cloud-deployer-dependencies bom
- Remove ResourceLoadingAutoConfiguration as that is now in
deployer itself with a way to configure loaders.
- spring-cloud-task-core now depends on spring-cloud-deployer-autoconfigure.
- Rest of deployer modules like support/maven are still defined in deps
as those are optional in spring-cloud-deployer-autoconfigure.
- Make exit code nullable and only update of execution status can make it a valid integer
- Update JDBC create/start task execution queries to have exitCode as `null` values
- Update tests to validate/verify the appropirate exit code values for create/start/complete task executions
On merge had to add a pause to the TaskLauncherSinkTests to wait for the task to complete successfully Before we assumed that 0 was a satisfactory result meaning it was either running or completed. Now with the null being returned it could be zero or null. So we have to wait for the task to complete.
All version changes are present.
Fixed all Java-Doc Errors and warnings
* Due to the stricter nature of the javadoc compiler we can't wrap <ul> / <ui> in <p>
* We will also need to Push up a test app for taklauncher to work with. The old one fails to start now. Or use one of the task starters possibly.
* Built on the work from TASK-439C. Wait for that merge before merging this one.
* Replaced applicationFailedEvent class attribute with applicaitonFailedException
* Also polished the app used by the taskLauncherSink integration test
Migrating to use ApplicationContextRunner or ImportAutoConfiguration with SpringApp.run, instead of SpringApplicationBuilder, because builder does not handle AutoConfiguration properly
SimpleTaskAutoConfiguration now has an annotation AutoConfigureBefore the BatchTaskAutoConfig so that it is processed prior. THis is so that that BatchTaskAutoConfig can create the appropriate beans
SimpleTaskAutoConfiguration has new annotations so that it is AutoConfigured after BindingServiceConfiguration and after SimpleTaskAutoConfiguration. This is so that it does not attempt to start emitting messages before stream is ready and it can create the appropriate beans after SimpleTaskAutoConfiguration has run.
Renamed SimpleTaskConfiguration to SimpleTaskAutoConfiguration.
Task version updated to 2.1.0
Added missing headers
Updated documentation.
Deprecated EnableTask
Added ability to disable Task autoconfiguration.
Removed @EnableTask from tests
Resolves#439Resolves#440Resolves#448Resolves#466
- Add the ability to retrieve the last TaskExecution to:
- MapTaskExecutionDao
- JdbcTaskExecutionDao
- Refactor `JdbcTaskExecutionDao` and use `NamedParameterJdbcTemplate` for all persistence store calls
- Add the following TaskExecution methods to TaskExplorer:
- getLatestTaskExecutionsByTaskNames
- getLatestTaskExecutionForTaskName
- Add Tests
- Ensure that code is JDK7 compatible due to backporting needs
- Ensure commit backports to 1.2.x
Polishing on tests during merge
If a user adds spring-cloud-starter-config to the dependencies it has to add a proxy for the datasource else the Hikari connection pool pukes.
resolves#407
