Let's voice the baseline candidates and concerns so we have the
candidate agreed on by the end of the week.
To get the discussion started, how about 2.249?
https://jenkins.io/changelog/
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers"
Hello everyone,
Latest LTS RC was made public and it is ready to be tested. Final
release is scheduled for 2020-08-12.
Please, report your findings in this thread.
Download bits from
http://mirrors.jenkins-ci.org/war-stable-rc/2.235.4/jenkins.war
Thanks!
--
oliver
--
You received this mes
PM Johno Crawford
wrote:
Hi Oliver,
Any https servers available to download the latest LTS RC?
J
On Sun, Aug 2, 2020 at 9:30 AM Oliver Gondža
wrote:
Hello everyone,
The backporting PR is now ready:
https://github.com/jenkinsci/jenkins/pull/4918
On 21/08/2020 16.22, Mark Waite wrote:
Oliver,
We're scheduled to have a release candidate of 2.249.1 next Wednesday,
August 26. I don't see a stable-2.249 branch on the Jenkins core
repository.
Will you be st
Hello everyone,
Latest LTS RC was made public and it is ready to be tested. Final
release is scheduled for 2020-09-09.
Please, report your findings in this thread.
Download bits from
http://mirrors.jenkins-ci.org/war-stable-rc/2.249.1/jenkins.war
(sha256:b87ac2d3296149d5b28a40016f6394fb1246
I am not aware that any work have been done to support this.
On 27/08/2020 21.06, Ullrich Hafner wrote:
My warnings plugin is using in our Jenkins CI build also UI tests (using
the ATH container). Is there a way to start these UI tests (using the
ATH container) so that depending plugins that ha
Hello everyone,
Latest LTS RC was made public and it is ready to be tested. Final
release is scheduled for 2020-10-07.
Please, report your findings in this thread.
Download bits from
http://mirrors.jenkins-ci.org/war-stable-rc/2.249.2/jenkins.war
(sha256:da03fb4edb732f8a9b8034944257ba1deccc
Hey Folks, After all those years with the project doing my best here and
there (Release and LTS officer, reviewer and maintainer of a number of
components), I have chosen to step back a bit. Partially as my focus is
shifting away slowly, but mostly to direct my attention to my family and
the tw
Let's voice the baseline candidate suggestions and concerns.
We seem to be in the situation where all recent weeklies are fixing
recent regressions making none of them an appealing candidate to me. I
do not feel like choosing the latest weekly in a hope all will be well
from now on. But at the
For now, we have no better candidate than 2.263. I suggest to accept it,
with possibility to reevaluate in two weeks when the line is supposed to
be initiated. We will keep it if nothing pressing pops up.
On 23/10/2020 02.05, Mark Waite wrote:
That's correct. The windows installer can't be bui
Hello everyone,
Latest LTS RC was made public and it is ready to be tested. Final
release is scheduled for 2020-11-04.
Please, report your findings in this thread.
Download bits from
http://mirrors.jenkins-ci.org/war-stable-rc/2.249.3/jenkins.war
(sha256:9b6a00807f2539571c5a838ec9494d091089
Hey, Thank you all for the inputs. I approve the suggested timeline, so
the calendar is updated.
Please do not count on the exact RC date in late December.
On 12/11/2020 00.43, Victor Martinez wrote:
+1
Just a quick question regarding the winter break, even if the release
dates are not known
Hey folks,
I will be holding a brief session on the LTS maintenance and
certification process tomorrow on zoom. Anyone interested is welcome to
join. I will very likely not have enough material to fill the entire
hour so everyone is encouraged to bring whatever questions they have.
Part of t
Hello everyone,
Latest LTS RC was made public and it is ready to be tested. Final
release is scheduled for 2020-12-02.
Please, report your findings in this thread.
Download bits from
http://mirrors.jenkins-ci.org/war-stable-rc/2.263.1/jenkins.war
(sha256:679d2436eb1b537fe378905306cdbf904e2a
Hey, there is a long anticipated feature merged in in the plugin[1][2],
but no maintainer appears to be active to cut a release.
Are there any objections if I step in a do the release?
[1] https://github.com/jenkinsci/ghprb-plugin/pull/731
[2] https://issues.jenkins-ci.org/browse/JENKINS-55793
Hey, I am struggling with something supposedly simple. I need to get a
list of strings from user through both UI and JCasC.
In UI, I use `f:repeatable > f:textbox`, that unfortunately produces a
bit clumsy json structure of `"foo": [ {"name": "value 1"},
{"name": "value b"}, ... ]`. For databi
Hey folks, There are 2 new plugin pending hosting request right now, and
I would like to elaborate on the Gating subsystem it introduces.
Partially to get the word our, but also to gain more feedback.
The concept of Gating permits Jenkins to become aware of availability of
individual infrastru
M, Mark Waite wrote:
No objections from me.
On Wed, Jan 6, 2021 at 2:18 AM Oliver Gondža wrote:
Hey, there is a long anticipated feature merged in in the plugin[1][2],
but no maintainer appears to be active to cut a release.
Are there any objections if I step in a do the release?
[1
Backporting to 1.509.3 is now complete. We have 24 backported isses
(labeled as 'lts-1.509.3-fixed') and 6 issues was left for next release.
Kohsuke, please create release candidate.
Thanks
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Develop
Hi,
It seems that the daemon listens to all repos and all branches belonging
to the jenkinsci organisation. When I reverted a couple of commits on the
stable branch it got linked to the jira[1] so it might seem to get
reverted in master which it was not. (in case you are wondering why the
Hi, have a look at HostingPlugins[1] wiki entry. Especially, "HTTP 401
when transferring a file to the Jenkins Maven repository" looks like your
problem.
[1]
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org
--
oliver
--
You received this
It is in sync now.
On Mon, Sep 16, 2013 at 2:17 PM, Jesse Glick wrote:
> Looks like this has already begun. Can we make sure the label
> 1.509.4-fixed gets applied to things that are backported?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Develo
I forgot to mark the rejected issues after 1.509.3. I do not promise I
will have time to review and backport all new candidates. Btw.: What do
core think, are the LTS releases becoming too huge? We seem to sustain the
quality lever for now, IMO.
--
oliver
--
You received this message becau
Hi,
I have finished backporting issues for 1.509.4. On governance meeting, we
agreed that this is the very last minor release based on 1.509. We have 5
blockers and 8 critical fixes backported, 35 issues in total[1]. All 4
issues rejected from 1.509.3 will be present in 1.509.4.
Kohsuke,
Hi, I am not sure if there is a way of making EnvVars case-sensitive
without breaking existing setups. How about making the class
case-sensitive internally and when resolving particular key prefer exact
matches over the insensitive ones?
Given that we have:
TEST=UC_TEST
test=lc_test
PATH=/b
Just a wild guess but could it be ui-samples-plugin[1]? Formerly a part of
core repo.
[1] https://github.com/jenkinsci/ui-samples-plugin
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop
Hi,
I have started backporting fixes[1] for upcoming LTS 1.532.1.
Please note that I will be mostly offline until the first of November, and
continue backporting afterwards.
[1]
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+%221.532.1-fixed%22
--
I have backported all soaked candidates into stable branch.
We bundle maven-plugin 2.0, ssh-slaves 1.5, credentials 1.9.1 and
ssh-credentials 1.5.1.
Provided no more candidates will be flagged until next week, I will ask
Koshuke to produce RC. Sorry I missed the meeting.
--
oliver
--
You
IFAICT JENKINS-14336 has caused regression not yet resolved, the other two
are features. Generally, I do not consider features to be backported until
someone explicitly asks. So, I will have a look at JENKINS-19739 and
JENKINS-15757.
--
oliver
--
You received this message because you are s
Hi,
Backporting to 1.532.1 is finished[1]. Kohsuke, please, publish release
candidate.
Daniel: Non of the 2 RFEs is voted enough and trivial enough to be
backported.
[1]
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+%221.532.1-fixed%22
--
oliv
Hi Marco,
I am glad to hear you consider contributing to selenium test suite.
The exception means that runner timed out waiting for jenkins to become
ready ("Jenkins completed initialization" should appear in log). I do not
use tomcat controller but the details should be in Jenkins log (prob
Thanks nicolas,
Could you list the repos that rejected the push and point us to the backup
repos so we can fix the rest manually? For instance
next-build-number-plugin is missing 6 commits compared to my local copy. I
assume this is not the only one.
--
oliver
--
You received this messag
I agree it's ready.
Btw there is still some low hanging fruit on[1] that can be easily
automated. I'll try to cover it until next release.
[1] https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.532.x+RC+Testing
--
oliver
--
You received this message because you are subscribed to the Google G
Hi,
I have started backporting changes for 1.532.2[1].
[1]
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+%221.532.2-fixed%22
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsub
Hi,
the vncserver does not start[1][2] for selenium test suite. Can anyone at
CloudBees have a look at it?
[1] https://jenkins.ci.cloudbees.com/job/selenium-tests/277/console
[2] https://jenkins.ci.cloudbees.com/job/selenium-tests-stable/15/console
Thanks
--
You received this message becaus
On Wed, 18 Dec 2013 16:53:24 +0100, Jesse Glick
wrote:
Is there a schedule for its release?
I believe people will not have enough time for manual testing before
holidays. I suggest releasing RC before Christmas and 1.532.2 in early
January.
Running selenium tests locally and will report
Hi,
The RC is out[1] fixing 24 issues[2].
[1] https://jenkins-ci.org/stable-rc
[2]
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+10172+AND+labels+%3D+%221.532.2-fixed%22
Happy testing
--
oliver
--
You received this message because you are subscribe
Hi,
After a brief discussion with Kohsuke I would like to propose a change in
a process of LTS release publishing. Currently, we try to deliver LTS
release once a month preceded by a one week RC testing period. The effort
is coordinated on dev list and the effective release date is influenc
New model was discussed and agreed on at today's meeting. Detail at
https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line.
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receivin
I have left out that bullet accidentally: "When we pick the next 1.X as
the baseline, 1.Y.* releases will cease". IOW there will be no updates to
upstream LTS once we move to a newer baseline.
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
De
Core tests started to fail with:
java.security.cert.CertificateExpiredException: NotAfter: Wed Feb 26
12:06:22 EST 2014
at
sun.security.x509.CertificateValidity.valid(CertificateValidity.java:273)
at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:581)
at hudso
Hi,
According to documentation[1][2] it is done using the -p option. I am sure
what command you are referring to but I consider passing all console
options to build as parameters to be a bad idea from command API evolution
standpoint.
[1] https://ci.jenkins-ci.org/cli/command/build
[2] ja
see https://cloudbees.zendesk.com/requests/15609
On Thu, Jan 16, 2014 at 3:26 PM, ogondza wrote:
> Is there any development?
>
> --
> oliver
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop
Rc looks good and we are ready for the release as long as I am concerned.
The selenium tests are broken[1] since mid-december. Meanwhile I run those
tests locally before rc.
[1]
https://groups.google.com/forum/#!topic/jenkinsci-dev/0Sf_YgLUmxc/discussion
--
oliver
--
You received this mes
Just realized that this was sitting in my drafts folded since January
21th. Sorry
---
I have finished manual testing. The release is good to go.
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group a
Hi,
I would like to announce the first release of Implied Labels Plugin. Its
overall goal is to eliminate redundancy in label declarations using
globaly configured label implications.
More at wiki page
https://wiki.jenkins-ci.org/display/JENKINS/Implied+Labels+Plugin
--
oliver
--
You r
t; Would you prefer a bug report on the issue, or is this mail message
> sufficient?
>
> Thanks,
> Mark Waite
>
>
> On Mon, Feb 10, 2014 at 2:54 PM, oliver gondža wrote:
>
>> Hi,
>>
>> I would like to announce the first release of Implied Labels Plugin. I
Hi,
I have started backporting changes for the next LTS release[1]. Unless
there are any objections I suggest to switch to a new model from 1.532.3.
Backporting will end at the end of February so we are ready to have RC out
14 days after yesterday's LTS release.
[1]
https://issues.jenki
Thanks for fixing it. Selenium tests are running again.
--
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.c
Hi,
If you want to be notified about all started builds see RunListener[1], if
only for explicitly configured jobs see BuildWrapper[2].
[1] http://javadoc.jenkins-ci.org/?hudson/model/listeners/RunListener.html
[2] http://javadoc.jenkins-ci.org/?hudson/tasks/BuildWrapper.html
--
oliver
--
Y
Jesse,
I suggest to reject JENKINS-18680 as a candidate for this release line. It
is a minor issue an requires backporting JENKINS-18028 and bunch of other
commits as well. Just checking in case you have some serious objections.
--
oliver
On Wed, Feb 19, 2014 at 4:55 PM, Jesse Glick wrote:
>
Mostly same story here with the exception I have never felt comfortable or
productive working in ruby.
Btw, you have expressed dislike towards Cucumber/BDD style features in the
past. Can we take this opportunity to get rid of it as well? It should not
mean significantly more work and if it
Backporting for 1.532.3 is over. All soaked candidates with the exception
of JENKINS-18680 got backported.
Unit tests* and selenium tests** are passing. Kohsuke, please, post RC.
* https://jenkins.ci.cloudbees.com/job/core/job/jenkins_lts_branch/69/
**
https://jenkins.ci.cloudbees.com/job/s
Hi,
Here is a CI job for acceptance tests:
https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/
--
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
On Sat, 15 Mar 2014 22:34:01 +0100, Richard Lavoie
wrote:
What about just changing the selector to rely on html markup instead of
actual text ?
This will solve the issue altogether of the I18n problem.
In this case probably yes, generally no. There are a lot of elements that
are rather
On Tue, 18 Mar 2014 13:30:28 +0100, Ulli Hafner
wrote:
Seems that the latest changes broke a lot of tests:
https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/lastCompletedBuild/testReport/
I am looking at it. To me it seems that we are using the plugins UI
elements earl
Hi,
Backporting window for next LTS now opened. The RC will be published on
2014-04-16.
--
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 jenk
Hi,
Backporting window for next LTS now opened. The RC will be published on
2014-04-16.
--
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 jenk
Correction it is 1.554.1.
https://groups.google.com/d/topic/jenkinsci-dev/tpoD0qsucMk/discussion
--
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
On Wed, 16 Apr 2014 00:07:31 +0200, Ulli Hafner
wrote:
I'm currently working with 12 master students in the area of the
"acceptance test harness" project. Currently we are still in the
planning and knowledge building phase but we are planning to work in the
following areas soon:
Docker
Hello everyone,
As you probably all know, latest RC was made public just yesterday. Join
us testing what will become next LTS release!
We have two weeks to make sure that all the fixes[1] are in place and no
new regressions was introduced.
Report your findings in this thread or in the tes
On Wed, 23 Apr 2014 16:50:39 +0200, Ulli Hafner
wrote:
First of all, we will replace the current test fixture (GitHub project)
by a docker image with local git repository. Then we try to add some
more basic test cases. We will see how many additional test cases we can
add until end of ju
On Thu, 24 Apr 2014 18:50:36 +0200, Ulli Hafner
wrote:
I also would prefer to use Jira since all of our other issues are
located there.
I do not feel strongly here and Marco is right issues are disabled for the
repo. Let's be consistent with other repositories and use jira as well.
Ull
The RC testing period is over.
Regular test as well as acceptance tests are both green. Manual testing
have not discovered any problems either. As long as I am concerned we are
ready for the release.
https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.554.x+RC+Testing
https://jenkins.ci.cloud
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
--
You received this message because you are subscribed to the Google Groups "Jenkins
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
--
You received this message because you are subscribed to the Google Gro
On Thu, 15 May 2014 19:06:28 +0200, twr
wrote:
I make extensive use of summary actions on builds, but I would like to do
something similar on the project page (for a summary of all builds)?
Where would I start with this? (best I've managed is links to alternate
page via ProminentProjectActio
Hi,
Latest RC was made public. Join us testing what will become next LTS
release!
We have two weeks to make sure that all the fixes[1] are in place and no
new regressions was introduced. 1.554.2 will be released 2014-05-28.
Report your findings in this thread or in the test plan wiki.
Do
Thanks for the test you have already created. Can you publish what you
have in a PR, so we can discuss actual code?
--
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
On Thu, 22 May 2014 11:28:22 +0200, Ivan Kalinin
wrote:
Can anybody handle this please? That's a good plugin!
On Wednesday, May 21, 2014 3:53:32 PM UTC+4, Denis Chernilevskiy wrote:
Hello!
I'd like to publish our "Allure report publisher" plugin.
The plugin is currently hosted here:
https
This depends on how the project classes will be reused by other
testsuites. I believe it makes sense to reuse page objects for both core
and plugins. So framework and POs + necessary resources should be in src.
I am not sure it makes sense to reuse docker containers we use for
testing, thou
This seems to supplement capybara we ware using back in selenium tests.
Unfortunately, we have already reimplemented a lot of its features (see
CapybaraPortingLayer, Controll). I don't feel strongly about its inclusion.
--
oliver
--
You received this message because you are subscribed to the
Stephen,
You suggest strictly separating UI tests and behavior tests, but using
backdoor manipulation/verification via xml configuration is no longer
end-to-end testing. Not to mention that plugin config is not exposed to
user as XML. Plus, if we move test fixtures to xml and the plugin
p
Hi, First bunch on fixes was backported to be released this Wednesday as
1.554.3-rc.
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+%221.554.3-fixed%22
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Dev
Hi,
New LTS candidate is out. Final release is scheduled to 2014-06-25. Help
us make sure all fixes ware delivered without introducing another
regressions!
Download from here:
http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war
Check our test plan:
https://wiki.jenkins-ci.org
On Tue, 24 Jun 2014 01:14:04 +0200, Tom Fennelly
wrote:
After making a series of Jelly script changes, I'm now getting regular
OOM
failures from
AbstractProjectTest.testConfiguringBlockBuildWhenUpstreamBuildingRoundtrip
(in the test harness) Here's the branch
https://github.com/tfennelly/j
RC testing is over. We can proceed with the release.
Thanks everyone who helped with manual testing.
--
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 emai
Hi,
As the latest governance meeting did not happen, Jesse and I have picked
new release line without much feedback. Letting you know that unless there
are serious objections 1.565 is going to be the next LTS.
This decision will be cast in stone when backporting starts on Wednesday.
--
oli
Hi,
Backporting starts with a bit of a delay this time. End of the backporting
window and date RC will be published is not affected: 2014-07-09.
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+%221.565.1-fixed%22
--
oliver
--
You received this message
Note that there is a HTML Publisher Plugin to publish any directory as
report linked via build action. It seems to me that your usecase can be
satisfied using this plugin and any tool to generate the report invoked
from buildstep.
Btw.: I have never used log parser but I believe attaching n
--- Forwarded message ---
From: "oliver gondža"
To: "jenkinsci-us...@googlegroups.com"
Cc:
Subject: 1.565.1 LTS RC testing started
Date: Mon, 14 Jul 2014 13:14:10 +0200
Hello everyone,
Latest RC was made public last Wednesday. Join us testing what will become
n
Hi, if `mvn package` is able to build it without problems Eclipse is to
blame for missing imports.
Try running `mvn eclipse:eclipse` and refreshing the project from Eclipse.
For sources that needs to be attached use `mvn dependency:sources`.
--
oliver
--
You received this message because you
On Fri, 25 Jul 2014 23:15:53 +0200, Karthik V S
wrote:
I have a list of publishers that I have to add to my Jenkins job thru
Java
Code and then create the job.
How is that possible? Any inputs would be greatly appreciated.
Hi,
Create the job first, then add publishers. This is done routin
Hi,
Backporting changes for 1.565.2 is completed. Fixed issues:
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+%221.565.2-fixed%22
Somehow I forgot to announce that backporting started. Sorry about that.
--
oliver
--
You received this message because
On Wed, 13 Aug 2014 18:41:35 +0200, Kohsuke Kawaguchi
wrote:
1.565.2 RC1 posted.
Given that I dropped the ball once again, I'm happy to push the release
date out for two weeks to make up for it if need be.
I will not be able to start testing before Tuesday, postponing certainly
works for
On Fri, 22 Aug 2014 17:47:14 +0200, Christian Galsterer
wrote:
Hi,
I created a new plugin which allows to set the build description with
support for macros from the Token Macro Plugin.
My Github ID is:christiangalsterer
The repo is available at
https://github.com/christiangalsterer/build-de
Hello everyone,
Latest RC was made public and it is ready to be tested.
We have 8 days to make sure that all the fixes[1] are in place and no new
regressions ware introduced.
Report your findings in this thread or in the test plan wiki.
Download bits from
http://mirrors.jenkins-ci.org/war-st
Hi Stefan,
There are several fixes[1] in jobConfigHistory I am interested in that
will hopefully go into next release. As the core dependency was bumped
recently I have to maintain a private fork based on 2.6. Therefore, I
volunteer to maintain stable branch in community that works for 1.53
Sounds like
https://groups.google.com/d/msg/jenkinsci-dev/qkmbl3HrYgk/TBdhCTUGZgEJ
--
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-d
I have just found out that this was never delivered to jenkinsci-dev:
===
Backporting for new LTS release has started. User can expect RC to be
published by 2014-09-17.
Fixed issues:
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+%221.565.3-fixed%22
--
There seems to be some problem with
https://ci.jenkins-ci.org/view/All/job/infra_statistics/ and it seems that
only few can configure the job. I would like to have a look. Can I get
Job.CONFIGURE? Thanks
--
oliver
--
You received this message because you are subscribed to the Google Groups
Backporting is over, all candidates but one[1] will be included in 1.565.3.
[1] https://issues.jenkins-ci.org/browse/JENKINS-19310
--
oliver
JBoss QA Jenkins Team
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this gr
Hello everyone,
Latest RC was made public and it is ready to be tested.
We have 10 days to make sure that all the fixes[1] are in place and no new
regressions ware introduced.
Report your findings in this thread or in the test plan wiki.
Also, make sure to use linked war as this is the only bu
On Wed, 24 Sep 2014 19:42:27 +0200, Daniel Beck wrote:
I checked the anonymous usage stats a few weeks ago:
Out of 93,400 installs, we know the master's OS for 85,200 of them.
285 are AIX. 120 are HP-UX. 50 installs total on OpenBSD, Darwin,
OS/400, z/OS and NetBSD.
Not relevant enough IMO
On Wed, 01 Oct 2014 19:04:54 +0200, Peter Blume
wrote:
Hi,
I released my plugin on Sunday und updated yesterday. So far so good.
Hi,
Note that pushing to github != releasing. See:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org.
At le
Hi,
Next LTS was chosen today and backporting effectively starts now.
Backported issues:
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+10172+AND+labels+%3D+%221.580.1-fixed%22
--
oliver
--
You received this message because you are subscribed to the Go
Noting Daniel suggests JENKINS-24453 to be 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.co
On Mon, 13 Oct 2014 16:50:05 +0200, Jesse Glick
wrote:
On Sun, Oct 12, 2014 at 9:32 AM, ogondza wrote:
That would be great, Jesse, thanks!
So you probably already know this, but in case not: it is not possible
to apply security fixes to this branch (via git-merge) until the
stable-vs.-sta
Backporting is effectively over. 8 issues was backported for 1.580:
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+%221.580.1-fixed%22
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To
Hi, LTS RC testing is on.
Bits are on usual location:
http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war
So does test plan:
https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.580.x+RC+Testing
Sorry for the late notice
--
oliver
--
You received this message because you are subscr
1 - 100 of 476 matches
Mail list logo
