Title | We don't explain which jobspecs won't work |
Status | closed |
Priority | optional |
Assigned user | Richard Brooksby |
Organization | Ravenbrook |
Description | "p4 -G job -o" applies much more stringent tests than "p4 job -o". It won't even give you a form unless all the values are correct. This means that tricks like ones in Perforce's jobspec, where an illegal value like "setme" is specified as the default value for a select field, can't be used with the integration. |
Analysis | Work out which jobspecs won't work and explain why not in the AG. Even better, check automatically by trying a "p4 -G job -o" early on and throwing an error referring to some documentation. We're generating the jobspec, so this isn't an issue except for advanced configuration, which we may not support. Re-open this job if we decide to. RB 2000-11-30 |
How found | manual_test |
Evidence | <http://www.ravenbrook.com/project/p4dti/doc/2000-10-26/perforce-alpha-test/ > item 6 |
Observed in | 0.3.2 |
Created by | Richard Brooksby |
Created on | 2000-11-22 14:45:43 |
Last modified by | Gareth Rees |
Last modified on | 2001-12-10 19:03:00 |
History | 2000-11-22 RB Created from sources (see evidence). 2000-11-30 RB Suspended (see analysis). 2001-03-20 RB Downgraded to "optional" (see analysis). |
Change | Effect | Date | User | Description |
---|---|---|---|---|
10413 | closed | 2001-03-22 12:01:07 | Gareth Rees | In the Integrator's Guide, gave warning about incompatible jobspecs. |
5101 | suspended | 2000-11-29 14:50:12 | Gareth Rees | Merged automatic configuration from branch/2000-11-28/auto-config into master sources. |