Em quarta-feira, 21 de setembro de 2016 21:44:35 UTC-3, Leandro Marinho escreveu:
Ai galela, também fiquei enroscado neste problema.
O problema esta relacionado a versão do ruby presente.
root@precise32:/var/lib/jenkins/secrets# ruby -v
ruby 1.8.7 (2011-06-30 patchlevel 352) [i686-linux]
root@precise32:/var/lib/jenkins/secrets#
mas:
==> ci: ruby-xz requires Ruby version >= 1.9.3.
Tentei Instalar o fpm manualmente conforme descreve o registro no log e este até instalou e, em novo provisionamento não aparece mais o erro do fpm
Porem ao rodar o build, no jenkins, e este ao executar o Script para fpm, novamente aparece o erro:
channel stopped
[workspace] $ /bin/sh -xe /tmp/hudson4896210677898911031.sh
+ fpm -s dir -t deb -C combined/target --prefix /var/lib/tomcat7/webapps/ -d tomcat7 -n devopsnapratica -v 1.master -a noarch devopsnapratica.war
/tmp/hudson4896210677898911031.sh: 2: /tmp/hudson4896210677898911031.sh: fpm: not found
Build step 'Execute shell' marked build as failure
Archiving artifacts
Finished: FAILURE
Neste caso então , não adianta instalar o fpm, manualmente para burlar o erro.
Solução: atualizar o ruby, via rvm, para que o fpm seja instalado conforme ci.pp
Porem a atualização foi penosa más consegui:
Através do stackoverflow abaixo, resolvi
http://stackoverflow.com/questions/9439502/rvm-install-ruby-installation-err
1 -- Instalar o rvm via curl:
apt-get install curl
curl -L
https://get.rvm.io | bash -s stable
Nao instale o rvm via apt-get
apt-get install ruby-rvm
rvm reload
rvm install 1.9.3
root@precise32:~# rvm install 1.9.3
Searching for binary rubies, this might take some time.
Found remote file
https://rvm_io.global.ssl.fastly.net/binaries/ubuntu/12.04/i386/ruby-1.9.3-p551.tar.bz2
Checking requirements for ubuntu.
Installing requirements for ubuntu.
Updating system.........
Installing required packages: gawk, libyaml-dev, libsqlite3-dev, sqlite3, autoconf, libgmp-dev, libgdbm-dev, libncurses5-dev, automake, libtool, bison, pkg-config, libffi-dev............
Requirements installation successful.
ruby-1.9.3-p551 - #configure
ruby-1.9.3-p551 - #download
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 11.6M 100 11.6M 0 0 53891 0 0:03:46 0:03:46 --:--:-- 156k
ruby-1.9.3-p551 - #validate archive
ruby-1.9.3-p551 - #extract
ruby-1.9.3-p551 - #validate binary
ruby-1.9.3-p551 - #setup
ruby-1.9.3-p551 - #gemset created /usr/local/rvm/gems/ruby-1.9.3-p551@global
ruby-1.9.3-p551 - #importing gemset /usr/local/rvm/gemsets/global.gems..............................
ruby-1.9.3-p551 - #generating global wrappers........
ruby-1.9.3-p551 - #gemset created /usr/local/rvm/gems/ruby-1.9.3-p551
ruby-1.9.3-p551 - #importing gemsetfile /usr/local/rvm/gemsets/default.gems evaluated to empty gem list
ruby-1.9.3-p551 - #generating default wrappers........
root@precise32:~#
Ruby atualizado
root@precise32:~# ruby -v
ruby 1.9.3p551 (2014-11-13 revision 48407) [i686-linux]
root@precise32:~#
Só que a agora com a nova versao do ruby, para atender ao erro :
ci: ruby-xz requires Ruby version >= 1.9.3.
Ao reprovisionar a ci, tomo o erro abaixo:
C:\Users\alex>vagrant provision ci
==> ci: Installing Puppet modules in "librarian" with Librarian-Puppet...
==> ci: Running provisioner: puppet...
==> ci: Running Puppet with ci.pp...
==> ci: stdin: is not a tty
==> ci: /opt/vagrant_ruby/lib/ruby/site_ruby/1.8/rubygems.rb:900:in `report_activate_error'
==> ci: :
==> ci: Could not find RubyGem puppet (>= 0)
==> ci: (
==> ci: Gem::LoadError
==> ci: )
==> ci: from /opt/vagrant_ruby/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `activate'
==> ci: from /opt/vagrant_ruby/lib/ruby/site_ruby/1.8/rubygems.rb:1276:in `gem'
==> ci: from /opt/vagrant_ruby/bin/puppet:18
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
Precisamos entender porque ainda continua tentando usar o ruby 1.8.7
Alguem arrisca?