|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I ran into a similar issue at my employer yesterday. For us, saving job configurations failed with a "connection reset" when I had a Groovy command embedded in the configuration that used "&&". The root cause ended up being an Intrusion Prevention System that our networking team had set up which was blocking the traffic. For us, at least, the problem wasn't with Jenkins at all.