[JIRA] [build-flow] (JENKINS-20843) build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace
Damien Nozay commented on JENKINS-20843 build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace build-flow v. 0.12 can now use a workspace back again. https://github.com/jenkinsci/build-flow-plugin/commit/00b7ad56eca41eebcfd19bd3e54de0ace66ae0be Corey, could you please verify you are now able to use it as you intended? 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow] (JENKINS-20843) build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace
Corey O'Connor commented on JENKINS-20843 build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace I'd expect the requirements of a build steps should be something jenkins would filter on. As for archive artifact: That "archive artifacts" doesn't make sense for a build flow job is an example of the issue. If archiving artifacts does not make sense then the step should not be selectable in the UI. Anyways, sounds like properly resolving this issue requires changes to jenkins core. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20843) build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace
Corey O'Connor updated JENKINS-20843 build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace Change By: Corey O'Connor (02/Dec/13 9:04 PM) Description: The build flow job type does not initialize the project's workspace. However, this project supports options, like SCM, that require a workspace to be initialized. This means:# build-flow projects cannot use SCM#* build-flow projects cannot be triggered by SCM changes if that trigger requires a workspace. Due to JENKINS-20767 all Git triggered projects currently require a workspace.# build-flow projects cannot use any post-build action that assumes a workspace. EG: archive artifacts commit that introduced issue: https://github.com/jenkinsci/build-flow-plugin/commit/444097d65ecb97c92005b3acd63db8e03bdeb6a3 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20843) build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace
Nicolas De Loof commented on JENKINS-20843 build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace I don't think there's a way to filter build step to require a workspace. Archiving artifact for a flow don't make sense, only jobs triggered by artifact have built artifacts to be archived. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20843) build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace
Corey O'Connor created JENKINS-20843 build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 02/Dec/13 9:03 PM Description: The build flow job type does not initialize the project's workspace. However, this project supports options, like SCM, that require a workspace to be initialized. This means: build-flow projects cannot use SCM build-flow projects cannot be triggered by SCM changes if that trigger requires a workspace. Due to JENKINS-20767 all Git triggered projects currently require a workspace. build-flow projects cannot use any post-build action that assumes a workspace. EG: archive artifacts Project: Jenkins Priority: Major Reporter: Corey O'Connor 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
