Jenkins Certified by Bitnami (PV)

This image is for customers that require legacy paravirtualization support (PV). New deployments should use the "Jenkins" image at Jenkins is a Java based, open source automation server that is nearly synonymous with Continuous Integration and Continuous Delivery. Software development teams use it to be more efficient by building, testing, and deploying updates to software projects automatically and enabling more changes to be integrated more frequently, with fewer problems. Jenkins has been integral to the rise of DevOps-based software de... See more

Customer Reviews

Create Your Own Review

Can't login, default user not well documented

  • By Ravel
  • on 12/29/2015

Instance started fine, and the default served page of the jenkins instance is a bitnami page that redirects you to the jenkins application. On that same page, it says the default user is "user", however it doesn't provide any password, so I couldn't login. After some googling on forums and pages for default username and password, I found, which says that the default username and password should be user/bitnami. I tried it, and it didn't work. The work around would be to ssh and edit the config.xml, but for me that breaks the purpose of using an AMI, since at that point I can just install on a plain ec2 instance, with updated Jenkins and linux version.

Out of date & too complicated

  • By James Billingham
  • on 05/14/2014

First issue - the version is really quite old. The AMI has never been updated.

Second - the Bitnami stack system is really too complex. Installing Jenkins manually is significantly easier.

Last - I did have a problem with the default password not being correct, but that might be user error.

I would recommend instead that you create a Ubuntu 14.04 instance, then it is virtually a one line installation:

Easy to launch Jenkins, but some issues

  • By Amazon Customer
  • on 01/22/2014

I wanted to Jenkins server for research so choose this marketplace product for speedy start. It was very good for this purpose. If I want to launch Jenkins for same reason, I will use it again.

But it seems not enough for full operation for production usage (please read blow plugin installation issue), so if you plan to launch Jenkins for heavy use, you might have to manage it with bare EC2 instance.

## Good
- Very easy to use. Only a few clicks. If you familiar with AWS console, almost same to launch EC2 instance.
- No extra cost for using software.
- Can login instance via SSH (Jenkins SaaS doesn't allow it)

## No Good
- Can't install new Jenkins plugin (why?) it's very serious issue.
- Need to googling first login id/pass (should be written startup page?)

showing 1 - 3