Backporting for 1.554.2 started

42 views
Skip to first unread message

oliver gondža

unread,
May 5, 2014, 5:13:09 PM5/5/14
to jenkin...@googlegroups.com
Backporting window for 1.554.2 is opened since April 30th. You can expect
RC at May 14th.

https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+%221.554.2-fixed%22

--
oliver

Daniel Beck

unread,
May 6, 2014, 2:50:07 PM5/6/14
to jenkin...@googlegroups.com
Are you planning to include JENKINS-18008? The fix was in 1.560.

https://github.com/jenkinsci/jenkins/commit/56052c8452173140c63d5cc15bdd79b510523cc4

While it updates the "winstone" component, there are no other unrelated changes.

https://github.com/jenkinsci/winstone/compare/winstone-2.2...winstone-2.3
> --
> 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.
>

Jesse Glick

unread,
May 13, 2014, 11:32:33 AM5/13/14
to jenkin...@googlegroups.com
Consider backporting

https://github.com/jenkinsci/jenkins/commit/fb0ad71b719f4a49e21492273c3f3a03035b92fa

Should be harmless, just in test harness, but useful.

Stephen Connolly

unread,
May 14, 2014, 5:20:27 AM5/14/14
to jenkin...@googlegroups.com
I am strongly inclined to advocate for the inclusion of:


But I also understand if this is too late in the day and we need to wait for 1.554.3...




--
oliver

--
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-dev+unsubscribe@googlegroups.com.

ogondza

unread,
May 14, 2014, 8:31:39 AM5/14/14
to jenkin...@googlegroups.com
On Wednesday, May 14, 2014 11:20:27 AM UTC+2, Stephen Connolly wrote:


But I also understand if this is too late in the day and we need to wait for 1.554.3...

Yes, we will. Note the issue is not resolved.

oliver gondža

unread,
May 14, 2014, 8:39:23 AM5/14/14
to jenkin...@googlegroups.com
Backporting is finished. There are 12 fixes only, no critical or blocker
issues. No fix was rejected.

https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+%221.554.2-fixed%22

--
oliver

Stephen Connolly

unread,
May 14, 2014, 8:51:35 AM5/14/14
to jenkin...@googlegroups.com
Only not resolved because the bot has been slow to pick up the [FIXED...] commit comment


--
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.

Christopher Orr

unread,
May 14, 2014, 7:09:35 PM5/14/14
to jenkin...@googlegroups.com
Hmm.. are there still problems with the JIRA bot?

I pushed several [FIXED JENKINS-xxx] commits today, and over 24 hours
ago to android-emulator-plugin, but JIRA still hasn't updated at all.

Thanks,
Chris


On 05/14/2014 02:51 PM, Stephen Connolly wrote:
> Only not resolved because the bot has been slow to pick up the
> [FIXED...] commit comment
>
>
> On 14 May 2014 13:31, ogondza <ogo...@gmail.com
> <mailto:ogo...@gmail.com>> wrote:
>
> On Wednesday, May 14, 2014 11:20:27 AM UTC+2, Stephen Connolly wrote:
>
>
> https://github.com/jenkinsci/jenkins/commit/7c620e9fd321029e05f7cc994d3da1dde48411f7
>
> But I also understand if this is too late in the day and we need
> to wait for 1.554.3...
>
>
> Yes, we will. Note the issue is not resolved.
>
> --
> 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
> <mailto:jenkinsci-de...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> 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
> <mailto:jenkinsci-de...@googlegroups.com>.

Kohsuke Kawaguchi

unread,
May 15, 2014, 2:32:43 AM5/15/14
to jenkin...@googlegroups.com
1.554.2 RC posted.


--
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-dev+unsubscribe@googlegroups.com.

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



--
Kohsuke Kawaguchi

Kohsuke Kawaguchi

unread,
May 16, 2014, 1:38:49 PM5/16/14
to jenkin...@googlegroups.com
The daemon that does that was not receiving emails because Dyndns
killing its free service severed the mail delivery route.

I have that fixed a while back, but Google Groups never retries an email
address once it starts bouncing, even after the bounce is fixed, and I
didn't notice that that was happening until too late.

The problem is corrected now, I'll investigate if I can rerun the daemon
by manually feeding commit messages while the daemon was incapacitated.
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins

Kohsuke Kawaguchi

unread,
May 19, 2014, 1:04:43 PM5/19/14
to jenkin...@googlegroups.com

I've manually fed the backlog to the daemon, so all the pending messages
except one has been processed.

The one message that just doesn't seem to work for some reason is
1d597cf in androd-emulator-plugin that fixes JENKINS-12821. JIRA fails
in trying to retrieve existing comments.

But orrc has already marked this as fixed anyway, so I think there's
little damage.
Reply all
Reply to author
Forward
0 new messages