Infrastructure Preview avaliações

nice

Kevin D. · Revisado há almost 9 years

Juan G. · Revisado há almost 9 years

Anthony P. · Revisado há almost 9 years

Saurabh K. · Revisado há almost 9 years

+1

Fabrizio B. · Revisado há almost 9 years

There are 3 Jenkins images. The one in the lab doesn't exist. After launching the 'correct' bitnami image it attempts to install plugins during login. This errors out due to permission issues. This lab was needs updating. It would be very frustrating to a novice cloud, and *nix person.

Thomas L. · Revisado há almost 9 years

Jenkins deployment template no longer deploys binaries to /opt/bitnami/

Nicholas R. · Revisado há almost 9 years

Omar P. · Revisado há almost 9 years

Ravi M. · Revisado há almost 9 years

Don B. · Revisado há almost 9 years

Stephanie W. · Revisado há almost 9 years

Enric P. · Revisado há almost 9 years

"sudo /opt/bitnami/ctlscript.sh stop" does not work.

David V. · Revisado há almost 9 years

Mickey B. · Revisado há almost 9 years

Mikhail B. · Revisado há almost 9 years

good

Eliton O. · Revisado há almost 9 years

/opt/bitnami/ctlscript.sh is not available at that location

Mikhail Y. · Revisado há almost 9 years

There is no Bitnami distribution and the Jenkins instance I set up was not compatible with your instructions for starting/stopping the service

Michael R. · Revisado há almost 9 years

Jenkins can't be accessed after it has deployed.

Jim K. · Revisado há almost 9 years

so important to know

Gustavo M. · Revisado há almost 9 years

Gouri N. · Revisado há almost 9 years

should have step by step in more detail

Willie R. · Revisado há almost 9 years

Yuri L. · Revisado há almost 9 years

Natanael H. · Revisado há almost 9 years

the /opt/bitnami... is out of date. the current vm that gets launched uses sysctl /etc/init.d/jenkins for service control.

Dustin B. · Revisado há almost 9 years