@Dimuthu Since the build job is not created as a consequence the deployment does not happen also. So there will be not artifact to launch. Hence it throws an error and we need to handle that. As soon as a build job is created as mentioned above it will subsequently start the deployment process.
@Udara Your suggestion is correct. We can provide the information about Jenkins not available to the user. Since we haven't noticed Jenkins going offline often the above solution suggested by me would work. Further more since we can inform the user above the Jenkins outage, they can go ahead with building the application again. Thanks GayanD On Thu, Oct 23, 2014 at 9:56 PM, Udara Liyanage <[email protected]> wrote: > Hi Gayan, > > Shouldn't let the user be know at branch creation time that Jenkins is not > online so auto build and app deploy won't work until Jenkins become online? > Jobs are kept in a queue if offline and start execute when become online. > If user click App Deploy while Jenkins is offline, he will be shown a > error and may be schedule it to deploy when online. > > > > Touched, not typed. Erroneous words are a feature, not a typo. > -- Gayan Dhanuska Software Engineer http://wso2.com/ Lean Enterprise Middleware Mobile 071 666 2327 Office Tel : 94 11 214 5345 Fax : 94 11 214 5300 Twitter : https://twitter.com/gayanlggd
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
