-
Notifications
You must be signed in to change notification settings - Fork 46
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
Parity with standard Jenkinsfile for Docker #42
Comments
Maybe this should be a bug instead of feature request but reporting as feature request in case the behaviour is as intended. |
Hi @m0un10 , On which job type you are experiencing this problem ? Pipeline or MultiBranch Pipeline ? |
The issue is with pipeline project when selecting "Pipeline As Yaml from SCM", it won't automatically do the checkout. I've just tested on multi-branch and it seems to be fine. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Since the standard Jenkinsfile doesn't require an explicit clone, pipeline as yaml shouldn't either.
Describe the solution you'd like
When it is yaml from SCM it should automatically have the code cloned (as per the configuration) to be consistent with what happens for Jenkinsfile from SCM.
Describe alternatives you've considered
The workaround is to add an explicit checkout
This works..
But this doesn't
Unless you add a clone step before the maven build
The text was updated successfully, but these errors were encountered: