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
The 'pre-generate' contents still get written to disk (including a pom without github info), but the first attempt at deletion causes the rest of the script to prematurely fail.
My assumption is that this originally implemented using Java 8.
Are you interested in contributing a fix?
The fix is trivial. Assuming a fix without tests might be rejected, I started down down that path, which led to more (unrelated) issues. I'll submit a PR shortly and you can decide what to do when you see it.
The text was updated successfully, but these errors were encountered:
It looks like @jglick spotted that code as a potential problem as well (#602 (comment)), even though the actual issue (and symptoms) were not quite the same as mine.
Jenkins and plugins versions report
Environment
N/A
What Operating System are you using (both controller, and any agents involved in the problem)?
Linux (controller/agents N/A)
Reproduction steps
Generate an archetype with
-DhostOnJenkinsGitHub=false
:Expected Results
I expected the generation to:
.gitignore
After looking at the source to see what that flag is supposed to do, I'd also expect no
LICENSE.md
,Jenkinsfile
, or.github/
.Actual Results
gitignore
(no leading dot); this is what got my attention$ ls -a . .. .github gitignore Jenkinsfile LICENSE.md .mvn pom.xml README.md src
Anything else?
The root cause is using a private constructor:
archetypes/common-files/archetype-post-generate.groovy
Line 19 in 3343e9a
The 'pre-generate' contents still get written to disk (including a pom without github info), but the first attempt at deletion causes the rest of the script to prematurely fail.
My assumption is that this originally implemented using Java 8.
Are you interested in contributing a fix?
The fix is trivial. Assuming a fix without tests might be rejected, I started down down that path, which led to more (unrelated) issues. I'll submit a PR shortly and you can decide what to do when you see it.
The text was updated successfully, but these errors were encountered: