SqueakTrunk, ExternalPackages, ExternalPackages-4.4, ExternalPackages-4.3 and possibly others have all vanished from build.squeak.org. Anyone have any idea where they went?
frank
It might be that someone upgraded jenkins? It's now running 1.518, and some folks have seen this version have issues loading the ruby-runtime. That causes builds that use Ruby (like SqueakTrunk and the ExternalPackages-foo jobs, but NOT like ReleaseSqueakTrunk) to fail to load, hence disappear.
So: has anyone upgraded Jenkins?
frank
On 14 June 2013 23:39, Frank Shearar frank.shearar@gmail.com wrote:
SqueakTrunk, ExternalPackages, ExternalPackages-4.4, ExternalPackages-4.3 and possibly others have all vanished from build.squeak.org. Anyone have any idea where they went?
frank
Yes, Jenkins is updated almost continuously, every few days anyway, just like every other piece of software on the system by apt/dpkg.
Is the recommended fix to revert to 1.517? Or an earlier version?
Ken
P.S. FYI All this is logged in /root/admin-log.txt (actually it's under RCS in the same location) and /var/log/apt/history.log as well as other logs.
On 06/15/2013 07:27 AM, Frank Shearar wrote:
It might be that someone upgraded jenkins? It's now running 1.518, and some folks have seen this version have issues loading the ruby-runtime. That causes builds that use Ruby (like SqueakTrunk and the ExternalPackages-foo jobs, but NOT like ReleaseSqueakTrunk) to fail to load, hence disappear.
So: has anyone upgraded Jenkins?
frank
On 14 June 2013 23:39, Frank Sheararfrank.shearar@gmail.com wrote:
SqueakTrunk, ExternalPackages, ExternalPackages-4.4, ExternalPackages-4.3 and possibly others have all vanished from build.squeak.org. Anyone have any idea where they went?
frank
Ah, so I'm not going crazy! Yes, the recommended workaround is to roll back to 1.517. It's something to do with the 1.518+ruby-runtime mix. Someone's reported that using a custom patch with the ruby-runtime plugin also works, but I'd much rather roll back.
frank
On 15 June 2013 13:43, Ken Causey ken@kencausey.com wrote:
Yes, Jenkins is updated almost continuously, every few days anyway, just like every other piece of software on the system by apt/dpkg.
Is the recommended fix to revert to 1.517? Or an earlier version?
Ken
P.S. FYI All this is logged in /root/admin-log.txt (actually it's under RCS in the same location) and /var/log/apt/history.log as well as other logs.
On 06/15/2013 07:27 AM, Frank Shearar wrote:
It might be that someone upgraded jenkins? It's now running 1.518, and some folks have seen this version have issues loading the ruby-runtime. That causes builds that use Ruby (like SqueakTrunk and the ExternalPackages-foo jobs, but NOT like ReleaseSqueakTrunk) to fail to load, hence disappear.
So: has anyone upgraded Jenkins?
frank
On 14 June 2013 23:39, Frank Sheararfrank.shearar@gmail.com wrote:
SqueakTrunk, ExternalPackages, ExternalPackages-4.4, ExternalPackages-4.3 and possibly others have all vanished from build.squeak.org. Anyone have any idea where they went?
frank
Done. So how do we know when it is safe to go back in the water again? What can we do to continue to track development?
Ken
On 06/15/2013 08:10 AM, Frank Shearar wrote:
Ah, so I'm not going crazy! Yes, the recommended workaround is to roll back to 1.517. It's something to do with the 1.518+ruby-runtime mix. Someone's reported that using a custom patch with the ruby-runtime plugin also works, but I'd much rather roll back.
frank
On 15 June 2013 13:43, Ken Causeyken@kencausey.com wrote:
Yes, Jenkins is updated almost continuously, every few days anyway, just like every other piece of software on the system by apt/dpkg.
Is the recommended fix to revert to 1.517? Or an earlier version?
Ken
P.S. FYI All this is logged in /root/admin-log.txt (actually it's under RCS in the same location) and /var/log/apt/history.log as well as other logs.
On 06/15/2013 07:27 AM, Frank Shearar wrote:
It might be that someone upgraded jenkins? It's now running 1.518, and some folks have seen this version have issues loading the ruby-runtime. That causes builds that use Ruby (like SqueakTrunk and the ExternalPackages-foo jobs, but NOT like ReleaseSqueakTrunk) to fail to load, hence disappear.
So: has anyone upgraded Jenkins?
frank
On 14 June 2013 23:39, Frank Sheararfrank.shearar@gmail.com wrote:
SqueakTrunk, ExternalPackages, ExternalPackages-4.4, ExternalPackages-4.3 and possibly others have all vanished from build.squeak.org. Anyone have any idea where they went?
frank
Thanks! The builds are back. SqueakTrunk had forgotten it used the RVM plugin, but I fixed that.
I can't figure out if we want to track activity on https://github.com/jenkinsci/jenkins.rb/tree/master/ruby-runtime or https://github.com/jenkinsci/ruby-runtime-plugin.
On 15 June 2013 14:21, Ken Causey ken@kencausey.com wrote:
Done. So how do we know when it is safe to go back in the water again? What can we do to continue to track development?
Ken
On 06/15/2013 08:10 AM, Frank Shearar wrote:
Ah, so I'm not going crazy! Yes, the recommended workaround is to roll back to 1.517. It's something to do with the 1.518+ruby-runtime mix. Someone's reported that using a custom patch with the ruby-runtime plugin also works, but I'd much rather roll back.
frank
On 15 June 2013 13:43, Ken Causeyken@kencausey.com wrote:
Yes, Jenkins is updated almost continuously, every few days anyway, just like every other piece of software on the system by apt/dpkg.
Is the recommended fix to revert to 1.517? Or an earlier version?
Ken
P.S. FYI All this is logged in /root/admin-log.txt (actually it's under RCS in the same location) and /var/log/apt/history.log as well as other logs.
On 06/15/2013 07:27 AM, Frank Shearar wrote:
It might be that someone upgraded jenkins? It's now running 1.518, and some folks have seen this version have issues loading the ruby-runtime. That causes builds that use Ruby (like SqueakTrunk and the ExternalPackages-foo jobs, but NOT like ReleaseSqueakTrunk) to fail to load, hence disappear.
So: has anyone upgraded Jenkins?
frank
On 14 June 2013 23:39, Frank Sheararfrank.shearar@gmail.com wrote:
SqueakTrunk, ExternalPackages, ExternalPackages-4.4, ExternalPackages-4.3 and possibly others have all vanished from build.squeak.org. Anyone have any idea where they went?
frank
We are now 5 releases behind on Jenkins (1.517 -> 1.522). What can be done to allow us to track releases again while having all builds continue to work?
Ken
I appreciate that we don't want to get left behind, but I also don't see the need to keep right on the bleeding edge. I'm happy for us to try out the latest build - it looks like they might have fixed the Ruby issue - and if necessary revert.
When would be a convenient time for such an experiment?
frank
On 6 July 2013 21:08, Ken Causey ken@kencausey.com wrote:
We are now 5 releases behind on Jenkins (1.517 -> 1.522). What can be done to allow us to track releases again while having all builds continue to work?
Ken
box-admins@lists.squeakfoundation.org