Making Jenkins instances deployed over HTTPS work

[vivek]

My Jenkins instance is running on CloudBees DEV@cloud, the Jenkins instance is available over HTTPS. There is bug in the Janky job_creator.rb where it fails to talk over https and hubot jenkins command shows this stack trace https://gist.github.com/1504508.

The fix is simple, for both exist? and run method, set http.use_ssl=true based on scheme. I verified this fix to work with Jenkins instance running over HTTPS.

[sr]

Great, thanks. I think the Builder won't work over SSL either. Same fix should do it.

[maletor]

Can you provide some documentation on setting this up with Cloudbees?

[maletor]

/cc @vivek

[vivek]

Checkout my blog on how you can use your Janky setup with CloudBees DEV@cloud provisioned Jenkins: http://blog.cloudbees.com/2011/12/devcloud-meets-github-janky.html. Once we roll out procfile support, you can pretty much host entire Janky installation on CloudBees.

[maletor]

I followed your blog to the T and the Janky instructions but I still
see it is not queuing jobs. I am using Janky at master.

On another note on cloudbees, if I set up the build with the gist's
schema.xml I must change it to accept builds via scripts.

On Feb 10, 2012, at 11:20 AM, vivek
reply@reply.github.com
wrote:

Checkout my blog on how you can use your Janky setup with CloudBees DEV@cloud provisioned Jenkins: http://blog.cloudbees.com/2011/12/devcloud-meets-github-janky.html. Once we roll out procfile support, you can pretty much host entire Janky installation on CloudBees.

---

Reply to this email directly or view it on GitHub:
#7 (comment)

[sr]

Try Janky 0.9.9 (just fresh)

[vivek]

Right, the build created on CloudBees provisioned Jenkins will be of
Execute Shell type.

Key piece of CoudBees integration is that you setup JANKY_BUILDER_DEFAULT
with CloudBees credentials, the build should automatically setup when you
give it command from the chat room. And you also need to point to the Janky
endpoint in the Notification Plugin configuration.

On Fri, Feb 10, 2012 at 12:34 PM, Ellis Berner <
reply@reply.github.com

wrote:

I followed your blog to the T and the Janky instructions but I still
see it is not queuing jobs. I am using Janky at master.

On another note on cloudbees, if I set up the build with the gist's
schema.xml I must change it to accept builds via scripts.

On Feb 10, 2012, at 11:20 AM, vivek
reply@reply.github.com
wrote:

Checkout my blog on how you can use your Janky setup with CloudBees
DEV@cloud provisioned Jenkins:
http://blog.cloudbees.com/2011/12/devcloud-meets-github-janky.html. Once
we roll out procfile support, you can pretty much host entire Janky
installation on CloudBees.

---

Reply to this email directly or view it on GitHub:
#7 (comment)

---

Reply to this email directly or view it on GitHub:
#7 (comment)

[vivek]

@maletor Right, I missed the part of 'accept build via scripts' part. Thanks.

[CTSi]

Hey Vivek, Great post. Any idea if Cloudbees have rolled out procfile support support yet? Thanks >Once we roll out procfile support, you can pretty much host entire Janky installation on CloudBees.