- Download jenkins.war
- Create pom.xml (it'll be pretty much empty)
- Create Procfile to do 'java -jar jenkins.war' etc...
Deploy!
| <?xml version="1.0" encoding="UTF-8"?> | |
| <!-- | |
| Just need a plain and mostly empty pom.xml for Heroku to detect that this is a Java application | |
| --> | |
| <project xmlns="http://maven.apache.org/POM/4.0.0" | |
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | |
| xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> | |
| <modelVersion>4.0.0</modelVersion> | |
| <groupId>com.example</groupId> | |
| <version>1.0-SNAPSHOT</version> | |
| <artifactId>helloworld</artifactId> | |
| </project> |
| # Only listen on http; disable ajp and https | |
| web: java -jar jenkins.war --httpPort=$PORT --ajp13Port=-1 --httpsPort=-1 |
To get initial password restart the Dyno and type
heroku logs --app your-app-name where you installed heroku cli
For preventing it to sleep register site here
https://kaffeine.herokuapp.com
Where does the jenkins create its configuration files in heroku after it has been deployed using this approach.
Since Heroku is not persisting the configuration files after restart so I want to keep all these configuration files inside the git. So after restart I do not need to configure again and it will pick from the config files. Is it possible ?
@satnam348 I am facing the same issue, after 4 or 5 hours it is asking me for the Administrator password. Anyone know why?