Reply to: Anyone done any Jenkins?

[The Only Way Is Keynsham]

Think it was yum install jenkins -y on RHEL!!

Checked the gui worked and handed it over to the devs. No complaints but half the time they insist on stuff then never use it!

Lol! Yeah, been there myself

[stek]

Well, in my case it'll probably take up most of my time getting it set up before I get on with the regular dev work at which point I guess it'll just tick over with minimal input from myself.

They don't even do any unit testing so I guess I'll be configuring the Git plugin and whatever build engine they want to use. NAnt or whatever.

Think it was yum install jenkins -y on RHEL!!

Checked the gui worked and handed it over to the devs. No complaints but half the time they insist on stuff then never use it!

[The Only Way Is Keynsham]

Like everyone's said Jenkins is just a small cog, last role before this I was Environments Manager (stupid title) and did Jenkins, Maven, SonarQube, Cobbler, Puppet, RHEL Kickstarts, AIX NIM builds, DB2 installs, VMware ESX, storage, fibre, and all the networking and firewalling.

Can't think how Jenkins can be anything other than a tiny part of environments and builds.

And didn't it used to be called Hudson?

Well, in my case it'll probably take up most of my time getting it set up before I get on with the regular dev work at which point I guess it'll just tick over with minimal input from myself.

They don't even do any unit testing so I guess I'll be configuring the Git plugin and whatever build engine they want to use. NAnt or whatever.

[stek]

Like everyone's said Jenkins is just a small cog, last role before this I was Environments Manager (stupid title) and did Jenkins, Maven, SonarQube, Cobbler, Puppet, RHEL Kickstarts, AIX NIM builds, DB2 installs, VMware ESX, storage, fibre, and all the networking and firewalling.

Can't think how Jenkins can be anything other than a tiny part of environments and builds.

And didn't it used to be called Hudson?

[d000hg]

Used it predominantly to manage unit testing so far. Not too awful unlike some systems I've used, certainly not a waste of time.

[pauldee]

past?

Whoops, yes. Now edited.

[SueEllen]

Jenkins/Team City/Octopus they're all things that anyone with any common sense can pick up in a few days and become proficient at.

Trouble is getting part the agents if it's not on your CV.

past?

[pauldee]

Jenkins/Team City/Octopus they're all things that anyone with any common sense can pick up in a few days and become proficient at.

Trouble is getting past the agents if it's not on your CV.

[SueEllen]

I was writing Java applets for websites at the time - animations, really.

Somebody thought that now Microsoft had jumped aboard the Java bandwagon they'd soon have the monopoly therefore the decision was taken.

Should have aligned yourself with Apple...

[The Only Way Is Keynsham]

exactly what I did when I read that!

OP - tell me more, I need a good laugh! Why on earth were you using that?

I was writing Java applets for websites at the time - animations, really.

Somebody thought that now Microsoft had jumped aboard the Java bandwagon they'd soon have the monopoly therefore the decision was taken.

[garethevans1986]

I've not used Jenkins but used TeamCity (and Bamboo for a little bit) for .NET CI and then Octopus Deploy for deployments.

[jmo21]

Visual J++.

exactly what I did when I read that!

OP - tell me more, I need a good laugh! Why on earth were you using that?

[MrMarkyMark]

I thought this was a Leeroy Jenkins thread

No, its one of Scroaties creations talking total tulip as per usual

[northernladuk]

I thought this was a Leeroy Jenkins thread

[RasputinDude]

Anyone done any Jenkins?

It depends on what you mean by "doing" Jenkins.

As previously said, it's pretty damned easy to set up Jenkins as a stand alone that just builds the software. If you are talking about the set-up that I am responsible for - several servers, multiple slaves building for OSX, Windows, linux, iOS and android and then also automatically deploying virtualised (where possible) test environments and running multiple tests against the artefacts then it gets a little more complex.