Cannot change width of Execute shell text box on configure page for a project

62 views
Skip to first unread message

Aidan Semple

unread,
Mar 25, 2015, 9:28:08 AM3/25/15
to jenkins...@googlegroups.com
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 harder to read. This happens in IE, Chrome and Firefox. I am not able to shrink the width of the text box (only the height).

However in Jenkins 1.544 I could change the width and the command would wrap accordingly. Well this was using firefox but does not work in IE or chrome.
Any ideas on what I need to do to fix this? It could be browser related or even Jenkins, but would be grateful for any tips.
Thanks in advance
Aidan

Stephen Connolly

unread,
Mar 25, 2015, 10:31:04 AM3/25/15
to jenkins...@googlegroups.com
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 command for that branch)

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b2548396-ba83-4110-8c10-943394290201%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Bryan Adams

unread,
Mar 25, 2015, 11:24:09 AM3/25/15
to jenkins...@googlegroups.com
I'd like to see this functionality come back as well.

Eric Pyle

unread,
Mar 25, 2015, 11:33:11 AM3/25/15
to jenkins...@googlegroups.com
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 ssss xxx etc etc etc"
cmdline="${cmdline} more command and args etc"
$cmdline

Eric
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

Aidan Semple

unread,
Mar 26, 2015, 8:58:04 AM3/26/15
to jenkins...@googlegroups.com
Some good ideas... thanks for the replies!
Reply all
Reply to author
Forward
0 new messages