Releases: JobService/job-service
v3.2.2
Version Number
3.2.2-697
New Features
- None
Bug Fixes
- SCMOD-9193: Add SQL failover handling
During an SQL failover event the Worker Job Tracking project has been updated to treat SQL failures as transient issues so that tasks are retried and not thrown away as fatal failures.
Known Issues
- None
v3.2.1
Version Number
3.2.1-691
New Features
- None
Bug fixes
- Fix for broken documentation site.
Known Issues
- None
v3.2.0
Version Number
3.2.0-689
New Features
- SCMOD-8513: Labels
Extra key-value pair metadata can be associated with new jobs.
Replaces externalData field which has been deprecated. - SCMOD-7632: Updated to meet logging standard mentioned in caf-logging
- SCMOD-5777: Set postgres database connection application name
- SCMOD-8520: Updated to use security hardened base images
Bug Fixes
- SCMOD-8609: Fixed export documents failure.
Known Issues
- None
v3.1.0
Version Number
3.1.0-578
New Features
- SCMOD-6955: Job types
Job types can be defined, and new jobs can target a type to use a well-defined, type-specific input format. - SCMOD-7309: NotFinished job status filter
The statusType parameter accepts a new value, which includes only jobs which haven't reached a final state. - SCMOD-7308: Job list sorting
The sort parameter has been added to the jobsGet API.
Bug fixes
- SCMOD-7065: Fixed HTTP status for parallel duplicate job creation
- SCMOD-7143: Fixed WorkerCallback update for TaskInformation
- SCMOD-7336: Job-Tracking failure fixed during Postgres failover
Known Issues
- None
v3.0.0
Version Number
3.0.0-471
Breaking Changes
- All API requests must provide a partition ID in the request path.
New Features
- SCMOD-6622: Job partitions
Jobs are organised into partitions, which provide isolation between groups of jobs.
Bug Fixes
- SCMOD-6620: Deadlock creating a job
It was previously possible for a deadlock to occur when creating a job, or when a job completed.
Known Issues
- None
v2.7.0
Version Number
2.7.0-440
Version Number
${version-number}
New Features
-
SCMOD-6182: Last Updated Time field
When retrieving the status of a job a newlastUpdateTimefield is returned which provides the last time any activity happened on the job, such as when it was last progressed or completed. -
SCMOD-5725: Kubernetes Quick Start
A Quick Start guide has been added for using the Job Service with Kubernetes. -
Prerequisite jobs pre-created declaration
Previously when a job was created with a prerequisite, and that prerequisite job was not found in the system, then it was assumed that the job was yet to be created. This remains the default behavior, but now an options string can be specified as a suffix with the prerequisite jobs ids, and if one of the options is ",pc" (i.e. precreated), then if the job is not found then instead of assuming that it is yet to be created the assumption will be that it was previously created, has completed successfully, and has been deleted. This means that the prerequisite can be effectively ignored.
Bug Fixes
-
SCMOD-6216: Prerequisite jobs could be ignored
Previously a job which had multiple prerequisite jobs might have been erroneously started before all of the prerequisite jobs had been completed. In particular this could happen if some of the prerequisite jobs had not yet been created. This has been corrected. -
Specified delay could be ignored
Previously if a delay was specified then it was ignored if there were no prerequisite jobs or if they were already complete. This has been corrected.
Deprecated Features
-
SCMOD-4883: Pre-installed PostgreSQL Docker Image
Previous versions contained a PostgreSQL Docker Image which had the Job Service pre-installed. This of course was never useful for production but was useful for testing. It is not available for this release. It may or may not be re-introduced in the future. -
SCMOD-5725: Docker Compose Quick Start
The Docker Compose Quick Start guide has been removed. The Job Service can of course still be used with Docker Compose and this is still supported. The Docker Compose Quick Start guide may be re-introduced in the future.
Known Issues
- None
v2.6.0
Version Number
2.6.0-383
New Features
- SCMOD-4658: Database jobservice is created or upgraded when the container
starts up - Alternative Java client that uses Jersey 2.x libraries added
Bug Fixes
- SCMOD-4348: Jobs were not getting updated due to database lock (Deadlocks)
Known Issues
- None
v2.5.0
Version Number
2.5.0-284
New Features
- SCMOD-3285: Job Service container has been updated to deploy job service api onto Tomcat9.
- SCMOD-3525: Job Service updated to support async job status updates
Job Service Updated to support Tracking Report messages that are dispatched by the worker framework to update the status of a job. - SCMOD-3376: Use environment variables to configure job tracking worker.
Known Issues
v2.4.0
Version Number
2.4.0-211
New Features
-
CAF-3881: Clean tables up as early as possible
The Job Service has been changed to clean up the dynamic task tables in the database when all subtasks belonging to that task have been completed. Previously the tables were cleaned up only when the entire job was completed. -
CAF-3893: Job Tracking Worker logging
Job Tracking Worker logging is now controllable via theCAF_LOG_LEVELenvironment variable. -
CAF-3904: Errors reporting progress
The Job Tracking Worker has been changed to support a catch and retry mechanism in the event of a database concurrency related exception being detected. -
CAF-3920: Health check exposed on separate port
The Job Service has been updated to expose a/healthcheckendpoint which can be used by Docker or the container orchestrator. This endpoint is exposed on a separate port from the service's main operations.
Known Issues
- None
Changes
- The complete list of changes is available here.
v2.3.0
Version Number
2.3.0-159
New Features
- Support added for dependent jobs. The Job Service can now accept a job and a list of dependent jobs. The Job Service
causes the job to wait until all dependent jobs have completed before automatically executing the job. - CAF-2349: Health check added for job tracking worker.
- CAF-3656: Liquibase database installation and upgrade changes.
- CAF-3736: Enable multi-process logging
All processes running inside the container now output their log entries to the standard output streams, which can be accessed using thedocker container logscommand.
Known Issues
- None