Tests looks good to me. Kohsuke, please post RC.
https://jenkins.ci.cloudbees.com/job/core/job/jenkins_lts_branch/53/
--
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
Hi,
I would like to introduce this little command line tool I use to move jobs
around between different Jenkins instances. I find this useful when
reproducing reported defects in testing environment and I plan to use this
for larger migration of jobs and views. Tool identifies configured
Definitely related, selenium-tests repo lost 17+ commits after such push.
--
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
I have already asked Github support to provide hashes of former master
positions and referenced this thread. Will report ASAP.
--
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
JENKINS-19739 backported
--
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+unsubscr...@googlegroups.com.
For more options, visit
Hi,
I have backported one more commit[1] Stephen wanted after the 1.509.4-rc
was released. Contrary to what we have agreed on governance meeting I
decided _not_ to backport JENKINS-19251 as it depends on JENKINS-16261
(which is something I should have checked before, sorry). If someone
I consider this pull request feature complete. If interested, try it out:
https://jenkins.ci.cloudbees.com/job/core/job/jenkins_main_trunk/1247/artifact/war/target/jenkins.war
--
oliver
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To
I would really like to avoid 1.509.5 . Can we produce
1.509.4-JENKINS-14362-jzlib before 1.509.4 or even before 1.509.4-rc so we
can benefit from the reports?
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group
Jesse under
https://github.com/jenkinsci/jenkins/commit/a021fe5c2422c47d977d7937f4e01483f121b777:
@olivergondza if you are backporting this then I would urge you to also
backport
https://github.com/jenkinsci/jenkins/commit/b02d45737e4eb7a0455ebe192271cf76bbf271e0
from
Hi, it's been a while but finally I have something that seems to work for
freestyle, maven and matrix projects. I am working on report aggregation so
it is sill a work in progress. But the most important part is done:
asynchronous test result updating for individual builds.
tl;dr: Every build
I am releasing this plugin to deliver the feature early. In the meantime,
someone might find it useful.
https://wiki.jenkins-ci.org/display/JENKINS/JUnit+Realtime+Test+Reporter+Plugin
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To
Thanks. Reverting JENKINS-14351 as the fix for JENKINS-19192 is bright new.
--
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
Thanks for the feedback. I guess we agreed that it would be an interesting
feature for core provided we can implement it in a reasonably efficient way.
@kpfleming: We can do better than re-runing JUnitResultArchiver. I have
modified the parser to update result object incrementally in order
I assume we do not want to wait two weeks with 1.509.3 until stapler 1.217
became soaked. Besides, using stapler 1.217 in Jenkins seems to introduce
new regression [1].
It seems that JENKINS-18776 is the only thing to revert it we want to stay
on 1.207. So I vote for pushing it to 1.509.4 that
Thanks, never heard about the plugin before. This seems to require
assistance from the project being built, right?
I simply rerun JUnitParser to collect report files regardless where did
they come from.
Perhaps I'm wrong. I do not have enough time try it out.
--
oliver
--
You received
From all the alternatives
- not including the fix for JENKINS-18776 in 1.509.1
- reverting the bug in stapler, releasing it and using blending edge
stapler in LTS Jenkins
- or backporting necessary fix and using stapler 1.207.1
I prefer the last one but the decision is on you and Kohsuke.
Jesse,
The tags are in place. Maintaining a list of lts-candidates that has not
been backported yet seems like an overkill to me. I was about to label the
issues lts-1.509.3-fixed when they get merged to jenkinsci:stable. I do not
mind labelling issues as fixed right away when backported to my
I have started relabelling with lts-1.509.3-fixed. Candidates to go
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hiderequestId=12146
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop
There seems to be https://github.com/jenkinsci/matrixtieparent-plugin
repository. However, I do not know what is the relation between the two.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop
Bumping my original request.
On Friday, April 12, 2013 5:42:17 PM UTC+2, ogondza wrote:
Hi,
Can I have commit rights granted for jenkins core? My ICLA was merged
already (thanks Jesse).
GitHub ID: olivergondza
--
oliver
--
You received this message because you are subscribed
https://wiki.jenkins-ci.org/display/JENKINS/Basic+guide+to+Jelly+usage+in+Jenkins
is a good start
--
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
The work is here https://github.com/jenkinsci/selenium-tests. It covers
both the core and same plugins.
Hi,
What is the procedure for creating new JIRA components? There is quite a
lot mailer-plugin related issues but corresponding component does not seem
to exist.
Hi, it's been two months I proposed[1] a change that propagates build
parameters to matrix combination filters.
Several people seemed to be interested in such behaviour in the past, but
the pull request remains unnoticed.
[1] https://github.com/jenkinsci/jenkins/pull/584/
--
oliver
101 - 124 of 124 matches
Mail list logo