On 01/07/2014 11:14 AM, Kevin Fleming (BLOOMBERG/ 731 LEXIN) wrote:
<snide mode>
For a continuous integration project, Jenkins seems to have quite a few
error-prone manual processes.
</snide mode>
Yes, the automation of the release process has been lacking.
It is fully scripted, but when it fails in the middle there's really no
good way to automatically resume/recover from where it failed.
----- Original Message -----
From: [email protected] <mailto:[email protected]>
To: [email protected] <mailto:[email protected]>
At: Jan 7 2014 14:11:44
1.546 has been released yesterday, but there's no tag corresponding to it
in
https://github.com/jenkinsci/jenkins
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
