problem with URL trigger since jenkins migration
Bug #1329523 reported by
Fathi Boudra
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro CI |
Triaged
|
Low
|
Fathi Boudra |
Bug Description
In trying to trigger my kbuilder job using the URL trigger, I noticed that this is now failing since the Jenkins upgrade. Since it's
passing a URL as an argument, all of the special characters are escaped, but Jenkins used to unpack this back into a format that could be used in commands.
For example, see the TREE parameter here:
https:/
Jenkins used to decode this automatically, but it's not anymore, which results in the get fetch commands that use that URL failing.
Changed in linaro-ci: | |
status: | New → Confirmed |
assignee: | nobody → Paul Sokolovsky (pfalcon) |
Changed in linaro-ci: | |
importance: | Undecided → High |
status: | Confirmed → Triaged |
Changed in linaro-ci: | |
assignee: | Paul Sokolovsky (pfalcon) → Fathi Boudra (fboudra) |
importance: | High → Low |
To post a comment you must log in.
FYI... I'm working around this in the job by manually decoding the URL from the $TREE input variable.
TREE=`python -c "import urllib, sys; print urllib. unquote( sys.argv[ 1])" $TREE`