CBD-26
Suspended
Fix ticket issues: Do 'p4 login' if necessary.
Presently, the CBD automation presumes it has a valid ticket. Add a
'p4 login -s' ticket status check, and if it fails, attempt a 'p4 login'
using credentails available via a mechanism similer to that used by
the SDP to ensure checkpoints run reliably.
This check needs to be added to BOTH the update trigger and the broker
filter script.
This change will increase the coupling betweeen CBD and the SDP, which
has been kept to a minimum thus far. That's acceptable.
Presently, the CBD automation presumes it has a valid ticket. Add a
'p4 login -s' ticket status check, and if it fails, attempt a 'p4 login'
using credentails available via a mechanism similer to that used by
the SDP to ensure checkpoints run reliably.
This check needs to be added to BOTH the update trigger and the broker
filter script.
This change will increase the coupling betweeen CBD and the SDP, which
has been kept to a minimum thus far. That's acceptable.
- Status
- Suspended
- Project
- perforce-software-cbd
- Severity
- B
- Reported By
- C. Thomas Tyler
- Reported Date
- 8 years ago
- Modified By
- C. Thomas Tyler
- Modified Date
- 8 years ago
- Owned By
- tom_tyler
- Dev Notes
- Suspended this job on 2015/06/25.
This would make CBD more robust,
but a reason to avoid fixing this is that having broken tickets on
the server is a bigger problem, and 'fixing' this for CBD would mask
the root cause. Tickets on a server should be completely reliable
to benefit all automation on the Helix server, with CBD triggers and
broker filter scripts just being one example.
A counter point: CBD automation is used almost constantly, so even
if is viewed as a workaround to some unrelated problem with tickets
being broken on the server, it's probably going to be an effective
workaround. - Type
- Feature
Log in to comment