-
Notifications
You must be signed in to change notification settings - Fork 343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JENKINS-69658] Move internal script
block in "failed-test.jelly" to external file
#439
[JENKINS-69658] Move internal script
block in "failed-test.jelly" to external file
#439
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the test failures show this isn't working
The error says: There is still a path issue. I will read about Jelly, add a path in Jelly, and try again. |
This tutorial here: Do not explain I did find the tutorial explaining I am not able to figure out where my file path is wrong. Or is it something else? |
best to search the jenkinsci GitHub org to see how it's used, lots of this stuff is under-documented so code is the best example |
All the checks have passed. @uhafner was right about this:
I was making the mistake of adding the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your PR. The 1:1 conversions looks good.
(I wonder if we should also change var
to const
and the TODO does not make sense to me as well?)
script
block to external file
script
block to external filescript
block in "failed-test.jelly" to external file
About changing The properties are being reassigned in two places.
In that case should we change it to But the value is not being changed directly so maybe we can. |
That's not reassigning the value that's modifying properties which is allowed when it's a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
What
Moved the following the
<script>
block that was causing the issue to an external file:Closes
https://issues.jenkins.io/browse/JENKINS-69658