Feed aggregator

Jenkins User Conference – Save the Date

Jenkins Blogs - Tue, 2015-03-03 15:38

We have some exciting news to share with you! We have finalized most of the dates and locations for the 2015 Jenkins User Conference (JUC) World Tour.

Save the date(s):

  • US East (Washington DC): June 18-19
  • Europe (London): June 23-24
  • Israel: July 16 (ETA)
  • US West (Santa Clara): September 2-3

The big news? The JUC agenda has been expanded this year to cover two days! That means you get twice as many opportunities to learn how others are using Jenkins and to network with other Jenkins users.

CALL FOR PAPERS IS OPEN FOR ALL JUC CONFERENCES

We need JUC speakers! The Call for Papers is open now and you can apply here. This is an opportunity for YOU to give back to the community by sharing your Jenkins knowledge and success. Jenkins speakers contribute significantly to the overall JUC experience.

In return for speaking, you will receive free admission to the conference and fame/fortune within the Jenkins community. OK, we can’t guarantee the latter, but we can guarantee the former! Hurry and apply now, because the Call for Papers deadline for US East and Europe expires on March 22, 2015.

Not interested in speaking? Another way to contribute to the community is by letting us know who you want to hear from. Nominate or refer that amazing speaker and we’ll do the rest. Contact alytong13@gmail.com

JUC SPONSORSHIPS

Lastly, be a JUC sponsor. Any organization can do this – whether a vendor that sells into the Jenkins ecosystem or a company that has received value from Jenkins and wants to give back to the community. You can find out more here. (NOTE: JUC is not a moneymaking venture for the community – so sponsorships do make a difference.)

Perforce Plugin 1.3.34

Project Releases - Mon, 2015-03-02 08:43
Perforce Plugin 1.3.34

Matrix Groovy Execution Strategy Plugin 1.0.0 (new)

Project Releases - Sun, 2015-03-01 18:34
Matrix Groovy Execution Strategy Plugin 1.0.0

Copy Artifact Plugin 1.35

Project Releases - Sun, 2015-03-01 14:08
Copy Artifact Plugin 1.35

xUnit Plugin 1.94

Project Releases - Sat, 2015-02-28 14:25
xUnit Plugin 1.94

Change Assembly Version 1.5.1

Project Releases - Sat, 2015-02-28 10:46
Change Assembly Version 1.5.1

Repository Connector Plugin 1.1.1

Project Releases - Sat, 2015-02-28 08:25
Repository Connector Plugin 1.1.1

Xcode Plugin 1.4.8

Project Releases - Sat, 2015-02-28 07:50
Xcode Plugin 1.4.8

Groovy folks, time to start agreeing

kohsuke's blog - Sat, 2015-02-28 00:07

I wrote about the drama unfolding in the Groovy project a month ago.

I left that topic for a while, but I was pleased to find out today that the question is no longer whether they need to move to a foundation, but rather which foundation it should be. There’s an email thread that has 188 messages and counting, going for more than 2 weeks, where the community is trying to figure out where to go.

I feel a bit of deja-vu, and I feel like I know exactly what’s going on. And no, I don’t mean the Jenkins drama, though we were in a relatable situation. Instead, I was thinking when I and my wife bought a house 5 years ago.

So there were two houses we really liked. The white house and the beige house. Like any informed buyer would do, my wife and I start disecting pros and cons. The white house felt a lot brighter and airy than the beige house, but the beige house has a bigger backyard. The white house is closer to a hospital, which might mean more noise. The beige house has a big tree nearby, and the gutter might fill up. List like that went on and on.

Now, the thing is, at a certain point, a list like this gets more confusing than helpful. I can add up all the pros and cons, but it doesn’t help me getting any closer to the decision making. In fact I’m no longer sure if the white house I wanted was really such a good idea. After all, it has no less than a dozen things listed under “cons”. I can see that my wife is getting just as confused as I am. The conversation starts to go in circles. I was lucky enough that our parents were living in the other side of the Pacific ocean, so we kept this conversation to ourselves. Otherwise, I’m sure it would have been even worse. They mean well, but sometimes too many opinions are more harmful than helpful.

In 1am in one of those long nights, I finally realized that agreeing on something, anything, is more important than figuring out the absolute best house out of two. So like every husband would do, I started trying to talk myself out of the white house I originally wanted, and speak about things I liked about the beige house that my wife originally wanted. I tried to downplay the concerns she had about the beige house.

Even though I started doing this consciously, the strange thing is that I started getting convinced by my own arguments that I didn’t fully believe in. Sure, the beige house doesn’t have the attic room that’s going to be my LEGO room, but I can get a brighter office and maybe I should keep my LEGO there so that I can occupy myself if meetings get boring. And in the end, we bought the beige house and we still live there mostly happily.

I feel like it’s time for Groovy guys to start doing this “let’s agree, whatever it is” dance. Judging from the conversations, I think they’ve figured out that they can live in any of these three foundations. The trick is not to get caught up on all the gory details, because there will be always something you don’t like. Yes, voting might be burdensome. Yes, losing @author tag might be annoying. Yes, infra migration would be painful. But you’ll be all right, and you’ll get used to it sooner than you think.

It’s time for people in the community to give the project leaders a blank check. I think we should be able to all trust them that they have the best interest of the project in mind.

And more importantly, it’s time for the project leaders to start converging. You guys need to sense where your consensus is heading to, and try to talk yourself into it. Try to create an echo chamber.

Engineers aren’t the best people to do this, but you guys really need to do this, because the clock is ticking. The difference between foundations is relatively small, but the difference between moving forward and procrastinating is huge. It’s a part of the leadership responsibility to form a consensus and then turn around and sell that to everyone, so that everyone feels better about what’s being done.

Remember, there’s really no wrong answer. Just different correct answers.

Categories: Planet

Gitlab Hook Plugin 1.3.1

Project Releases - Fri, 2015-02-27 12:19
Gitlab Hook Plugin 1.3.1

Matrix Project Plugin 1.2.1

Project Releases - Fri, 2015-02-27 12:12
Matrix Project Plugin 1.2.1

Robot Framework Plugin 1.6.0

Project Releases - Thu, 2015-02-26 17:33
Robot Framework Plugin 1.6.0

OpenShift Deployer Plugin 1.2.0

Project Releases - Thu, 2015-02-26 17:29
OpenShift Deployer Plugin 1.2.0

AntepediaReporter-CI-plugin 1.8

Project Releases - Thu, 2015-02-26 13:20
AntepediaReporter-CI-plugin 1.8

AntepediaReporter-CI-plugin 1.8

Project Releases - Thu, 2015-02-26 13:20
AntepediaReporter-CI-plugin 1.8

AntepediaReporter-CI-plugin 1.8

Project Releases - Thu, 2015-02-26 13:20
AntepediaReporter-CI-plugin 1.8

Notification Plugin 1.8

Project Releases - Thu, 2015-02-26 12:31
Notification Plugin 1.8

TestFairy Plugin 2.5

Project Releases - Thu, 2015-02-26 08:22
TestFairy Plugin 2.5

vSphere Cloud Plugin 2.4

Project Releases - Thu, 2015-02-26 05:22
vSphere Cloud Plugin 2.4

100K Celebration Podcast

Jenkins Blogs - Wed, 2015-02-25 20:39

As a part of the Jenkins 100K celebration, Dean Yu, Andrew Bayer, R. Tyler Croy, Chris Orr, and myself got together late Tuesday evening to go over the history of the project, how big the community was back then, how we grow, where we are now, and maybe a bit about future.

We got carried away and the recording became longer than we all planned. But it has some nice sound bites, back stage stories, and stuff even some of us didn't know about! I hope you'll enjoy it. The MP3 file is here, or you can use your favorite podcast app and subscribe to http://jenkins-ci.org/podcast.