Some good ideas... thanks for the replies!
On Wednesday, 25 March 2015 13:28:08 UTC, Aidan Semple wrote:
>
> I'm running Jenkins 1.600 and am currently setting up a new project with
> rather a long command to put in to one of the Execute Shell text boxes.
> Unfortunately the command is so long it
Although I know it's not the same thing, you could build up a string
variable containing pieces of the command and then run that. You should
also upgrade to 1.601 because there are some known issues with 1.600.
cmdline="blah ddd xxx etc etc etc"
cmdline="${cmdline} more command and args et
I'd like to see this functionality come back as well.
On Wednesday, March 25, 2015 at 8:28:08 AM UTC-5, Aidan Semple wrote:
>
> I'm running Jenkins 1.600 and am currently setting up a new project with
> rather a long command to put in to one of the Execute Shell text boxes.
> Unfortunately the co
This might be a silly idea, but why don't you check the script file with
this command execute into SCM and then just run the script file in your
execute shell text box? (That means you can see the history of changes
easier... and when building older branches/pull requests you have the
correct comma
I'm running Jenkins 1.600 and am currently setting up a new project with
rather a long command to put in to one of the Execute Shell text boxes.
Unfortunately the command is so long it extends the width of the text box
considerably messing up the display of the project in my browser so it is
har
