Supply a unique jenkins trigger auth token per project
Bug #1228403 reported by
Francis Ginther
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cupstream2distro Configuration |
New
|
High
|
Unassigned | ||
Bug Description
Ran into a situation where jenkins triggered multiple jobs from a single trigger request:
https:/
If this is a jenkins bug, we need to workaround it. A possible solution is to use a unique authorization token per set of jobs (that jenkins-
So far, I've only seen this once.
To post a comment you must log in.
