Details
-
Bug
-
Resolution: Fixed
-
Medium
-
4.2 M3
-
None
-
None
Description
This was observed on BEAC in these builds:
- https://bamboo.extranet.atlassian.com/browse/JSTS-TALCNIGHTLY1-12
- https://bamboo.extranet.atlassian.com/browse/JSTS-ODCJ0-2
In both cases, new jobs in the plan were created by cloning an existing job, then modifying and saving it. Then, a branch build was executed. In that build, all changes made after cloning were ignored: the tasks in cloned jobs ran exactly as the original tasks from which they were cloned, ignoring any (saved) modifications to the plan made after cloning.
For example, see the following log files:
- https://bamboo.extranet.atlassian.com/download/JSTS-ODCJ0-BUNDLEDPLUGINSN/build_logs/JSTS-ODCJ0-BUNDLEDPLUGINSN-2.log
- https://bamboo.extranet.atlassian.com/download/JSTS-ODCJ0-JOB1/build_logs/JSTS-ODCJ0-JOB1-2.log
Both logs refer to test suite -Dtestng.suite=src/test/resources/testng-bundledplugins.xml. This is the suite of the original job (JSTS-ODCJ-BUNDLEDPLUGINSN). Yet, job JSTS-ODCJ-JOB1 (which was cloned from JSTS-ODCJ-BUNDLEDPLUGINSN) had been modified to use suite -Dtestng.suite=src/test/resources/testng-group1.xml:
That change was ignored in the build, so the jobs both ran the same suite.
Attachments
Issue Links
- copied to
-
BDEV-1142 Loading...