-
Task
-
Resolution: Unresolved
-
Minor
-
None
Support for this input type is unplanned
If you need support for this Input type please vote for this ticket and leave a comment explaining your use case with an example.
In Scope
- Support the "file" input parameter type
[JENKINS-40395] Support for file input parameter type
Epic Link | New: JENKINS-38490 [ 174672 ] |
Description |
Original:
In Scope * Support the "file" input parameter type |
New:
{panel:title=Support for this input type is unplanned} If you need support for this Input type please vote for this ticket and leave a comment explaining your use case with an example. {panel} In Scope * Support the "file" input parameter type |
Resolution | New: Won't Do [ 10001 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Won't Do [ 10001 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Resolution | New: Postponed [ 6 ] | |
Status | Original: Reopened [ 4 ] | New: Resolved [ 5 ] |
Resolution | Original: Postponed [ 6 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
blue-ocean: 1.1.7
This error occurs when trying to use declarative pipeline for a file parameter.
"This pipeline uses input types that are unsupported. Use Jenkins Classic to resolve parametrized build."
Could support for file be added?
parameters {
choice(name: 'Environment', choices: 'DEV\nQA\nSTAGE\nPROD', description: 'Which environment to import to.')
file(name: 'import.json', description: 'The file to import.')
}