Re-doing the 2.0 branch

57 views
Skip to first unread message

Daniel Beck

unread,
Jan 18, 2016, 7:33:34 PM1/18/16
to Jenkins Developers
Hi everyone,

I deleted the 2.0 branch and started over from current master.

So far, the branch only contained changes from Tom's PR 1822[1], which he committed directly to the branch due to a misunderstanding. I originally planned to have any issue be resolved in follow-up PRs, and revisit the list of plugins later. Given the nature of the change and the discussions around it, Tyler, Tom, and I decided to not continue with the branch as it was, so into the trash it went (now known as 2.0-original).

Tom will submit a new PR for the install wizard, this time targeting the new 2.0 branch, which will contain a placeholder list of plugins only (basically what is currently bundled). I'll also try to get him to implement an update site-based data source later, so the data is downloaded from the update site, rather than bundled with Jenkins.

For the specific selection of plugins, our previous discussion ended without a real result[2]. I'll write up a proposal with criteria for which plugins to include on the wiki so we have something to base discussions on.

Daniel

1: https://github.com/jenkinsci/jenkins/pull/1822
2: https://groups.google.com/forum/#!msg/jenkinsci-dev/w-_18aYn4QQ/t_WT442bBwAJ

Kanstantsin Shautsou

unread,
Jan 19, 2016, 11:04:54 AM1/19/16
to Jenkins Developers, m...@beckweb.net
Would be cool if it wouldn't mass spam jira issues already fixed and released long time ago.

Daniel Beck

unread,
Jan 19, 2016, 11:07:05 AM1/19/16
to jenkin...@googlegroups.com

On 19.01.2016, at 17:04, Kanstantsin Shautsou <kanstan...@gmail.com> wrote:

> Would be cool if it wouldn't mass spam jira issues already fixed and released long time ago.

Which issues were spammed?

Kanstantsin Shautsou

unread,
Jan 19, 2016, 11:15:35 AM1/19/16
to Jenkins Developers, m...@beckweb.net

Slide

unread,
Jan 19, 2016, 11:27:37 AM1/19/16
to Jenkins Developers, m...@beckweb.net
I got an email for a REALLY old issue this past week as well. Not a big deal unless you are involved in lots of issues I would guess.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/60b4a958-c71c-4ab3-9877-28ee383038b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Daniel Beck

unread,
Jan 19, 2016, 11:55:30 AM1/19/16
to jenkin...@googlegroups.com

On 19.01.2016, at 17:15, Kanstantsin Shautsou <kanstan...@gmail.com> wrote:

> I.e. https://issues.jenkins-ci.org/browse/JENKINS-10629

I don't think that was me. The linked commit indicates it's the test harness change:

https://github.com/jenkinsci/jenkins-test-harness/commit/9823d43e2d9ebd9cccad7efca8eb965bc4aafedf

In fact, since I threw away the old branch and created a new one with basically no changes, there are no new commits referencing any issues. The only email you should have received would be that one open PR against 2.0(-original) was closed.

What I _did_ cause was a few emails since I merged master into 2.0(-original) to refresh the state of Jenkins there, but those were at most ~3 months old. And they predate this restart of the 2.0 branch.

Jesse Glick

unread,
Jan 19, 2016, 1:52:09 PM1/19/16
to Jenkins Dev
“Someone” should update the JIRA link daemon to be more discerning:
only send notifications for non-cherry-picked commits pushed to the
`master` branch, for example.

Arnaud Héritier

unread,
Jan 19, 2016, 3:29:36 PM1/19/16
to jenkin...@googlegroups.com
We could also replace this old bot integration with the native DVCS plugin in Jira which is displaying commits and PR links without adding comments. 

I think Tyler will like this idea which may require some additional resources in Jura side ....
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
-----
Arnaud Héritier
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

Jesse Glick

unread,
Jan 19, 2016, 3:41:13 PM1/19/16
to Jenkins Dev
On Tue, Jan 19, 2016 at 3:29 PM, Arnaud Héritier <aher...@gmail.com> wrote:
> the native DVCS plugin in Jira which is displaying commits and PR links without adding comments.

That would be great if we can get it set up!

Tom Fennelly

unread,
Jan 20, 2016, 6:26:19 AM1/20/16
to Jenkins Developers, m...@beckweb.net
The plugin selection wizard (and plugin unbundling) PR is back ... https://github.com/jenkinsci/jenkins/pull/1995

The current set of plugins in the wizard are just those that are currently bundled in Jenkins 1.x. The actual list needs to be decided. Let the debate begin ....
Reply all
Reply to author
Forward
0 new messages