You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And this both scenarios should have the same outcome.
In my particular case, I have two Jenkins instances connecting to each other, one provides a file where the connections details are provided, which cannot be created (using RealJenkinsRule) because the locations hasn't been set yet.
This error happens now because previously the port was assigned beforehand and now is assigned by jetty in runtime by a file. To that port number could be passed out as param in jcasc
unclassified:
location:
url: ${MY_URL}
but now is impossible.
Expected Results
JenkinsLocationConfiguration.xml file exists when the RealJenkinsRule is used.
Actual Results
The mentioned file doesn't exist.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
Only JTHWhat Operating System are you using (both controller, and any agents involved in the problem)?
Mac OS
Reproduction steps
This test shows the error:
When using rr.runRemotely the files is created (this includes rr.then), but not always
then
can be used (or makes testing very complex at least).This test currently passes
And this both scenarios should have the same outcome.
In my particular case, I have two Jenkins instances connecting to each other, one provides a file where the connections details are provided, which cannot be created (using RealJenkinsRule) because the locations hasn't been set yet.
This error happens now because previously the port was assigned beforehand and now is assigned by jetty in runtime by a file. To that port number could be passed out as param in jcasc
but now is impossible.
Expected Results
JenkinsLocationConfiguration.xml file exists when the RealJenkinsRule is used.
Actual Results
The mentioned file doesn't exist.
Anything else?
No response
The text was updated successfully, but these errors were encountered: