Improve human-readability of jobs on Jenkins' side
Bug #760784 reported by
Paul Sokolovsky
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro Android Frontend |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
Currently, backend passes build config to Jenkins in base64 encoded form. Unless there're security concerns, it would make sense to make it more discernible on Jenkins side, by using for example urlencoding (%xx).
Caveat: command-line encoder/decoder availability - base64 util is used now, but we always could use Python.
Changed in linaro-android-build-tools: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
summary: |
- Consider using more human-readable format to pass build config to - Jenkins + Improve human-readability of jobs on Jenkins' side |
Changed in linaro-android-build-tools: | |
importance: | Medium → Low |
importance: | Low → Wishlist |
affects: | linaro-android-build-tools → linaro-android-frontend |
To post a comment you must log in.
The main constraint here is that the encoded form can't contain newlines, because jenkins squashes them in the config xml. url encoding is probably less opaque than base64 though, I'll grant :)