Reason for change

This release fixes a couple serious bugs in the pipeline web front-end and pipeline client. In addition it fixes some performance problems, brings the pipeline software into compliance with SLAC security policy regarding use of oracle passwords, and fixes some minor issues identified during OpsSim2.

Test Procedure

The new software has been in use on the TEST server for over a week, and has undergone extensive stress testing (as part of the preparation for the new oracle database). The web front-end has been in DEV for over a week, and has been tested by Tom Glanzman among others. The pipeline server and client have been in DEV for 4 days and have been tested by the pipeline developers and others.

Rollback procedure

Any of these changes can quickly and easily be backed out should unanticipated problems appear when the code is moved to production.

Related JIRA

SSC-10@JIRA

Pipeline Front-End 2.5.1

The following fixes have been applied in 2.5.1. Note the PFE-159 is a critical bug that was introduced accidentally in release 2.5.0 as needs to be fixed quickly. This release has been in DEV at http://glast-tomcat03.slac.stanford.edu:8080/Pipeline-II for several days. In the event any problems are found after this release has been moved to PROD it is easy to reinstall 2.5.0.

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Pipeline Server 1.0.1

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Pipeline Client 1.0.2

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.